Skip to main content
Glama
carsonroell-debug

SelfHeal MCP

by carsonroell-debug
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to SelfHeal MCP

No user-submitted related servers found.

    Related Servers

    • SafeNode MCP Gateway

      sp3ak
      A
      license
      A
      quality
      A
      maintenance
      An MCP proxy that enforces policy on every tool call, blocking or flagging actions before they reach downstream MCP servers.
      1
      12 npm
      MIT

    • mcpclerk

      hishamalward
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides 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

    • mcp-policy-gateway

      mzquadri
      A
      license
      Not graded
      quality
      B
      maintenance
      Proxies 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

    • mcp-bastion

      Gowthaman90
      A
      license
      A
      quality
      A
      maintenance
      A reliability & security proxy for the Model Context Protocol (MCP) that provides self-healing connections, runtime tool-security, and compliance-mapped audit trails.
      5
      103 npm
      6
      Apache 2.0

    • proxy-mcp

      Rixmerz
      F
      license
      A
      quality
      D
      maintenance
      Universal MCP proxy server that discovers, searches, and executes tools across all configured MCP servers from a single entry point.
      7
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency3/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources