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

    • @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
      47 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.
      19 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

    • agent-verification-api

      nexus-mcp-infra
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables users to verify that an AI agent is who it claims to be by combining domain verification, agent-card checks, and a live MCP handshake, with paid requests handled via x402 on Base Sepolia testnet.
      -
    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.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: recompute locally, verify against on-chain anchor, and fetch discovery metadata. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (recompute_, verify_, dokimo_agent_card), which is predictable and readable.

    Tool Count5/5

    With only 3 tools, the server is tightly scoped to its specific verification workflow. Each tool is necessary and earns its place.

    Completeness4/5

    The surface covers local recompute, full verification, and discovery. The only minor gap is the lack of a tool to fetch or construct evidence packages, but that is outside the core verification workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources