Skip to main content
Glama

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

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

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

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

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