io.tooloracle/zkevidenceoracle
REMOTE · TOOLORACLE.IO · SCANNED SEP 23
ZKEvidenceOracle - 14 zero-knowledge proof tools for compliance evidence: Groth16, PLONK.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 437 tokens (~31/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 25% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.tooloracle/zkevidenceoracle MCP server?
io.tooloracle/zkevidenceoracle is a hosted endpoint at https://tooloracle.io/zk/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · tooloracle.io
claude mcp add --transport http io-tooloracle-zkevidenceoracle 'https://tooloracle.io/zk/mcp/'
{
"mcpServers": {
"io-tooloracle-zkevidenceoracle": {
"url": "https://tooloracle.io/zk/mcp/"
}
}
} {
"servers": {
"io-tooloracle-zkevidenceoracle": {
"type": "http",
"url": "https://tooloracle.io/zk/mcp/"
}
}
} [mcp_servers.io-tooloracle-zkevidenceoracle] url = "https://tooloracle.io/zk/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-tooloracle-zkevidenceoracle": {
"type": "remote",
"url": "https://tooloracle.io/zk/mcp/",
"enabled": true
}
}
} openclaw mcp add io-tooloracle-zkevidenceoracle --url 'https://tooloracle.io/zk/mcp/' --transport streamable-http
mcp_servers:
io-tooloracle-zkevidenceoracle:
url: "https://tooloracle.io/zk/mcp/" {
"McpServers": {
"io-tooloracle-zkevidenceoracle": {
"Transport": "http",
"Url": "https://tooloracle.io/zk/mcp/"
}
}
} assistant mcp add io-tooloracle-zkevidenceoracle -t streamable-http -u 'https://tooloracle.io/zk/mcp/'
{
"mcpServers": {
"io-tooloracle-zkevidenceoracle": {
"type": "http",
"url": "https://tooloracle.io/zk/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Aug 26 +1
- Stability: 0.97 → pass security
- 29 Aug 26 −1
- Stability: pass → 0.97 functional
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 73
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Sept 2026 · Probed https://tooloracle.io/zk/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tooloracle.io | CN=YE2,O=Let's Encrypt,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6375d594a6b9fdf6754e5a9a3d1f38b0dbd |
| SANs: mcp.tooloracle.io, tooloracle.io, www.tooloracle.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of tooloracle.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| tooloracle.io. | present | 45856 | 8 | Verified |
| tooloracle.io. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none'; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tooloracle.io/zk/mcp/ | Verified | 200 | |
| http (plaintext) | http://tooloracle.io/zk/mcp/ | HTTPS enforced | 308 | https://tooloracle.io/zk/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
anchor_status ~25
On-chain anchor status: Polygon ZK attestation + XRPL report anchoring.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
audit_proof ~29
Auditor-ready proof package: commitment + merkle + credential.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | – |
No output schema declared.
No examples provided.
build_merkle_tree ~33
Build merkle tree from all active evidence. Root hash proves evidence exists.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | – |
No output schema declared.
No examples provided.
create_commitment ~32
Hash compliance status into ZK commitment. Proves state without revealing details.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | – |
No output schema declared.
No examples provided.
create_vc ~53
Create W3C Verifiable Credential for DORA compliance. Grade + score only.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | – |
| type | string | – | dora_readiness|mica_compliance|aml_screening |
No output schema declared.
No examples provided.
health_check ~14
Server status + crypto info.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
obligation_proof ~43
Prove obligation fulfilled without showing evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | – |
| obligation_id | string | – | e.g. DORA-TPR-03 |
No output schema declared.
No examples provided.
ping ~10
Connectivity test.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
privacy_report ~27
Privacy-preserving report: hashes instead of raw data.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | – |
No output schema declared.
No examples provided.
selective_disclosure ~48
Disclose specific fields, hash the rest.
| Name | Type | Req | Description |
|---|---|---|---|
| disclose | string | – | Comma-separated: score,grade,entity_name,total_checks,green_checks |
| entity_id | string | – | – |
No output schema declared.
No examples provided.
threshold_proof ~45
Prove 'score >= X' without revealing exact score.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | – |
| threshold | integer | – | Minimum score to prove (default: 80) |
No output schema declared.
No examples provided.
verify_commitment ~23
Verify commitment against current state.
| Name | Type | Req | Description |
|---|---|---|---|
| commitment_id | string | – | – |
No output schema declared.
No examples provided.
verify_merkle_proof ~34
Verify evidence in merkle tree.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence_id | string | – | – |
| tree_id | string | – | – |
No output schema declared.
No examples provided.
verify_vc ~21
Verify credential integrity.
| Name | Type | Req | Description |
|---|---|---|---|
| credential_id | string | – | – |
No output schema declared.
No examples provided.
What is the io.tooloracle/zkevidenceoracle MCP server?
io.tooloracle/zkevidenceoracle is an MCP server listed in the public MCP registry as io.tooloracle/zkevidenceoracle. ZKEvidenceOracle - 14 zero-knowledge proof tools for compliance evidence: Groth16, PLONK. This page covers its hosted endpoint (https://tooloracle.io/zk/mcp/).
Is the io.tooloracle/zkevidenceoracle MCP server safe to use?
io.tooloracle/zkevidenceoracle scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.tooloracle/zkevidenceoracle MCP server expose?
io.tooloracle/zkevidenceoracle exposes 14 tools: create_commitment, verify_commitment, build_merkle_tree, verify_merkle_proof, create_vc, and 9 more. Their descriptions and schemas cost roughly 437 tokens of context every time the server is loaded.
Does the io.tooloracle/zkevidenceoracle MCP server require authentication?
No. We connected to io.tooloracle/zkevidenceoracle without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.tooloracle/zkevidenceoracle MCP server still maintained?
io.tooloracle/zkevidenceoracle is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.