All servers · AI models & agents
LinkPulse
io.github.walkojas-boop/linkpulse · v1.0.0
No registry update 90+ days
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2024-11-05 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | tools |
| Tool definitions | 4 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
URL reality check for agents: status, content hash, classification, wayback fallback.
Connect
streamable-http · https://linkpulse-neon.vercel.app/mcp
claude mcp add --transport http linkpulse https://linkpulse-neon.vercel.app/mcp{
"mcpServers": {
"linkpulse": {
"url": "https://linkpulse-neon.vercel.app/mcp"
}
}
}Tools as reported by the server
linkpulse_checkFetch 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_diffRe-check a URL and tell you whether its content hash has changed since a previous hash you supply. Returns boolean + new hash.linkpulse_resolveResolve redirect chain for a URL without downloading the full body. Returns final URL + redirect count.linkpulse_classifyClassify 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.
Repository · Website · JSON · Text for agents · Registry updated 2026-04-19