io.github.CloudCorpRecords/failshare
failshare
Is the io.github.CloudCorpRecords/failshare MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-08.
Shared failure knowledge for agents: check known tool failures, report failures and outcomes.
alive probed 2026-11-14 · unchanged since 2026-11-08
- Run it
- npx -y @reneturcios/failshare@0.1.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- failshare 0.1.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- 0.2 % of a 1M context window
- Count
- 2.2k tokens in Claude Opus 5.5, exact, measured 2026-11-08. With the Claude Code prefix mcp__…__ on each tool name: 2.3k. The o200k_base estimate is 1.3k. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/CloudCorpRecords/failshare
- Registry
- active, updated 2026-11-04 · 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.73×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| check_tool_failure | 780 | 450 | 35 % |
| report_tool_failure | 692 | 399 | 31 % |
| report_tool_success | 420 | 242 | 19 % |
| report_recovery_outcome | 345 | 199 | 15 % |
Compare this server with others, or with the servers that share its tool set.
Same tool set as 1 other server
These registry entries have the same tool names and the same schema sizes.
- com.failecho/failecho failecho.com
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.CloudCorpRecords/errorwatch · alive
- io.github.CloudCorpRecords/evalsnap · alive
- io.github.CloudCorpRecords/exercisedb · alive
- io.github.CloudCorpRecords/exitprobe · alive
- io.github.CloudCorpRecords/fairdraw · alive
- io.github.CloudCorpRecords/famboard · alive
- io.github.CloudCorpRecords/familyorg · alive
- io.github.CloudCorpRecords/faqmine · alive
Servers that mention knowledge or failures.
- inference.sh ac.inference.sh/mcp · needs auth
- Knowledge Base ai.b77/knowledge-base · needs auth
- brainattic ai.brainattic/knowledge-base · needs auth
- Buron ai.buron/buron · paid (402)
- ColdState — Deterministic Knowledge Infrastructure ai.coldstate/knowledge · alive
- DeepDNA ai.deepdna/knowledge · alive
- ai.emberverse/emberverse · alive
- xmp4 — Semantic code knowledge for your stack ai.example4/xmp4 · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-08 08:01 | alive | 254 ms | 4 | 2.2k | 1.3k |
| 2026-11-05 08:34 | alive | 282 ms | 4 | 2.2k | 1.3k |
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.