# io.github.ypratap11/dokimo-mcp (remote · dokimo.augaster.com)

Verify AI-agent revenue: recompute a Merkle proof and check it against an on-chain anchor.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `dokimo.augaster.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/ypratap11-dokimo-mcp/dokimo.md), [page](https://verifymcp.io/servers/ypratap11-dokimo-mcp/dokimo)

## Channel facts

- Endpoint: `https://dokimo.augaster.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 533 tokens (~177/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.ypratap11/dokimo-mcp server?

io.github.ypratap11/dokimo-mcp is a hosted endpoint at https://dokimo.augaster.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ypratap11-dokimo-mcp 'https://dokimo.augaster.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ypratap11-dokimo-mcp": {
      "url": "https://dokimo.augaster.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ypratap11-dokimo-mcp": {
      "type": "http",
      "url": "https://dokimo.augaster.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ypratap11-dokimo-mcp]
url = "https://dokimo.augaster.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ypratap11-dokimo-mcp": {
      "type": "remote",
      "url": "https://dokimo.augaster.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ypratap11-dokimo-mcp --url 'https://dokimo.augaster.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ypratap11-dokimo-mcp:
    url: "https://dokimo.augaster.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ypratap11-dokimo-mcp": {
      "Transport": "http",
      "Url": "https://dokimo.augaster.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ypratap11-dokimo-mcp -t streamable-http -u 'https://dokimo.augaster.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ypratap11-dokimo-mcp": {
      "type": "http",
      "url": "https://dokimo.augaster.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 67, +10)

- [security improvement] Transport: fail → pass

### 2026-09-15 (score 57, −9)

- [security regression] Transport: pass → fail

### 2026-09-13 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-10 (score 64)

First indexed and scored.

## MCP tools (3)

### `recompute_merkle_root` (~246 tokens)

Trustlessly recompute a dokimo-merkle-v1 root — LOCAL, no network, no trust.

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

Input parameters:

- `leaf` (string, required): The raw leaf value (e.g. a JSON string like '{"k":"total_assets","v":"..."}'). Hashed in the leaf domain as H(0x00 ‖ leaf).
- `proof_path` (array, required): Ordered Merkle proof path: a list of [sibling_hash_hex, side] pairs, where side is "L" if the sibling is on the left or "R" if on the right. Empty list for a single-leaf tree.

### `verify_evidence_package` (~245 tokens)

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. ``package`` must contain: ``leaf`` (str), ``root`` (str),
    ``proof_path`` (list of [sibling_hash, "L"|"R"]), and
    ``rule_version_commitment`` (str); ``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.

Input parameters:

- `package` (object, required): The Dokimo evidence package to verify. Required keys: 'leaf' (str), 'root' (str), 'proof_path' (list of [sibling_hash, "L"|"R"]), and 'rule_version_commitment' (str). 'close_id' (str) is optional and…

### `dokimo_agent_card` (~42 tokens)

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ypratap11-dokimo-mcp/dokimo#diagnostics

## Score history

- 2026-09-20: 69
- 2026-09-19: 68
- 2026-09-18: 68
- 2026-09-17: 67
- 2026-09-16: 67
- 2026-09-15: 57
- 2026-09-14: 66
- 2026-09-13: 66
- 2026-09-12: 65
- 2026-09-11: 65
- 2026-09-10: 64

## Common questions

### What is the io.github.ypratap11/dokimo-mcp server?

io.github.ypratap11/dokimo-mcp is listed in the public MCP registry as io.github.ypratap11/dokimo-mcp. Verify AI-agent revenue: recompute a Merkle proof and check it against an on-chain anchor. This page covers its hosted endpoint (https://dokimo.augaster.com/mcp).

### Is the io.github.ypratap11/dokimo-mcp server safe to use?

io.github.ypratap11/dokimo-mcp scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.ypratap11/dokimo-mcp server expose?

io.github.ypratap11/dokimo-mcp exposes 3 tools: recompute_merkle_root, verify_evidence_package, dokimo_agent_card. Their descriptions and schemas cost roughly 533 tokens of context every time the server is loaded.

### Does the io.github.ypratap11/dokimo-mcp server require authentication?

No. We connected to io.github.ypratap11/dokimo-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.ypratap11/dokimo-mcp server still maintained?

io.github.ypratap11/dokimo-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://dokimo.augaster.com/mcp
- Repository: https://github.com/ypratap11/dokimo-mcp
- Website: https://dokimo.augaster.com/
- Changelog RSS feed: https://verifymcp.io/servers/ypratap11-dokimo-mcp/dokimo.xml
- Changelog JSON feed: https://verifymcp.io/servers/ypratap11-dokimo-mcp/dokimo.json
- HTML version of this page: https://verifymcp.io/servers/ypratap11-dokimo-mcp/dokimo