Skip to main content
Glama
receipts-compliance-mcp-mit

receipts-compliance-mcp-mit

Related Servers

Alternatives to receipts-compliance-mcp-mit

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables offline verification of Ed25519-signed AI-agent receipt bundles and turns them into auditor-ready Markdown evidence reports covering EU AI Act Annex IV, ISO/IEC 42001, ISO/IEC 23894, NIST AI RMF, SOC 2, GDPR, HIPAA and the EU CRA. Also signs AI constitutions and audits bundles against them, without uploading anything.
      11
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Provides tools to issue, verify, and export cryptographically signed receipts for AI agent actions, enabling tamper-proof audit trails for compliance with regulations like the EU AI Act.
      4
      53 npm
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents and builders to run governance assessments including A³ scorecards, evidence-chain templates, compliance checklists, passport lookup, privacy/credential scanning, and doctrine knowledge routing, with traceable audit-ready outputs. It provides local, zero-dependency tools for AI governance self-assessment and registration readiness.
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and builders to run local, audit-traceable governance assessments, including an A³ scorecard, ISO/IEC 42001 and NIST evidence templates, compliance checklists, passport lookup, and sensitive-text screening.
      MIT
    • 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

    TDQS

    A4/5.0

    Scored across 11 tools

    Disambiguation4/5

    Each build_* tool targets a named, distinct regulatory framework (Annex IV, ISO 42001, NIST AI RMF, SOC 2, GDPR DPIA, HIPAA, ISO 23894, EU CRA), so selection is mostly clear from the name alone. The only real friction is the cluster of AI-risk/governance reports (build_iso_23894 vs build_nist_ai_rmf, build_annex_iv vs build_iso_42001), where an agent must read descriptions to pick the right one.

    Naming Consistency5/5

    All tools are snake_case verb_noun with a small set of verbs (verify_, create_, build_) used uniformly. The pattern is predictable: build_<framework> for report generation, verify_/create_ for the manifest and constitution primitives.

    Tool Count5/5

    11 tools sits squarely in the well-scoped range. Each build_* tool corresponds to a genuinely different compliance artifact rather than being a redundant variant, and the two non-build tools (verify_manifest, create_constitution) anchor the receipt/constitution lifecycle.

    Completeness3/5

    The report surface is broad, but the underlying receipt lifecycle has notable gaps: there is no create_receipt or list/get_receipt, no verify_constitution or verify_receipt equivalent, and verify_manifest explicitly does not check the ML-DSA-65 half of v3 signatures. Agents can build reports but have limited ability to inspect, verify, or manage the receipt sets and constitutions they depend on.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues