Skip to main content

mcp

com.verifyum/mcpVersion 0.1.0

Privacy-preserving file proofs on Solana. Files are hashed locally. Currently free, no API key.

Status

Responds236 msAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 14:21 UTC
Latency
236 ms
Remotes responding
1 of 1
Sign-in
No sign-in
Hosting
EU hosting detected (detected, not a legal statement)
Registry data as of
Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://api.verifyum.com/mcpResponds236 ms
No sign-in

Claude Code

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

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: verifyum
Remote MCP server URL: https://api.verifyum.com/mcp

Cursor

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

VS Code

code --add-mcp '{"name":"verifyum","type":"http","url":"https://api.verifyum.com/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

3 tools

Tools of mcp
Read-only
Idempotent
Open world
verifyum_anchor_commitmentSubmit 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 manifest on its own machine first, as documented at https://verifyum.com/agents. This creates a real public transaction on Solana Mainnet. Public use is currently free and the network fee is currently paid by AI SENSE AS. That is a current service policy, not a permanent pricing guarantee. Create proofs only on clear user intent, never speculatively, in bulk, or as a hidden side effect. When retrying, reuse the exact same commitment and idempotency key.YesNoYesYes
verifyum_get_proofRead the lifecycle state of one Verifyum proof (queued, submitted, finalized or failed). Input is a public proof ID only.NoYesYesYes
verifyum_verify_public_proofCheck 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 independently confirm the transaction on chain, because this hosted check is performed by the Verifyum service itself. A finalized Verifyum anchor demonstrates that a commitment to exact file bytes existed no later than the estimated Solana block time. It does not prove authorship, ownership, legal signature validity, when the file was first created, or whether statements inside the file are true.NoYesYesYes

Details

Registry status
Active
Published
Aug 31, 2026
Updated
Aug 31, 2026
Repository
Not given
Categories
Uncategorized
GDPR
Not declared

Are you the operator? Claim this listing