Skip to main content
Glama
CSOAI-ORG

Agent Compliance Passport MCP

by CSOAI-ORG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Agent Compliance Passport MCP

No user-submitted related servers found.

    Related Servers

    • PiQrypt MCP Server

      PiQrypt
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to sign decisions with post-quantum cryptographic proofs and maintain secure audit trails for compliance. It provides tools for stamping events, verifying chain integrity, and exporting audit data across industries like finance and healthcare.
      4
      30 npm
      MIT

    • TrustAtom MCP Server

      CWNApps
      A
      license
      A
      quality
      B
      maintenance
      Provides cryptographic signing and verification for AI decisions to generate verifiable, Ed25519-signed receipts for compliance and auditing. It automatically maps AI actions to regulatory frameworks like HIPAA and SOX with high-performance, sub-3ms signing.
      4
      MIT

    • Proof Layer MCP

      World-999-Labs
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides cryptographic governance receipts for AI agents, enabling pre-execution evaluation and signed verdicts (EXECUTE/BLOCK/REVIEW/SHADOW) with offline-verifiable audit trails.
      MIT

    • @sequesign/mcp

      Sequesign
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to create cryptographically verifiable receipts of their delegated work, with capabilities for multi-party approval and offline verification.
      11
      47 npm
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: issuing passports, verifying them offline, and exchanging credentials for authorization. No overlap or ambiguity exists.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (exchange_credentials, issue_passport, verify_passport), making them predictable and easy to understand.

    Tool Count4/5

    Three tools for a passport system is reasonable, covering the core operations of issuance, verification, and credential exchange. However, it is slightly minimal for a full lifecycle.

    Completeness3/5

    The set covers creation, offline verification, and A2A handshake, but notably lacks passport revocation or listing capabilities, which are common in such systems.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources