io.github.CloudCorpRecords/linkedcheck

linkedcheck

Is the io.github.CloudCorpRecords/linkedcheck MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-03.

Verify a PR really addresses the issue it claims to close: closing keywords plus diff scope.

alive probed 2026-11-14 · unchanged since 2026-11-03

1tools

319tokens in Claude Opus 5.5

0.2 %of Claude's 200k window

0.1×the median server

180 msto initialize

3 msto list tools

Run it: npx -y @reneturcios/linkedcheck@0.1.0 (stdio, probed in a container with the network off)
Host: npmjs.com
Reports itself as: linkedcheck 0.1.0
Capabilities: tools
Instructions: none
Of a 1M window: <0.1 % of a 1M context window
Count: 319 tokens in Claude Opus 5.5, exact, measured 2026-11-03. With the Claude Code prefix mcp__…__ on each tool name: 330. The o200k_base estimate is 180. Counted again when the tool definitions change. Method.
Repository: https://github.com/CloudCorpRecords/linkedcheck
Registry: active, updated 2026-11-02 · 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.77×.

Tool	≈ Claude tokens	o200k estimate	Share of this server
check_pr_issue_link	319	180	100 %

Other registry entries on npmjs.com, the ones next to this name; all of them.

Servers that mention addresses or keywords.

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.