dokimo-mcp
Server Details
Verify AI-agent revenue: recompute a Merkle proof and check it against an on-chain anchor.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- ypratap11/dokimo-mcp
- GitHub Stars
- 0
- Server Listing
- dokimo-mcp
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 3 tools
The three tools target distinct stages: discovery (agent card), local proof recomputation, and networked anchor verification. The only mild overlap is that both recompute_merkle_root and verify_evidence_package recompute a Merkle proof, but the descriptions explicitly frame one as offline-only and the other as the anchored check, so an agent can choose correctly.
All names are snake_case and two follow a clear verb_noun pattern (recompute_merkle_root, verify_evidence_package). dokimo_agent_card deviates as a bare noun phrase with a server prefix, but it is still readable and unambiguous.
Three tools is on the thin side but each maps to a genuinely distinct capability (discovery, local check, remote check) with no filler. The surface is well-scoped to a narrow Merkle-anchor verification service.
The core verification lifecycle is covered, but there are notable gaps: no tool to fetch or construct an evidence package, no batch/multi-record verification (explicitly one record only), and no way to inspect anchors or record status. Agents can work around these by supplying packages themselves, but coverage is partial.
Available Tools
3 toolsdokimo_agent_cardARead-onlyIdempotentInspect
Fetch Dokimo's public A2A agent card — the discovery document describing what it can verify (skills, endpoints, supported A2A versions).
Inputs: no named parameters.
recompute_merkle_rootARead-onlyIdempotentInspect
Recompute a dokimo-merkle-v1 root locally — no network call, no anchor check.
Hash ``leaf`` in the leaf domain (H(0x00 ‖ leaf)) and replay ``proof_path`` —
a list of ``[sibling_hash, side]`` where side is "L" or "R" — hashing internal
nodes as H(0x01 ‖ left ‖ right). Compare the returned root to the ``root`` in an
evidence package yourself; if it differs, the package was tampered with.
Returns ``{recomputed_root, merkle_scheme, steps}``.
Inputs: leaf (required), proof_path (required).
verify_evidence_packageARead-onlyIdempotentInspect
Ask Dokimo to check one record of an evidence package against the on-chain anchor.
Sends the package to Dokimo's public A2A endpoint, which recomputes the Merkle
proof AND checks the anchored commitment (root + rule version, plus the close
summary for v2) against the anchor on Base. The verdict is Dokimo's answer and
is not signed. ``package`` must contain: ``leaf`` (str), ``root`` (str),
``proof_path`` (list of [sibling_hash, "L"|"R"]), and
``rule_version_commitment`` (str); for a v2 close also ``summary`` and
``binding``; ``close_id`` is optional/echoed.
Returns the verdict: ``{verified, checks:{recompute, onchain_anchor,
rule_version_bound}, ...}``. ``verified`` is true only if the proof recomputes
AND the commitment is anchored on-chain. It covers this one record only.
Inputs: package (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Check an AI agent you did not build: is it who it claims, inside its mandate, and what's its record
One-stop claim verification for AI agents: verdicts with confidence, evidence, signed receipts.
Proof-of-spend and reserve checks for AI agents: receipts, spend audit, NAV, reconciliation.
Notary for AI agents: seal fingerprints, verify proofs, check mandates. Anchored in Bitcoin.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables 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.3MIT
- FlicenseNot gradedqualityDmaintenanceCryptographically anchored, tamper-evident evidence receipts for AI agents — verified run receipts, existence-at-time proofs, and cited answers from an anchored public record. Remote MCP with proof-gated settlement; attests existence and integrity, never truth.-
- AlicenseNot gradedqualityNot gradedmaintenanceEnables agents and audit systems to hash execution logs into tamper-proof Merkle trees, compute cryptographic inclusion proofs, and verify audit-trail integrity on demand. It runs as a zero-dependency Python MCP server (stdio JSON-RPC) or as an importable module, exposing anchoring, proof generation, and integrity verification over local agent activity records.MIT
- AlicenseNot gradedqualityBmaintenanceTrust layer for agent work: verify the artifact an AI agent produced, meter what the run actually cost, and keep the agent inside its mandate. Signed receipts verify offline. 20 checks/day free, then 0.005 USDC per call or $49 per environment per month. Locales: en, hi.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.