Skip to main content
Glama
ypratap11

dokimo-mcp

by ypratap11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoPort for HTTP transport when MCP_TRANSPORT=http. Defaults to 8080.8080
MCP_TRANSPORTNoTransport for the MCP server. Set to 'http' to serve MCP Streamable HTTP at /mcp on $PORT (default 8080) with CORS. The default is stdio.stdio

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
recompute_merkle_rootA

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}.

verify_evidence_packageA

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.

dokimo_agent_cardA

Fetch Dokimo's public A2A agent card — the discovery document describing what it can verify (skills, endpoints, supported A2A versions).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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