Skip to main content
Glama
CCS Verifier MCP Server

CCS Verifier MCP Server

Related Servers

Alternatives to CCS Verifier MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP hosts to verify agent spending mandates and receipts, providing stateless tools for authorization, chain verification, credential verification, and DID resolution.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server enables agents to issue and verify Ed25519-signed receipts over artifacts, binding an agent, task and file hash so anyone can confirm offline that a delivered file is unchanged. It exposes two tools, issue_receipt and verify_receipt, requiring no account, chain or network access.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Append-only evidence receipts for AI records: seal, verify, cite, chain-check, anchor status. A seal proves a record existed at a time, not that its contents are true. Five tools over stdio with npx -y apex-psi-mcp — no account, no key, verification free forever.
      5
      69 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Issue and verify signed receipts for agent actions, enabling durable, independently checkable proof of policy decisions. Supports offline verification via get_keyset and verify_receipt tools without an account.
      0
      Inno Setup
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for offline verification of signed artifacts — receipts, manifests, and audit bundles. MIT licensed, works without accounts or API calls. Tools: self_test, verify_receipt, verify_bundle, explain_artifact.
      4
      94 npm
      6
      Apache 2.0

    TDQS

    A3.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: verifying a receipt, retrieving verifier metadata, and generating a test receipt. There is no meaningful overlap or risk of misselection.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern: verify_receipt, get_verifier_info, generate_test_receipt. The convention is predictable and readable.

    Tool Count5/5

    Three tools are well-scoped for a focused CCS verifier service, and each earns its place in the workflow. The count is appropriately minimal rather than thin.

    Completeness4/5

    The core verification lifecycle is covered: verify, inspect verifier info, and generate test data. Minor gaps like batch verification or receipt parsing are not present but can be worked around for most use cases.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues