Skip to main content
Glama
ypratap11

dokimo-mcp

by ypratap11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to dokimo-mcp

No user-submitted related servers found.

    Related Servers

    • zkVerify

      zkarchitect
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to fetch and independently verify on-chain data such as account balances and contract code hashes using Merkle proofs and ECDSA signatures, with x402 payment integration.
      3
      MIT
    • FairSeal MCP Server by fairseal-io

      FairSeal MCP Serverofficial

      fairseal-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Cryptographic receipts for AI agent decisions and game outcomes. Notarize decisions, anchor commitments on Base mainnet, and verify receipts end to end - hash content, submit anchors, check status. Ships 17 tools with both a hosted remote endpoint and a local npm package.
      2 npm
      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
      29 npm
      Apache 2.0

    • Witnessed

      medtekki
      A
      license
      Not graded
      quality
      D
      maintenance
      Verifiable action receipts for AI agents — agents sign claims locally, an independent witness countersigns and timestamps, anyone can verify offline.
      7 npm
      MIT
    • garl by Garl-Protocol

      garlofficial

      Garl-Protocol
      A
      license
      Not graded
      quality
      F
      maintenance
      Cryptographic verification for AI agent actions — ECDSA-secp256k1 signed Action Receipts anchored on Base, multi-dimensional trust vectors, capability tokens, and offline-verifiable on-chain proof. 29 tools.
      2
      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.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a clearly distinct operation: local Merkle root recomputation, remote evidence verification against an on-chain anchor, and fetching the A2A agent card. The recompute vs. verify overlap is explicitly clarified (local/no network vs. remote/anchor check), leaving no realistic misselection risk.

    Naming Consistency4/5

    Two tools follow a clean verb_noun pattern (recompute_merkle_root, verify_evidence_package), while dokimo_agent_card is a noun phrase with a vendor prefix. The deviation is minor and still predictable/readable.

    Tool Count5/5

    Three tools is well-scoped for a narrow evidence-verification server: one local primitive, one authoritative remote check, and one discovery document. Each earns its place with no filler.

    Completeness4/5

    The core verification lifecycle (recompute, anchor-check, discovery) is covered, but there is no tool to fetch the anchor/commitment data independently, list records, or batch-verify a package—minor gaps agents can work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources