LinkPulse MCP Server

by walkojas-boop Your server? Claim it

not responding

LinkPulse is listed as active in the registry but did not answer our last check. It exposes 4 tools.

URL reality check for agents: status, content hash, classification, wayback fallback.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 91 days of history · worst day 1%

91 days agonow

4.4%

Uptime 24h

4 of 91 checks

Tools

read from the server

1391 ms

Response time

average over 24h

open, no key

Access

streamable-http

LinkPulse does not always answer

Over the last week it answered 4.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add linkpulse --transport http https://linkpulse-neon.vercel.app/mcp

Settings → Connectors → Add custom connector, then paste this address

https://linkpulse-neon.vercel.app/mcp

~/.codex/config.toml

[mcp_servers.linkpulse]
url = "https://linkpulse-neon.vercel.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "linkpulse": {
      "url": "https://linkpulse-neon.vercel.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "linkpulse": {
      "type": "http",
      "url": "https://linkpulse-neon.vercel.app/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

linkpulse

linkpulse_check

Fetch a URL and return its current state: HTTP status, final URL after redirects, SHA-256 content hash, classification, readability score, title/meta-description, and wayback archive fallback if dead. Cached 10 minutes.

linkpulse_classify

Classify content you already have (status code + content-type + body sample) without an outbound fetch. Useful if your agent already fetched the URL via another tool.

linkpulse_diff

Re-check a URL and tell you whether its content hash has changed since a previous hash you supply. Returns boolean + new hash.

linkpulse_resolve

Resolve redirect chain for a URL without downloading the full body. Returns final URL + redirect count.

Endpoints

URL	Transport	State	Latency	Checked
https://linkpulse-neon.vercel.app/mcp	streamable-http	answering	70 ms	14 min ago

Alternatives to LinkPulse

same job, measured the same way

Web Hygiene MCP

by luca-003

Live web checks for AI agents: sitemaps, robots.txt, URL status, broken links, feeds, citations.

answering

Checkly MCP

by mrfentmen

Assertion checks for status, headers and content - no API key.

97 installs/wk local only

Uk AI Act MCP

by csoai-org

UK AI regulation compliance tools for AI agents. Capabilities: UK risk classification, AISI

124 installs/wk local only

LinkPulse

by workers-mike-tusa-linkpulse

Check one web page for broken links, redirect chains hop by hop and mixed content. Free, no key.

1 tools answering

Feedoracle Macro MCP

by feedoracle

Real-time macroeconomic signals for AI agents. 86 FRED series, regime classification, DeFi rates.

31 tools answering

AgentFirstStack Mail

by agentfirststack

Email inboxes for AI agents: wait for mail, pull out verification codes and links, reply. Free.

answering

link-check-lite

by tidybytetools

Check web links for status codes, broken links and redirect chains.

1 080 installs/wk local only

Patent Data

by patentdata

US patent status for agents: applications, office actions, owners, PTAB, claims, monitors.

answering

LinkPulse — questions

Answers built from our own checks of this server.

What can LinkPulse do?

It exposes 4 tools, read directly from the server on our last check. Among them: linkpulse_check, linkpulse_classify, linkpulse_diff, linkpulse_resolve. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is LinkPulse working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 4 of 91 checks got a reply (4.4%), average response time 1391 ms. The bar chart above shows every period we have measured.

Is LinkPulse still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

The registry lists LinkPulse as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect LinkPulse?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does LinkPulse need an API key?

No. LinkPulse completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is LinkPulse?

It answers our handshake in 1391 ms on average, which is faster than 1% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.