Skip to main content
Glama

Related Servers

Alternatives to RugSnare

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      C
      maintenance
      Enables developers to enforce versioned data contracts for MCP tool schemas, with additive-only evolution checked in CI, SHA-256 pinning against rug pulls, and signed handles instead of protocol sessions.
      4
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Stop MCP servers from rug-pulling your AI agent. A lockfile + runtime reference monitor for MCP tools.
      2
      Apache 2.0
    • 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
      C
      maintenance
      An MCP server that exposes nine local-first contract-ops CLIs as tools for contract extraction, linting, comparison, conversion, template vaults, and signed-contract vaults, with signing operations strictly human-gated.
      30 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      A local stdio proxy that pins every MCP tool definition when you approve a server and blocks the session with a diff if a description, schema or annotation changes later. A deterministic hash compare (RFC 8785 + SHA-256), with no model in the loop.
      4
      34 npm
      3
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP security trust layer. Continuously monitors 800+ MCP packages on npm for install scripts, command injection, hardcoded secrets, capability drift, and publisher posture. Ships a GitHub Action policy gate for PR-level allow/warn/block decisions. 5 MCP tools, no API key required.
      8
      26 npm
      1
      MIT

    TDQS

    B3.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct targets: drift_feed_status queries the public RugSnare drift-feed, while pins_report queries the local project's pin store. Their descriptions make the different data sources explicit, so an agent should not confuse them.

    Naming Consistency4/5

    Both tool names use consistent snake_case and are noun-oriented read-only report names. However, the pattern is not a uniform verb_noun convention, and the mix of 'status' versus 'report' suffixes is a minor stylistic inconsistency.

    Tool Count3/5

    Two tools is thin for a server named RugSnare that appears to cover MCP server drift monitoring and pin management. The count is not extreme, but it feels borderline for the likely domain.

    Completeness2/5

    Both tools are read-only reporting operations, leaving no way to pin/unpin servers, approve/unapprove tools, or otherwise manage the pin store. For a drift and pinning domain, these are significant gaps that would cause agents to hit dead ends for core lifecycle actions.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive