Skip to main content
Glama

Related Servers

Alternatives to deusproof-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      A
      quality
      B
      maintenance
      Stamp, upgrade, and verify Bitcoin timestamps via AI agents using the OpenTimestamps protocol. No API keys required.
      9
      80 npm
      3
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to certify documents, prove agreements, and verify counterparty claims with on-chain receipts on Hedera Hashgraph. Provides tools for document certification, two-party attestation, and agent registration with zero-config setup.
      6
      57 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables on-chain attestation of any content onto the DigiByte blockchain, providing permanent, timestamped, tamper-evident proofs. Allows AI agents to notarize their outputs or verify attestations using only the blockchain.
      7 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to create cryptographically verifiable receipts of their delegated work, with capabilities for multi-party approval and offline verification.
      11
      84 npm
      Apache 2.0

    TDQS

    A3.9/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: identity (claim_authorship), recording (certify_creation vs notarize_hash), lookup (verify_certificate, get_agent_passport, prior_art_search), governance (council_ballot/council_vote), and cards (seal_agent_card/agent_card_history). The only soft overlaps are certify_creation vs notarize_hash (both timestamp things) and birth_certificate vs get_agent_passport (both return agent metadata), but the descriptions clearly draw the lines: public authorship record vs private hash-only proof, and your own entry with key-holder info vs public stats.

    Naming Consistency4/5

    The dominant pattern is verb_noun (claim_authorship, certify_creation, notarize_hash, seal_agent_card, verify_certificate, get_agent_passport, council_vote) with a clean council_ballot/council_vote pairing. A few noun-first identifiers (birth_certificate, prior_art_search, agent_card_history, council_ballot) deviate, but they are readable, domain-conventional, and not chaotic.

    Tool Count5/5

    Eleven tools sit squarely in the well-scoped range for a provenance/notarization registry. Each tool covers a distinct capability (identity, recording, search, verification, governance, agent cards) and none feels like filler.

    Completeness4/5

    The surface covers the full lifecycle: identity claim, creation/private notarization, prior-art search, verification, passport read, and agent-card sealing plus history. Minor gaps remain (no listing of an agent's own certificates, no revocation/retraction path), but an append-only ledger makes revocation largely out of scope and agents can work around the rest.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data