zkevidenceoracle MCP server
io.tooloracle/zkevidenceoracletooloracle.iostreamable-httpv1.0.0Scanned
ZKEvidenceOracle - 14 zero-knowledge proof tools for compliance evidence: Groth16, PLONK.
14 tools: 11 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
11 tools here change things. Govern them.
- 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 zkevidenceoracle MCP server can do
The zkevidenceoracle MCP server is published by tooloracle.io, a domain the MCP Registry verified. It has 14 tools. It can create or change data (11 tools: create_commitment, verify_commitment, verify_merkle_proof, create_vc and 7 more), but cannot delete data. 3 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 3 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 21, 2026, version 1.0.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.
14 tools
Changes things 11Claude Code: ask
audit_proofAuditor-ready proof package: commitment + merkle + credential.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...dy proof package: commitment + merkle + credential."
Description, as the server wrote it Auditor-ready proof package: commitment + merkle + credential.
create_commitmentHash compliance status into ZK commitment.No findings
Why it is in this group
- The name "create_commitment" says "create": a word for a change.
Description, as the server wrote it Hash compliance status into ZK commitment. Proves state without revealing details.
create_vcCreate W3C Verifiable Credential for DORA compliance.1 finding
Why it is in this group
- The name "create_vc" says "create": a word for a change.
Findings
- Info
The description mentions "Credential".
What this check looks forMatched text
description: "Create W3C Verifiable Credential for DORA compliance. Grade + score only..."
Description, as the server wrote it Create W3C Verifiable Credential for DORA compliance. Grade + score only.
health_checkServer status + crypto info.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Server status + crypto info.
obligation_proofProve obligation fulfilled without showing evidence.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Prove obligation fulfilled without showing evidence.
privacy_reportPrivacy-preserving report: hashes instead of raw data.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Privacy-preserving report: hashes instead of raw data.
selective_disclosureDisclose specific fields, hash the rest.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Disclose specific fields, hash the rest.
threshold_proofProve 'score >= X' without revealing exact score.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Prove 'score >= X' without revealing exact score.
verify_commitmentVerify commitment against current state.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Verify commitment against current state.
verify_merkle_proofVerify evidence in merkle tree.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Verify evidence in merkle tree.
verify_vcVerify credential integrity.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "Verify credential integrity."
Description, as the server wrote it Verify credential integrity.
Only reads 3Show 3 read-only tools
anchor_statusOn-chain anchor status: Polygon ZK attestation + XRPL report anchoring.No findings
Why it is in this group
- The name "anchor_status" says "status": a word for reading.
Description, as the server wrote it On-chain anchor status: Polygon ZK attestation + XRPL report anchoring.
build_merkle_treeBuild merkle tree from all active evidence.No findings
Why it is in this group
- The name "build_merkle_tree" says "tree": a word for reading.
Description, as the server wrote it Build merkle tree from all active evidence. Root hash proves evidence exists.
pingConnectivity test.No findings
Why it is in this group
- The name "ping" says "ping": a word for reading.
Description, as the server wrote it Connectivity test.
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 untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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, 19:32 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
- 11
- Protocol version
- 2025-03-26
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://tooloracle.io/.well-known/oauth-protected-resource/zk/mcp
- Authorization servers
- https://feedoracle.io
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 11 tools that change things (11 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://tooloracle.io/zk/mcp/: tools/list returned 14 tools to an anonymous client, including create_commitment (write), verify_commitment (write), verify_merkle_proof (write), create_vc (write), verify_vc (write) and 6 more
Findings
Matches of fixed checks, with the text they matched.
- Infocreate_vc
The description mentions "Credential".
What this check looks forMatched text
description: "Create W3C Verifiable Credential for DORA compliance. Grade + score only..."
- Infoverify_vc
The description mentions "credential".
What this check looks forMatched text
description: "Verify credential integrity."
- Infoaudit_proof
The description mentions "credential".
What this check looks forMatched text
description: "...dy proof package: commitment + merkle + credential."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http zkevidenceoracle https://tooloracle.io/zk/mcp/claude mcp add --transport http zkevidenceoracle https://tooloracle.io/zk/mcp/Run 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__zkevidenceoracle__build_merkle_tree",
"mcp__zkevidenceoracle__anchor_status",
"mcp__zkevidenceoracle__ping"
],
"ask": [
"mcp__zkevidenceoracle__create_commitment",
"mcp__zkevidenceoracle__verify_commitment",
"mcp__zkevidenceoracle__verify_merkle_proof",
"mcp__zkevidenceoracle__create_vc",
"mcp__zkevidenceoracle__verify_vc",
"mcp__zkevidenceoracle__privacy_report",
"mcp__zkevidenceoracle__selective_disclosure",
"mcp__zkevidenceoracle__audit_proof",
"mcp__zkevidenceoracle__threshold_proof",
"mcp__zkevidenceoracle__obligation_proof",
"mcp__zkevidenceoracle__health_check"
],
"deny": []
}
}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 zkevidenceoracle. Review it before you use it.
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/io.tooloracle/zkevidenceoracle/verify?hash=cb192a8c65a5a5882fd3624ceae88d2c4fe46559c5d9d0c5e41a9e1b23197421" | jq -e '.changed == false'Pinned hash cb192a8c65a5, from Nov 21, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.tooloracle/zkevidenceoracle/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.tooloracle/zkevidenceoracle)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:52 UTC.
zkevidenceoracle MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the zkevidenceoracle MCP server safe?
- No scan can promise that. What its definitions show: 14 tools, 11 of which can change, send or delete something, and 3 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 zkevidenceoracle MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the zkevidenceoracle 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 zkevidenceoracle MCP server have?
- 14 tools: 11 write, 3 read. create_commitment, verify_commitment, verify_merkle_proof, create_vc, verify_vc, privacy_report, selective_disclosure, audit_proof and 6 more.
Does the zkevidenceoracle MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the zkevidenceoracle MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the zkevidenceoracle MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.