Verifyum

com.verifyumPublished by verifyum.comOfficial publisherv0.1.0Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableFiles & StorageSecurity & Monitoring

Overview

AI-generated overview

Verifyum lets an assistant submit locally computed file commitments to Solana and check the lifecycle and validity of public proofs.

What you can do
Read the lifecycle state of a proof by its public proof ID (queued, submitted, finalized or failed). Verify a finalized proof: metadata consistency, the exact 128-byte memo, and the Ed25519 service signature against the published key registry, with the Solana RPC call and expectations for independent on-chain confirmation. Submit one locally calculated version 2 commitment, with an idempotency key, to be anchored.
When to use it
Useful when you need to timestamp or prove the existence of a file without uploading it, and want an assistant to submit the commitment and later check or verify the resulting proof.
Requirements
Remote streamable HTTP endpoint at api.verifyum.com; no package, environment variables or headers declared. The caller must hash the file and build the private manifest locally before anchoring. Currently free with no API key.
Before you install
Anchoring writes a commitment to a public chain and is not reversible. Only the commitment and idempotency key are sent; never send files, filenames, raw file hashes, nonces or private manifests. Verification is hosted, so confirm finalized proofs independently via the returned Solana RPC call.

Installation

In SourceWeft

  1. Open Verifyum in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.verifyum%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

3

verifyum_get_proof

Get Verifyum proof status

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

Parametersproof_idrequired

verifyum_verify_public_proof

Verify a public Verifyum 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 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.

Parametersproof_idrequired

verifyum_anchor_commitment

Anchor a prepared Verifyum 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 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.

Parameterscommitmentrequiredidempotency_keyrequired

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.