io.github.CloudCorpRecords/linkrot
linkrot
Is the io.github.CloudCorpRecords/linkrot MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-31.
Docs link checker separating dead, moved, and bot-blocked links from healthy ones.
alive probed 2026-11-14 · unchanged since 2026-10-31
- Run it
- npx -y @reneturcios/linkrot@0.1.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- linkrot 0.1.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- <0.1 % of a 1M context window
- Count
- 213 tokens in Claude Opus 5.5, exact, measured 2026-10-31. With the Claude Code prefix mcp__…__ on each tool name: 222. The o200k_base estimate is 121. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/CloudCorpRecords/linkrot
- Registry
- active, updated 2026-10-30 · registry entry
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.76×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| check_links | 213 | 121 | 100 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.CloudCorpRecords/libdocs-remote · alive
- io.github.CloudCorpRecords/licensefile · alive
- io.github.CloudCorpRecords/linkedcheck · alive
- io.github.CloudCorpRecords/linkguard · alive
- io.github.CloudCorpRecords/linkscribe · alive
- io.github.CloudCorpRecords/listingdata · alive
- io.github.CloudCorpRecords/litebase · alive
- io.github.CloudCorpRecords/localmodels · alive
Servers that mention separating or blocked.
- Yokka ai.yokka/yokka · needs auth
- app.getcallme/call-me · needs auth
- ai.smithery/luminati-io-brightdata-mcp · not found
- Unblocked com.getunblocked/unblocked-mcp · needs auth
- corsproxy.dev dev.corsproxy/mcp · needs auth
- AgentWork Outcome Router io.github.mitchellOpZero/agentwork · alive
- Agent Help Network com.agenthelpnetwork/agent-help-network · alive
- Check x402 Payment Readiness io.github.kingsleyzissougdi/check-x402-payment-readiness · TLS error
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers initialize and tools/list. Nothing to fix.