Skip to main content
Glama

Related Servers

Alternatives to mcp-diet

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      A firewall proxy for any stdio MCP server: every tool call is checked against a restrict-only policy before it runs, with encoded-argument inspection, taint tracking so private data can't leave, tool pinning, and a write-ahead audit log.
      1
      -
    • A
      license
      A
      quality
      B
      maintenance
      Stdio policy proxy that runs in front of another MCP server: blocks paths outside allowed folders, enforces tool allowlists, asks on the terminal before risky calls, masks secrets in server output and writes a hash-chained audit log.
      16
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Dependency-free, locally sandboxed MCP stdio server. Tools run as WASM inside a capability-based WASI sandbox (wasmtime); every tools/call is attested with cost/policy and signed manifests fail-closed.
      3
      67 PyPI
      48
      Business Source 1.1
    • A
      license
      Not graded
      quality
      D
      maintenance
      A local-first stdio proxy for MCP servers that traps destructive tool calls and holds them for manual commit or discard, preventing accidental mutations.
      AGPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      Local execution gate and stdio MCP proxy for AI agents, with tool policies, expiring leases, approvals and operator kill. Starts with two read-only setup tools; protection requires a trusted downstream server and private operator configuration. Not an OS sandbox. Apache-2.0.
      2
      162 PyPI
      6
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      A fail-closed policy boundary that translates local stdio MCP clients to authenticated Streamable HTTP servers, enforcing allowlists or read-only modes and redacting credentials from audit trails.
      Apache 2.0

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool maps to a clearly different action: analysis of tool definitions, reading spill files, redacting secrets, and inspecting runtime status. There is no plausible overlap — an agent can pick the right tool from the name alone, and the descriptions reinforce distinct resource/action pairs.

    Naming Consistency5/5

    All four tools share the `mcp_diet_` server prefix followed by a snake_case verb_noun pattern (analyze_tools, read_spill, redact_text, status). The one slight deviation is `status` (noun-only), but it is unambiguous and predictable within the set.

    Tool Count4/5

    Four tools is well-scoped for a narrow utility server covering analysis, spill reading, redaction, and status. It is on the thin side — the surface could support a policy/configuration tool — but no tool feels redundant or out of place.

    Completeness4/5

    The lifecycle is largely covered: analyze computes savings, read_spill retrieves oversized output, redact_text handles secret leakage, and status reports runtime config. The main gap is the absence of a tool to set or apply mcp-diet policies/config, so agents can inspect and analyze but not mutate configuration.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues