dokimo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP transport when MCP_TRANSPORT=http. Defaults to 8080. | 8080 |
| MCP_TRANSPORT | No | Transport 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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recompute_merkle_rootA | Trustlessly recompute a dokimo-merkle-v1 root — LOCAL, no network, no trust. Hash Returns |
| verify_evidence_packageA | Fully verify a Dokimo evidence package against the LIVE on-chain anchor. Sends the package to Dokimo's public A2A endpoint, which recomputes the Merkle
proof AND checks the compound commitment (root + rule version) against the
anchor on Base. Returns the verdict: |
| 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
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
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.
All tool names follow a consistent verb_noun snake_case pattern (recompute_, verify_, dokimo_agent_card), which is predictable and readable.
With only 3 tools, the server is tightly scoped to its specific verification workflow. Each tool is necessary and earns its place.
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.