SelfHeal MCP server
Self-healing proxy for MCP servers with retry, circuit breaker, and observability
0 stars43 downloads/wk
Reviews
Write oneNobody has reviewed SelfHeal MCP yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
SelfHeal MCP tools (8, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
circuit_resetReset a circuit breaker back to closed (healthy). Use after fixing the underlying issue.
circuit_statusCheck the health status of a target. Returns circuit state, failure count, and cooldown.
metricsGet observability metrics — success rates, latency, top errors, breakdown by tool and target.
recent_errorsGet the most recent failed calls with full error details and retry logs.
selfheal_circuitsGet circuit breaker status for all proxied targets
selfheal_metricsGet SelfHeal proxy metrics — success rates, latency, top errors
selfheal_recent_errorsGet recent failed tool calls with error details
wrap_callwrite actionExecute a function call with retry, circuit breaker, and metrics.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan13 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 62 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How SelfHeal MCP compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- Tools
- 8
- the typical server has 7
- Tools that change things
- 13%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 43
- more than 35% of 12,191 servers with a package
What its tools let an agent do: 7 read · 1 change
Install SelfHeal MCP in Claude Code, Cursor or VS Code
Runs npx -y selfheal-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add selfheal-mcp -- npx -y selfheal-mcp
What the publisher says
From the SelfHeal MCP repository's README, as published. We do not edit it. Read it on GitHub
SelfHeal MCP
Self-healing proxy for MCP servers. Wraps any MCP tool call with automatic retry, circuit breaker protection, and call observability.
Your AI agents stop breaking on flaky APIs.
One-click install: Install on MCPize | npx selfheal-mcp
Features
- Retry with backoff — Exponential backoff + jitter on transient failures (5xx, timeouts, rate limits)
- Circuit breaker — Per-target circuit breaker stops hammering dead services
- Call metrics — Success rates, latency, error frequency, broken down by tool and target
- Proxy mode — Wrap any existing MCP server transparently
- Zero config — Works standalone out of the box, config file for proxy mode
Quick Start
Standalone Mode
Add to your Claude Desktop / Claude Code config:
{
"mcpServers": {
"selfheal": {
"command": "npx",
"args": ["-y", "selfheal-mcp"]
}
}
}Then use wrap_call to make any HTTP request with self-healing:
Use the wrap_call tool to GET https://api.example.com/data with target "example-api"Proxy Mode
Create selfheal.config.json:
{
"mode": "proxy",
"targets": [
{
"name": "my-server",
"transport": "streamable-http",
"url": "https://my-mcp-server.com/mcp"
}
]
}{
"mcpServers": {
"selfheal": {
"command": "npx",
"args": ["-y", "selfheal-mcp"],
"env": {
"SELFHEAL_CONFIG": "/path/to/selfheal.config.json"
}
}
}
}All tools from my-server are re-exposed with self-healing built in.
Tools
Proxy Mode Adds
Configuration
Environment Variables
How It Works
Agent → SelfHeal MCP → [Retry + Circuit Breaker] → Target API/MCP Server
↓
Metrics Collector- Request arrives — Agent calls a tool
- Circuit check — If target has failed too many times, reject immediately
- Execute with retry — Try the call, retry on transient errors with exponential backoff
- Record metrics — Log success/failure, duration, attempts
- Update circuit — Track consecutive failures per target
Install
MCPize (Recommended)
One-click install with managed hosting: Install on MCPize
npm
npx selfheal-mcpPyPI
Not applicable — this is a TypeScript server. For Python alternatives, see LeadEnrich MCP.
License
MIT — Built by Freedom Engineers
Related
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
SelfHeal MCP: common questions
- Is SelfHeal MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the SelfHeal MCP safety report
- How do I install SelfHeal MCP?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does SelfHeal MCP need an API key?
- No secret keys are declared. It reads 3 settings from the environment.
- Is SelfHeal MCP maintained?
- The last commit was 99 days ago (2026-07-27). The latest release is v0.1.1.
- How does SelfHeal MCP compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); tools 8 (the typical server has 7); tools that change things 13% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.