Skip to main content
Glama
CSOAI-ORG

Trust Chain MCP

by CSOAI-ORG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Trust Chain MCP

No user-submitted related servers found.

    Related Servers

    • swt3-mcp

      tenova-labs
      A
      license
      Not graded
      quality
      A
      maintenance
      Cryptographic AI governance and compliance attestation. 75 tools across 80 regulatory frameworks including EU AI Act, NIST AI RMF, NERC CIP, 3GPP R19, OWASP MCP Top 10, CMMC, and SR 11-7. Full OWASP MCP Top 10 coverage. Witness Middleware for zero-code transport-layer compliance. Runtime containment attestation. Distillation provenance. Incident lifecycle chains.
      459 npm
      Apache 2.0

    • 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

    • 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
      39 npm
      MIT
    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

    B3.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a distinct and clear purpose: creating a trust anchor, adding attestations, computing trust score, revoking trust, and verifying the chain. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, such as 'create_trust_anchor' and 'verify_chain'. The naming is predictable and uniform.

    Tool Count5/5

    With 5 tools, the server is well-scoped for the domain of trust chain management. Each tool covers a fundamental operation without redundancy or excessive granularity.

    Completeness4/5

    The set covers core CRUD and lifecycle operations for trust anchors and attestations, including creation, attestation, scoring, revocation, and verification. However, it lacks list/read endpoints to retrieve existing anchors or attestations, which could be a minor gap in some workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources