Skip to main content
Glama

Related Servers

Alternatives to mcp-pin

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      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
      A
      maintenance
      Supply-chain gate for AI agent skills and MCP servers: poison-scan tool definitions, hash-pin the vetted set into a lock file and verify drift in CI. truecopy-mcp is a drop-in stdio proxy that filters a live server's tools/list down to its pinned, unmodified, unpoisoned tools.
      2
      91 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP security firewall (stdio): vet advertised tool definitions through static-scan → threat-feed → origin → pinning before they reach the model. Zero npm runtime deps. No secrets.
      9
      476 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A transparent MCP proxy that independently re-verifies tool-call claims instead of trusting them, paired with devmcp — the git/CI server it's proven against.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A transparent MCP stdio proxy that sits between an agent client and a real MCP server, intercepting tools/call requests to enforce runtime guardrails derived from the same YAML rules used for CI regression testing. It blocks forbidden, out-of-whitelist, looping, or non-idempotent tool invocations with JSON-RPC errors and writes every decision to an audit log.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Zero-dependency stdio MCP server for token-aware prompt version diffs. Compare prompts or files and get machine-readable token delta reports with confidence labels.
      MIT

    TDQS

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct scope: local pinned servers (my_servers), details of a pending local change (change_summary), public registry lookup (server_status), and setup instructions (how_to_protect). Although my_servers and server_status both concern server changes, their local-versus-public scopes are explicitly separated in the descriptions, leaving no real ambiguity.

    Naming Consistency4/5

    All tools share the mcp_pin_ prefix and snake_case, so the namespace and style are consistent. The suffixes are a mix of noun phrases (change_summary, server_status), a possessive (my_servers), and a how-to phrase (how_to_protect), which deviates from a pure verb_noun pattern but remains readable and predictable.

    Tool Count5/5

    Four tools is well-scoped for a pinning/protection server. Each tool earns its place, and the design intentionally delegates approval, review, and full diff inspection to the CLI rather than bloating the MCP surface.

    Completeness4/5

    The surface covers discovery, pending-change explanation, public log checks, and setup guidance, forming a coherent lifecycle. Approval/review and the actual changed text are intentionally left to terminal commands, a reasonable gap an agent can work around, though there is no MCP-native way to inspect the changed content.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues