C
Emerging
74/100
2 days ago

Zeus Insurance Protocol

Decentralized insurance and escrow for AI agents. Buy coverage against API failures and validator slashing via MCP tools. Live on X Layer (chainId 196).

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

igor-vii

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.
🔐
You'll be asked for 5 credentials: ADMIN_JWT_SECRET, AGENT_ERROR_SECRET, CLIENT_ERROR_SECRET, SERVER_PRIVATE_KEY, SESSION_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

lowesbuild@0.27.3GHSA-g7r4-m6w7-qqqr

esbuild allows arbitrary file read when running the development server on Windows

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
🔐 secretADMIN_JWT_SECRET
🔐 secretAGENT_ERROR_SECRET
configBASE_MAINNET_RPC_URL
configBASE_SEPOLIA_RPC_URL
configBOT_CHAIN_MAINNET_RPC_URL
configBOT_CHAIN_RPC_URLCustom RPC for BOT Chain
🔐 secretCLIENT_ERROR_SECRET
configCORS_ORIGINS
configDEPLOY_BLOCK
configESCROW_DEPLOY_BLOCK
configLOG_LEVEL
configREPLIT_DEV_DOMAIN
🔐 secretSERVER_PRIVATE_KEYEnables automatic mode — server signs transactions
🔐 secretSESSION_SECRETCookie signing secret (required)
configXLAYER_MAINNET_RPC_URLCustom RPC for X Layer
configZEUS_ESCROW_BOT_ADDRESS
configZEUS_ESCROW_NETWORK
configZEUS_INSURANCE_NETWORKOverride network for insurance contract only
configZEUS_NETWORKDefault network (bot-chain or x-layer)
configZEUS_STAKING_INSURANCE_ADDRESS
configZEUS_TREASURYWallet receiving x402 API fees
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployPORT
deployREDIS_URL
deploySENTRY_DSN
// 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

7/7 tools missing one or more hints — insurance_quote (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); insurance_prepare_buy (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); insurance_claim (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 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

6/7 tool handlers declare input schemas (86%)

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

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Domain consistency

npm scope @workspace doesn't match GitHub owner igor-vii

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 5 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/igor-vii-zeus-insurance-bot-5x5raa)](https://m8ven.ai/mcp/igor-vii-zeus-insurance-bot-5x5raa)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 7217486b58c5b371213514d3adbf0b7155c4be0e
code hash: a9e93a2a687a2380508fc3a5ea410c5f37df303ca0aa02f207c1aa451e19cc51
verified: 8/17/2026, 9:14:50 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