EVIDIQ Lineage (evidiq/evidiq-lineage-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 Lineage

Deterministic supply-chain provenance, SBOM/AI-BOM generation, and dependency risk analysis for npm and PyPI packages, with 14 security rules and verifiable reports.

→ evidiq/evidiq-lineage-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

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// 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: LINEAGE_SIGNER_PRIVATE_KEY, OG_PRIVATE_KEY, OKX_API_KEY, OKX_SECRET_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
configLINEAGE_SIGNER_ADDRESS
🔐 secretLINEAGE_SIGNER_PRIVATE_KEY
configOG_CHAIN_ID
🔐 secretOG_PRIVATE_KEY
🔐 secretOKX_API_KEY
configOKX_BASE_URL
configOKX_PASSPHRASE
🔐 secretOKX_SECRET_KEY
configOKX_SYNC_SETTLE
configOSV_BASE_URL
configPUBLIC_BASE_URL
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 — lineage_capabilities (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); validate_manifest (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); estimate_cost (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.

Tool inputs are validated

8/10 tool handlers declare input schemas (80%)

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

Tool handlers catch errors

7/10 tool handlers wrap calls in try/catch (70%)

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

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 4 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-lineage-mcp)](https://m8ven.ai/mcp/evidiq/evidiq-lineage-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 47b8801fc9f7be3a194972dc5463892e620e8a03
code hash: 5a1c8ecc0cb8d7d98b4f8064d3836e3e3cc651661cea950bc77669184fd1411a
verified: 7/27/2026, 10:23:28 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