EVIDIQ Vault MCP (evidiq/evidiq-vault-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 10 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
—
Source no longer public
1 month ago

EVIDIQ Vault MCP

Governed, tamper-evident memory and audit trail for AI agents with 0G Merkle segment sealing. Records agent actions in append-only namespaces with hash chaining, seals segments to 0G Storage, and supports audits and retention enforcement.

→ evidiq/evidiq-vault-mcp· listed on glama

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

evidiq

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 5 credentials: OG_PRIVATE_KEY, OKX_API_KEY, OKX_SECRET_KEY, VAULT_SIGNER_PRIVATE_KEY, X402_SETTLE_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configHOSTNAME
configOG_CHAIN_ID
🔐 secretOG_PRIVATE_KEY
🔐 secretOKX_API_KEY
configOKX_BASE_URL
configOKX_PASSPHRASE
🔐 secretOKX_SECRET_KEY
configOKX_SYNC_SETTLE
configPUBLIC_BASE_URL
configVAULT_DATA_DIRThe ledger lives under (/app/data/vault by default). It must be writable
🔐 secretVAULT_SIGNER_PRIVATE_KEY
configX402_ASSET0x779ded0c9e1022225f8e0630b35a9b54be713736
configX402_CHAINeip155:196
configX402_DOMAIN_NAME
configX402_DOMAIN_VERSION
configX402_FACILITATOR_URL
configX402_NETWORK
configX402_PAY_TO0x2a8efe3093278bb4bd3b2d9c7b5ba992ca4fc9b0
configX402_RPC
configX402_RPC_URL
🔐 secretX402_SETTLE_KEY
configX402_USE_FACILITATOR
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

10/10 tools missing one or more hints — append_record (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); query_records (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); seal_segment (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +7 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/evidiq/evidiq-vault-mcp)](https://m8ven.ai/mcp/evidiq/evidiq-vault-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: ad53fda22601ba6bbe1cee2aba222ecad30a9e38
code hash: a9e591eda2fac3bd2769877aceaf6ae9ff485f9dc697e2fda9f1ab1a21a3601f
verified: 8/9/2026, 3:56:44 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client