zkevidenceoracle
Server Details
ZKEvidenceOracle - 14 zero-knowledge proof tools for compliance evidence: Groth16, PLONK.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 2.6/5 across 14 of 14 tools scored. Lowest: 2/5.
Most tools have clearly distinct roles (e.g., ping vs health_check, various proof types), but privacy_report and selective_disclosure share similar privacy themes, and audit_proof combines multiple functions, causing slight ambiguity.
Mixed naming patterns: some tools use verb_noun (create_commitment, verify_vc), while others are noun_noun (anchor_status, obligation_proof) or single verbs (ping). No consistent convention.
14 tools is reasonable for a specialized ZK evidence oracle. The count covers core operations without being excessive, though a few could be merged.
Covers main lifecycle: creation (commitment, VC), building (merkle tree), verification (multiple), and proofs (obligation, threshold). Minor gaps like missing list/update tools, but acceptable for an immutable oracle.
Available Tools
14 toolsanchor_statusInspect
On-chain anchor status: Polygon ZK attestation + XRPL report anchoring.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
audit_proofInspect
Auditor-ready proof package: commitment + merkle + credential.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No |
build_merkle_treeInspect
Build merkle tree from all active evidence. Root hash proves evidence exists.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No |
create_commitmentInspect
Hash compliance status into ZK commitment. Proves state without revealing details.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No |
create_vcInspect
Create W3C Verifiable Credential for DORA compliance. Grade + score only.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | dora_readiness|mica_compliance|aml_screening | |
| entity_id | No |
health_checkInspect
Server status + crypto info.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
obligation_proofInspect
Prove obligation fulfilled without showing evidence.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No | ||
| obligation_id | No | e.g. DORA-TPR-03 |
pingInspect
Connectivity test.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
privacy_reportInspect
Privacy-preserving report: hashes instead of raw data.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No |
selective_disclosureInspect
Disclose specific fields, hash the rest.
| Name | Required | Description | Default |
|---|---|---|---|
| disclose | No | Comma-separated: score,grade,entity_name,total_checks,green_checks | |
| entity_id | No |
threshold_proofInspect
Prove 'score >= X' without revealing exact score.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No | ||
| threshold | No | Minimum score to prove (default: 80) |
verify_commitmentInspect
Verify commitment against current state.
| Name | Required | Description | Default |
|---|---|---|---|
| commitment_id | No |
verify_merkle_proofInspect
Verify evidence in merkle tree.
| Name | Required | Description | Default |
|---|---|---|---|
| tree_id | No | ||
| evidence_id | No |
verify_vcInspect
Verify credential integrity.
| Name | Required | Description | Default |
|---|---|---|---|
| credential_id | No |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!