io.github.ProtoTeemo/leakrank-guard

LeakRank Guard

Is the LeakRank Guard MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-27.

Scans code changes for leaked secrets and insecure config, with actionable fixes for AI agents.

alive probed 2026-11-15 · unchanged since 2026-10-27

3tools

298tokens in Claude Opus 5.5

0.1 %of Claude's 200k window

0.1×the median server

70 msto initialize

26 msto list tools

Run it: npx -y leakrank-guard@0.2.3 (stdio, probed in a container with the network off)
Host: npmjs.com
Reports itself as: leakrank-guard 0.2.3
Capabilities: tools
Instructions: none
Of a 1M window: <0.1 % of a 1M context window
Count: 298 tokens in Claude Opus 5.5, exact, measured 2026-10-28. With the Claude Code prefix mcp__…__ on each tool name: 334. The o200k_base estimate is 157. Counted again when the tool definitions change. Method.
Website: https://leakrank.com/guard?utm_source=mcp-registry&utm_medium=mcp
Registry: active, updated 2026-07-29 · registry entry
Changes: 2 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.

Most expensive tools

The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.90×.

Tool	≈ Claude tokens	o200k estimate	Share of this server
guard_scan_diff	163	86	55 %
guard_scan_baseline	82	43	27 %
guard_status	53	28	18 %

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

Servers that mention guard.

We add a row when the result changes. A server with no change keeps its last row.

Probed	Result	Init	Tools	Claude	o200k
2026-10-27 06:58	alive	89 ms	3	298	157
2026-10-20 06:44	alive	70 ms	3		157

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.