io.github.CloudCorpRecords/failshare
NPM · @RENETURCIOS/FAILSHARE · 2 COMPONENTS
Shared failure knowledge for agents: check known tool failures, report failures and outcomes.
Available components
Last scanned (17 hours ago)
Scores higher than 37% of npm servers
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 978 tokens (~244/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability observed for 0 of 30 days with no destabilising changes; credit accrues until the full window elapses.Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/@reneturcios/failshare@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_tool_failure Check what the network knows about a tool failure ~357
Use FailEcho when another tool fails, before retrying blindly. Call this BEFORE retrying a failed tool, API or MCP call. Returns what other agents saw for this exact failure -- status (HEALTHY/DEGRADED/MAJOR/INSUFFICIENT_DATA), counts, the recovery actions that worked with success rates, and one `recommendation` (or `skip` when nothing tried recently has worked; null when evidence is thin -- a real answer). Works on your own history before anyone else joins. Free, anonymous, stores nothing, never rate limited.
| Name | Type | Req | Description |
|---|---|---|---|
| error_code | string | – | Code, e.g. '422', 'ECONNRESET'. |
| error_message | string | – | The error text only; normalized server-side, not stored by this call. |
| error_type | string | – | Failure class, e.g. 'validation_error', 'timeout', 'rate_limit', 'auth_error'. |
| operation | string | yes | The tool or endpoint as the server names it, e.g. 'create_issue', not 'mcp__github__create_issue'. |
| reporter_id | string | – | Optional stable agent id; hashed, never stored raw. Lets from_other_agents be answered. |
| schema_hash | string | – | Short hash of the tool schema you used (separates 'API broke' from 'schema stale'). |
| service | string | yes | The MCP server's own name (serverInfo.name) or the API host, e.g. 'api.github.com'. Not your client's local alias. |
| verbose | boolean | – | Full record (timestamps, rates, effective counts, every action). Default: the compact answer. |
| version | string | – | Service/tool version, if known. |
No output schema declared.
No examples provided.
report_recovery_outcome Report whether a recovery action worked ~141
After acting on a failure -- retry, wait, refresh_schema, reconnect, use_fallback, reauthenticate -- report whether it worked. Every recommendation others get is built from these. Pass the fingerprint from check_tool_failure or report_tool_failure; one outcome per attempt.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What you tried, e.g. 'refresh_schema' ([a-z0-9_.-]). |
| fingerprint | string | yes | From check_tool_failure or report_tool_failure (32 hex chars). |
| reporter_id | string | – | Optional stable agent id; hashed, never stored raw. |
| successful | boolean | yes | True when the action resolved the failure. |
No output schema declared.
No examples provided.
report_tool_failure Report a failed tool call to the network ~304
Report a failed tool/API/MCP call so others can recognise it; call after a failure, alongside check_tool_failure. PRIVACY: this is a shared network. Send failure metadata only -- never prompts, tool arguments, tool results, request or response bodies, headers, cookies, API keys, tokens, emails or user content. Error text is normalized server-side and the raw string discarded. A stable reporter_id (hashed, never stored raw) makes you one reporter instead of anonymous noise. Writes are rate limited per client.
| Name | Type | Req | Description |
|---|---|---|---|
| error_code | string | – | Protocol/vendor code, e.g. '422'. |
| error_message | string | – | Error text. Normalized before storage; no secrets please. |
| error_type | string | – | Short failure class, e.g. 'validation_error'. |
| latency_ms | integer | – | Observed call latency in milliseconds. |
| operation | string | yes | The tool or endpoint as the server names it, e.g. 'create_issue', not 'mcp__github__create_issue'. |
| reporter_id | string | – | Optional stable identifier for your agent. Salted and hashed on arrival; never stored raw. |
| schema_hash | string | – | Short hash of the tool schema used. |
| service | string | yes | The MCP server's own name (serverInfo.name) or the API host, e.g. 'api.github.com'. Not your client's local alias. |
| version | string | – | Version of the service/tool. |
No output schema declared.
No examples provided.
report_tool_success Report a successful tool call to the network ~176
Report that a call SUCCEEDED. Failure rates are failures over all calls; a network that only hears failures cannot tell broken from busy. No error data -- service, operation, version, latency.
| Name | Type | Req | Description |
|---|---|---|---|
| latency_ms | integer | – | Observed call latency in milliseconds. |
| operation | string | yes | The tool or endpoint as the server names it, e.g. 'create_issue', not 'mcp__github__create_issue'. |
| reporter_id | string | – | Optional stable agent id; hashed, never stored raw. |
| schema_hash | string | – | Short hash of the tool schema used. |
| service | string | yes | The MCP server's own name (serverInfo.name) or the API host, e.g. 'api.github.com'. Not your client's local alias. |
| version | string | – | Version of the service/tool. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/failshare MCP server?
io.github.CloudCorpRecords/failshare runs locally as an npm package, launched with npx -y @reneturcios/failshare. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/failshare
claude mcp add cloudcorprecords-failshare -- npx -y @reneturcios/failshare
What is the io.github.CloudCorpRecords/failshare MCP server?
io.github.CloudCorpRecords/failshare is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/failshare. Shared failure knowledge for agents: check known tool failures, report failures and outcomes. This page covers its npm package (@reneturcios/failshare).
Is the io.github.CloudCorpRecords/failshare MCP server safe to use?
io.github.CloudCorpRecords/failshare scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.CloudCorpRecords/failshare MCP server expose?
io.github.CloudCorpRecords/failshare exposes 4 tools: check_tool_failure, report_tool_failure, report_tool_success, report_recovery_outcome. Their descriptions and schemas cost roughly 978 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/failshare MCP server still maintained?
io.github.CloudCorpRecords/failshare is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.CloudCorpRecords/failshare MCP server under?
io.github.CloudCorpRecords/failshare declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.