Skip to content

Verifyum MCP server

Which MCP servers are Verifyum's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-25

← Back to Verifyum

Whose server it is
  • Registry namecom.verifyum/mcpverified in the MCP registry

The registry name sits under verifyum.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-25
  • Stateanswerschecked 2026-10-25
  • Tools3
  • Server calls itselfverifyum-mcp-endpoint
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 528 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 10, the first on 2026-10-25
  • INITE MCP score100 of 100answers 100 · definitions 100 · context 100 · connects 100
  • Answered100% of days10 of 10 daily checks
  • Median first answer510 ms
  • Space in an agent's context≈ 618 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • not sure · prove a file existed unchanged by a given time
  • not sure · timestamp source archives and software release bundles
  • not sure · seal an AI agent's decision record for later audit

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-25
  • verifyum_get_proof

    Read the lifecycle state of one Verifyum proof (queued, submitted, finalized or failed). Input is a public proof ID only.

  • verifyum_verify_public_proof

    Check a finalized proof: metadata consistency, the exact 128-byte memo, and the Ed25519 service signature against the published key registry. The response also contains the exact Solana RPC call and expectations so the caller can…

  • verifyum_anchor_commitment

    Submit one locally calculated Verifyum version 2 commitment. Accepts only the commitment and an idempotency key. Never send a file, filename, raw file hash, nonce or private manifest. The caller must hash the file and build the private…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "verifyum": {
      "type": "http",
      "url": "https://api.verifyum.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http verifyum https://api.verifyum.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.verifyum.com/mcp as a custom connector in the settings.

OpenAPI spec

5 paths, read 2026-10-25. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.