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
      39 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      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.
      6
      805 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
      B
      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

    B3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only a single tool, there is no possibility of overlap or confusion; the tool has one clear purpose. An agent cannot misselect because there is nothing else to select.

    Naming Consistency4/5

    The lone tool uses a plain noun ('weather') rather than a verb_noun pattern, but with only one tool there is no internal inconsistency to penalize. It is readable and predictable enough.

    Tool Count2/5

    A single trivial tool is far too thin for a standalone server, and the server name 'mcp-pin' gives no indication of weather functionality. One tool provides almost no surface for an agent to work with.

    Completeness2/5

    The weather domain is barely covered: only current conditions for a city, with no forecast, hourly/daily breakdown, historical data, or location lookup. This creates dead ends for most realistic weather queries.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues