Verifyum is a remote MCP server that gives an AI agent 3 tools, among them verifyum_anchor_commitment, verifyum_get_proof, verifyum_verify_public_proof. It answers at https://api.verifyum.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Privacy-preserving file proofs on Solana. Files are hashed locally. Currently free, no API key.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 mani Inputs: commitment, idempotency_key |
verifyum_get_proof | Read the lifecycle state of one Verifyum proof (queued, submitted, finalized or failed). Input is a public proof ID only. Inputs: proof_id |
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 independen Inputs: proof_id |
Every block below points at https://api.verifyum.com/mcp. Pick your client and copy.
claude mcp add --transport http verifyum https://api.verifyum.com/mcp
{
"mcpServers": {
"verifyum": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.verifyum.com/mcp"]
}
}
}{
"mcpServers": {
"verifyum": {
"url": "https://api.verifyum.com/mcp"
}
}
}{
"servers": {
"verifyum": {
"type": "http",
"url": "https://api.verifyum.com/mcp"
}
}
}{
"context_servers": {
"verifyum": {
"url": "https://api.verifyum.com/mcp"
}
}
}{
"mcpServers": {
"verifyum": {
"serverUrl": "https://api.verifyum.com/mcp"
}
}
}{
"mcpServers": {
"verifyum": {
"url": "https://api.verifyum.com/mcp"
}
}
}name: Verifyum
version: 0.0.1
schema: v1
mcpServers:
- name: Verifyum
type: streamable-http
url: https://api.verifyum.com/mcp{
"mcpServers": {
"verifyum": {
"httpUrl": "https://api.verifyum.com/mcp"
}
}
}{
"mcpServers": {
"verifyum": {
"type": "http",
"url": "https://api.verifyum.com/mcp"
}
}
}{
"mcpServers": {
"verifyum": {
"url": "https://api.verifyum.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.verifyum.com%2Fmcp&type=streamable_http&id=verifyum&name=Verifyum
It answered our last check on 19 October 2026 in 278 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by verifyum.com and served from api.verifyum.com, the vendor's own domain: https://api.verifyum.com/mcp.
3, as returned by the server's own tools/list on 11 September 2026: verifyum_anchor_commitment, verifyum_get_proof, verifyum_verify_public_proof.
It answered our last check on 19 October 2026 in 278 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.verifyum.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.verifyum. Endpoint host: api.verifyum.com. ARD identifier: urn:air:com.verifyum:mcp:mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.