io.github.CloudCorpRecords/reachvuln

reachvuln

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

Rank vulnerabilities by whether the vulnerable code path is reachable in your code.

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

1tools

627tokens in Claude Opus 5.5

0.3 %of Claude's 200k window

0.2×the median server

299 msto initialize

5 msto list tools

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

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

Servers that mention vulnerabilities or vulnerable.

Strix ai.strix/strix · needs auth
Package Health Check app.openkrill/packages · alive
app.vercel.exploitwatch-kappa/exploitwatch · alive
app.zenable/zenable · needs auth
Vigía cloud.coredls.vigia/vigia · alive
CISA Known Exploited Vulnerabilities (kevwatch) com.a2awire/data-cisa-known-exploited-vulnerability-catalog · alive
com.edgethirteen.www/exploitwatch · not found
GitHits com.githits/githits · needs auth

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.