mcpbeat

LinkPulse MCP Server

io.github.walkojas-boop/linkpulse
answering

LinkPulse is answering right now. Last checked 3 min ago. 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 39 hours of history · worst hour 0%
39 hours agonow
1.1%
Uptime 24h
1 of 91 checks
4
Tools
read from the server
1684 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add linkpulse --transport http https://linkpulse-neon.vercel.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "linkpulse": {
      "url": "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
{
  "mcpServers": {
    "linkpulse": {
      "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

URLTransportStateLatencyChecked
https://linkpulse-neon.vercel.app/mcp streamable-http answering 1684 ms 3 min ago

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 1 of 91 checks got a reply (1.1%), average response time 1684 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.
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 with the file path 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 1684 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.