SelfHeal MCP
NPM · SELFHEAL-MCP
Self-healing proxy for MCP servers with retry, circuit breaker, and observability
Available components
Last scanned (21 hours ago)
Scores higher than 58% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 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 211 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 419 tokens (~83/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "wrap_call" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 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
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.
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Oct 26 −1
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 21 Oct 26 −1
- Stability: pass → 0.93 functional
- 17 Oct 26 +3
- Stability: 0.77 → pass security
- 16 Oct 26 −3
- Stability: pass → 0.77 functional
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/selfheal-mcp@0.1.1
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
circuit_reset Reset Circuit Breaker ~41
Reset a circuit breaker back to closed (healthy). Use after fixing the underlying issue.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | – | Target to reset. Omit to reset all. |
No output schema declared.
No examples provided.
circuit_status Circuit Breaker Status ~43
Check the health status of a target. Returns circuit state, failure count, and cooldown.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | – | Target to check. Omit to see all targets. |
No output schema declared.
No examples provided.
metrics Call Metrics ~43
Get observability metrics — success rates, latency, top errors, breakdown by tool and target.
| Name | Type | Req | Description |
|---|---|---|---|
| windowMinutes | number | – | Time window in minutes (default: 60) |
No output schema declared.
No examples provided.
recent_errors Recent Errors ~39
Get the most recent failed calls with full error details and retry logs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of errors to return (default: 20) |
No output schema declared.
No examples provided.
wrap_call Self-Healing Function Call ~149
Execute a function call with retry, circuit breaker, and metrics. Pass a target name and the function will be retried on transient failures. Use this to wrap any unreliable external call.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Request body (for POST/PUT/PATCH) |
| description | string | yes | Human-readable description of what this call does |
| headers | object | – | HTTP headers |
| method | string | – | HTTP method (default: GET) |
| target | string | yes | Identifier for the target service (used for circuit breaker tracking) |
| timeoutMs | number | – | Timeout per attempt in ms (default: 30000) |
| url | string | – | URL to call (for HTTP targets) |
No output schema declared.
No examples provided.
How do I install the SelfHeal MCP server?
SelfHeal MCP runs locally as an npm package, launched with npx -y selfheal-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · selfheal-mcp
claude mcp add carsonroell-debug-selfheal-mcp -- npx -y selfheal-mcp
What is the SelfHeal MCP server?
SelfHeal MCP is listed in the public MCP registry as io.github.carsonroell-debug/selfheal-mcp. Self-healing proxy for MCP servers with retry, circuit breaker, and observability. This page covers its npm package (selfheal-mcp).
Is the SelfHeal MCP server safe to use?
SelfHeal MCP scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against 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 SelfHeal MCP server expose?
SelfHeal MCP exposes 5 tools: wrap_call, circuit_status, circuit_reset, metrics, recent_errors. Their descriptions and schemas cost roughly 315 tokens of context every time the server is loaded.
Is the SelfHeal MCP server still maintained?
SelfHeal MCP 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 SelfHeal MCP server under?
SelfHeal MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.