SelfHeal MCP
Related Servers
Alternatives to SelfHeal MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceThis MCP server wraps agent tool calls with fault-tolerant retry logic, including adaptive exponential backoff, full jitter, 429 rate-limit backpressure handling, and circuit breaker patterns. It enables autonomous agents to execute tools reliably without frontier LLM round-trips, using a zero-dependency Python stdio JSON-RPC interface.7-
- FlicenseNot gradedqualityAmaintenanceActs as a gating proxy for MCP servers, merging tools and applying policy, verification, and audit layers.32 PyPI-
- AlicenseAqualityAmaintenanceAn MCP proxy that enforces policy on every tool call, blocking or flagging actions before they reach downstream MCP servers.131 npmMIT
- AlicenseNot gradedqualityAmaintenanceProvides a governance proxy layer for MCP servers, enforcing per-tool allowlists, human approval for write operations, quotas, secret redaction, and a hash-chained audit log of all calls.MIT
- AlicenseNot gradedqualityBmaintenanceProxies MCP traffic between a client and a downstream server to enforce runtime policies on tool declarations, call arguments, and results, including allowlisting, sandboxing, secret and egress controls, and injection detection. It also includes a deterministic benchmark for measuring which security controls stop which attacks.MIT
- FlicenseNot gradedqualityBmaintenanceEnables fault-tolerant agent tool execution with adaptive exponential backoff, full jitter, rate-limit 429 backpressure handling, and circuit breaker patterns to make AI agent calls resilient to transient failures. Plugs directly into MCP-compliant clients via JSON-RPC 2.0 stdio with zero external dependencies.7-
TDQS
Scored across 5 tools
Each tool has a clear, distinct purpose. circuit_reset and circuit_status are for circuit breaker state management, metrics for system observability, recent_errors for error inspection, and wrap_call for executing calls with resilience. There is no overlap or ambiguity between them.
The naming uses snake_case but mixes patterns: some tools start with a noun (circuit_*), some with an adjective (recent_errors), and one with a verb (wrap_call). While readable, the lack of a consistent verb_noun or noun_verb pattern reduces predictability.
With 5 tools, the server covers the essential resilience operations without being bloated. The number is appropriate for a focused self-healing utility, though a few additional tools (e.g., for configuration) could be added without harm.
The tool set covers the core lifecycle of circuit breakers, error tracking, and metrics. However, it lacks configuration tools for setting circuit breaker parameters or managing targets, which might be needed for full autonomy.