dokimo-mcp
by ypratap11
README.md
# dokimo-mcp
<!-- mcp-name: io.github.ypratap11/dokimo-mcp -->
**Give an AI agent the ability to verify another agent's revenue claims.**
An [MCP](https://modelcontextprotocol.io) server exposing [Dokimo's](https://dokimo.augaster.com)
trustless evidence verification as tools any MCP client (Claude Desktop, IDE
agents, custom agents) can call. It's the "agent that audits agents" — as tools.
Live, clickable version of what these tools do:
**https://dokimo.augaster.com/agent-audits-agents.html**
> This is a thin, self-contained **client**: it calls Dokimo's public endpoints and
> implements the public `dokimo-merkle-v1` hashing scheme. It contains no proprietary
> code. MIT-licensed.
## Tools
| Tool | What it does | Network? |
|---|---|---|
| `recompute_merkle_root(leaf, proof_path)` | **Trustless local recompute** — hash a leaf under `dokimo-merkle-v1` and replay the proof path to a root, with **no network and no trust in anyone**. Compare it to a package's claimed `root` yourself. | none |
| `verify_evidence_package(package)` | **Full verification** via Dokimo's public A2A endpoint: recompute **and** check the compound commitment (root + rule version) against the **on-chain anchor on Base**. Returns `verified: true` only if both hold. | Dokimo A2A |
| `dokimo_agent_card()` | Fetch Dokimo's public A2A agent card — what it can verify. | Dokimo |
**Verification model:** there is no path to `verified: true` without (1) the
caller's `(leaf, proof_path)` recomputing to the claimed `root`, **and** (2) the
compound commitment of `(root, rule_version_commitment)` being anchored on-chain.
Tamper one byte → recompute fails. Swap the rule version → the commitment changes
→ not anchored.
**Honest scope:** attests that a *reported* figure is reproducible and
tamper-evident against an on-chain anchor — not that any underlying business
number is "good." Non-custodial; reads public on-chain state only.
## Install & run
```bash
pip install dokimo-mcp
dokimo-mcp # runs over stdio
# or, from a clone:
pip install .
python -m dokimo_mcp
```
## Add to an MCP client
**Claude Desktop** — add to `claude_desktop_config.json`:
```json
{
"mcpServers": {
"dokimo": {
"command": "dokimo-mcp"
}
}
}
```
If `dokimo-mcp` isn't on `PATH`, use the module form:
```json
{
"mcpServers": {
"dokimo": {
"command": "python",
"args": ["-m", "dokimo_mcp"]
}
}
}
```
Then ask the agent: *"Use Dokimo to verify this evidence package"* (paste one), or
*"recompute this Merkle root and tell me if it matches."*
## Try it
The live demo page embeds a real, anchored evidence package. Fetch it and verify:
```python
import re, json, urllib.request
import dokimo_mcp as d
html = urllib.request.urlopen(urllib.request.Request(
"https://dokimo.augaster.com/agent-audits-agents.html",
headers={"User-Agent": d._UA})).read().decode()
pkg = json.loads(re.search(r"const PKG\s*=\s*(\{.*?\})\s*;", html, re.S).group(1))
print(d.verify_evidence_package(pkg)["verified"]) # True
# tamper one unit -> False
pkg["leaf"] = pkg["leaf"].replace("1001190933933115", "1001190933933116")
print(d.verify_evidence_package(pkg)["verified"]) # False
```
## Hosted / HTTP mode
The default transport is **stdio** (local use). Set `MCP_TRANSPORT=http` to serve
**MCP Streamable HTTP at `/mcp`** on `$PORT` (default 8081) with CORS — the shape
hosted platforms like [Smithery](https://smithery.ai) require. The included
`Dockerfile` + `smithery.yaml` (`runtime: container`) are set up for exactly this,
so Smithery can build and host it from this repo.
```bash
MCP_TRANSPORT=http PORT=8081 dokimo-mcp # or: docker run -p 8081:8081 <image>
```
## What is Dokimo?
Verifiable revenue infrastructure for autonomous commerce — audit-ready, independently
reproducible books for AI-agent machine payments (x402 / AP2 / Stripe), with each figure
tamper-evidently committed and anchored on-chain. https://dokimo.augaster.com
## License
MIT — see [LICENSE](LICENSE).
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