Skip to main content
Glama
Rohan Shield

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
      Not graded
      maintenance
      Enables real-time injection fuzzing, exfiltration canary detection, least-privilege tool sandboxing, and cryptographic audit proofs for untrusted prompts, RAG context, and agent actions over MCP.
      7
      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.
      3
      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
      -

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool maps to a clearly distinct action/resource: executing a confidential state transition, verifying a commitment digest, reading the current ledger state, and listing transaction history. The boundary between reading ledger state and listing transaction history is clear from the descriptions.

    Naming Consistency5/5

    All tools use the same rohan_ prefix followed by a consistent verb_noun pattern (execute_handshake, get_transaction_history, verify_commitment, get_ledger_state). The convention is predictable throughout.

    Tool Count5/5

    Four tools is well-scoped for a focused blockchain protocol server, and each tool has a clear, non-redundant role. There is no padding or extreme thinness given the domain.

    Completeness4/5

    The surface covers core operations: execute, verify, read state, and list history. Minor gaps exist, such as direct transaction/receipt lookup by hash or richer protocol query operations, but agents can likely work around them via history and state reads.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues