mcp
Privacy-preserving file proofs on Solana. Files are hashed locally. Currently free, no API key.
Should I use this
Quality & Safety
Findings (2)
- HIGHTool poisoning patterns detected
- MEDIUMTool description contains URL to non-standard domainin verifyum_anchor_commitment
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"mcp": {
"url": "https://api.verifyum.com/mcp"
}
}
}Remote endpoints
https://api.verifyum.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (3)
🟢verifyum_get_proof(proof_id)
Read the lifecycle state of one Verifyum proof (queued, submitted, finalized or failed). Input is a public proof ID only.
Input Schema
{
"type": "object",
"properties": {
"proof_id": {
"type": "string",
"pattern": "^[0-7][0-9a-hjkmnp-tv-z]{25}$",
"description": "A canonical 26-character Verifyum proof ID"
}
},
"required": [
"proof_id"
],
"additionalProperties": false
}🟢verifyum_verify_public_proof(proof_id)
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 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.
Input Schema
{
"type": "object",
"properties": {
"proof_id": {
"type": "string",
"pattern": "^[0-7][0-9a-hjkmnp-tv-z]{25}$",
"description": "A canonical 26-character Verifyum proof ID"
}
},
"required": [
"proof_id"
],
"additionalProperties": false
}🔴verifyum_anchor_commitment(commitment, idempotency_key)
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 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.
Input Schema
{
"type": "object",
"properties": {
"commitment": {
"type": "string",
"pattern": "^sha256:[0-9a-f]{64}$",
"description": "sha256: followed by 64 lowercase hexadecimal characters"
},
"idempotency_key": {
"type": "string",
"pattern": "^[A-Za-z0-9._~-]{16,128}$",
"description": "16 to 128 URL-safe characters, reused verbatim on retries"
}
},
"required": [
"commitment",
"idempotency_key"
],
"additionalProperties": false
}Community
Evidence