C
Emerging
74/100
17 days ago

EVIDIQ Methodology

A framework and verification MCP server for building, testing, deploying, and registering x402-paid MCP services on OKX.AI, providing 15 tools (git history audit, x402 compliance, OKX status checking, production readiness scoring, and on-chain attestation) plus 15 methodology skills.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

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 →

Install from

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 4 credentials: METHODOLOGY_SIGNER_PRIVATE_KEY, OG_PRIVATE_KEY, OKX_API_KEY, OKX_SECRET_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
🔐 secretMETHODOLOGY_SIGNER_PRIVATE_KEY
configMETHODOLOGY_X402_BYPASS
configOG_CHAIN_ID
configOG_COMPUTE_RPC
🔐 secretOG_PRIVATE_KEY
configOG_STORAGE_INDEXER
configOG_STORAGE_RPC
🔐 secretOKX_API_KEY
configOKX_BASE_URL
configOKX_PASSPHRASE
🔐 secretOKX_SECRET_KEY
configPUBLIC_BASE_URL
configX402_ASSET
configX402_BYPASS
configX402_CHAIN
configX402_DOMAIN_NAME
configX402_DOMAIN_VERSION
configX402_PAY_TO
configX402_RPC
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

15/15 tools missing one or more hints — methodology_capabilities (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); validate_plan_sections (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); diff_capabilities (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +12 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.

Tool inputs are validated

14/15 tool handlers declare input schemas (93%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 6/15 tool handlers wrap calls in try/catch (40%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

6/15 tools referenced in tests (40%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

1 child_process call — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

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 6 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-methodology-mcp-173ygr)](https://m8ven.ai/mcp/evidiq-evidiq-methodology-mcp-173ygr)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 7f8a6c33c76e82c8040fed5b53518d6fe3e6e1e1
code hash: d7db553f0883007dca54907ee74786deb686da3b7c054d19f01504490e5b24f0
verified: 8/2/2026, 9:04:56 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