io.github.maebsy/72hours
72hours security check
Is the 72hours security check MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-01.
Scan a public GitHub repo, explain risks, get fix prompts and rescan to confirm fixes.
alive probed 2026-11-02 · unchanged since 2026-11-01 · HTTP 200
- Endpoint
- https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc (streamable-http)
- Host
- oboe-handiness-enroll.ngrok-free.dev
- Protocol
- 2025-11-25
- Reports itself as
- 72hours-service 1.30.0
- Capabilities
- experimental, prompts, resources, tools
- Instructions
- 5 072 characters
- Of a 1M window
- 0.3 % of a 1M context window
- Count
- 2.9k tokens in Claude Opus 5.5, exact, measured 2026-11-01. With the Claude Code prefix mcp__…__ on each tool name: 3.0k. The o200k_base estimate is 1.5k. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/maebsy/YMCA-hackathon-2026
- Registry
- active, updated 2026-10-31 · 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.95×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| audit_repository | 363 | 186 | 13 % |
| incident_report | 328 | 168 | 11 % |
| check_fix | 262 | 134 | 9 % |
| verify_demo | 250 | 128 | 9 % |
| rescan | 221 | 113 | 8 % |
Compare this server with others.
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.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.