verifyum.com MCP server
com.verifyum/mcpverifyum.comstreamable-httpv0.1.0Scanned
Privacy-preserving file proofs on Solana. Files are hashed locally. Currently free, no API key.
3 tools: 1 can delete or cancel things, 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the verifyum.com MCP server can do
The verifyum.com MCP server is published by verifyum.com, a domain the MCP Registry verified. It has 3 tools. It can delete or cancel things (1 tool: verifyum_anchor_commitment) and create or change data (1 tool: verifyum_verify_public_proof). 1 tool only reads.
3 tools bring in text other people can write (verifyum_get_proof, verifyum_verify_public_proof and verifyum_anchor_commitment).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 14, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Deletes or cancels 1Claude Code: deny
verifyum_anchor_commitmentSubmit one locally calculated Verifyum version 2 commitment.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "submit": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
Changes things 1Claude Code: ask
verifyum_verify_public_proofCheck a finalized proof: metadata consistency, the exact 128-byte memo, and the Ed25519 service signature against the published key registry.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 1Show 1 read-only tool
verifyum_get_proofRead the lifecycle state of one Verifyum proof (queued, submitted, finalized or failed).Reads text others writeNo findings
Why it is in this group
- The name "verifyum_get_proof" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Read the lifecycle state of one Verifyum proof (queued, submitted, finalized or failed). Input is a public proof ID only.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:50 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.verifyum.com/mcp: tools/list returned 3 tools to an anonymous client, including verifyum_anchor_commitment (destructive), verifyum_verify_public_proof (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:verifyum_anchor_commitmentDeletes or cancelsannotations
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http verifyum https://api.verifyum.com/mcpclaude mcp add --transport http verifyum https://api.verifyum.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__verifyum__verifyum_get_proof"
],
"ask": [
"mcp__verifyum__verifyum_verify_public_proof"
],
"deny": [
"mcp__verifyum__verifyum_anchor_commitment"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as verifyum. Review it before you use it.
Capability tags behind 3 rules
- mcp__verifyum__verifyum_get_proof untrusted-input
- mcp__verifyum__verifyum_verify_public_proof untrusted-input
- mcp__verifyum__verifyum_anchor_commitment untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.verifyum/mcp/verify?hash=3955bf57964c405ecc43d5296fce4483aeff6ac4d9db3f6707f71b512d923ede" | jq -e '.changed == false'Pinned hash 3955bf57964c, from Nov 14, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.verifyum/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.verifyum/mcp)Source: MCP Registry. Synced Oct 21, 2026, 18:10 UTC.
verifyum.com MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the verifyum.com MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the verifyum.com MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: verifyum_anchor_commitment.
Can the verifyum.com MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the verifyum.com MCP server have?
- 3 tools: 1 destructive, 1 write, 1 read. verifyum_anchor_commitment, verifyum_verify_public_proof and verifyum_get_proof.
Does the verifyum.com MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the verifyum.com MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the verifyum.com MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.