Skip to main content
Glama
rohan-protocol

Rohan Shield

Official

Related Servers

Alternatives to Rohan Shield

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that provides a guarded interface to the mem9 persistent memory backend, protecting AI agents against prompt injection, secret leakage, and memory poisoning.
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that lets AI agents call APIs without ever seeing the credentials, using a local encrypted vault and per-secret allowlist policies for HTTP requests and subprocess environment variables.
      1
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP server that lets AI agents use gated APIs without holding keys, enforcing declarative policies, injecting secrets server-side, and auditing access without content.
      2
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for end-to-end encrypted secret storage and retrieval, enabling LLM agents to fetch secrets by name via one-time URLs while keeping plaintext out of model context and logs.
      1
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables developers and AI agents to enforce per-tenant security isolation for autonomous agents by compartmentalizing memory boundaries and managing sandboxed tenant execution. It exposes this deterministic, dependency-free guard through a native MCP server that plugs into Claude Desktop, Cursor, and other MCP-compliant clients.
      8
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Secret management MCP server for AI coding agents that prevents secrets from entering the LLM context window by returning metadata only and using side-channel injection. Integrates with Bitwarden and offers hooks for auto-capture and leak prevention.
      1
      MIT

    TDQS

    B3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool in the set, there is no possibility of overlap or misselection. The tool's purpose (a zero-knowledge state transition handshake) is unambiguous and clearly bounded.

    Naming Consistency4/5

    The single name `rohan_zk_handshake` is clean snake_case with a server prefix, so there is no inconsistency. However, a lone name cannot demonstrate a predictable verb_noun pattern across the set, so it falls just short of a 5.

    Tool Count2/5

    A single tool is too thin for a blockchain/cryptographic-protocol server, which normally implies proving, verifying, querying state, and inspecting transactions. The operation itself is non-trivial, which keeps this above the worst score.

    Completeness2/5

    The surface exposes only the handshake/prove operation, with no verification, state-read, or agreement-lifecycle counterparts. An agent has no way to check a proof result, retrieve state, or handle the other half of the interaction, creating dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues