Back to MCP Trust Indexm8ven
F
Warning
0/100
4 days ago

openzoo

Local x402-paying proxy and MCP server for openzoo.fun, enabling any OpenAI-compatible tool to pay for AI calls using a local burner wallet. It provides tools like zoo_ask for large-corpus questions, model listing, and wallet management.

→ staccDOTsol/openzoo· listed on glama

Warning. Serious findings were identified. Review the full report before connecting. 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

staccDOTsol

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
🚨
Secret credentials may flow to a network call
1 flow detected: OPENZOO_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 5 credentials: ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN, OPENAI_API_KEY, OPENZOO_TOKEN, OPENZOO_TUNNEL_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies3 high

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

high@modelcontextprotocol/sdk@1.12.0GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.12.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.12.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

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.
🔐 secretANTHROPIC_API_KEY
🔐 secretANTHROPIC_AUTH_TOKEN
🔐 secretOPENAI_API_KEYexport =sk-openzoo
configOPENZOO_API_BASE
configOPENZOO_ASK_MAX_TOKENS
configOPENZOO_BALANCE_POLL_SECS
configOPENZOO_BASE_RPC
configOPENZOO_BIND_MAX_BYTES
configOPENZOO_BIND_PART_BYTES
configOPENZOO_CONTEXT_MIN_CHARSOpt out with OPENZOO_NO_CONTEXT_CACHE=1 (always ship the full body); tune the threshold with (default 16384 chars).
configOPENZOO_DEFAULT_MODEL
configOPENZOO_DEMO_MAX_USD0.01 demo spend cap
configOPENZOO_DEMO_MODEL
configOPENZOO_DEMO_TOKENS
configOPENZOO_ENABLE_RH0 let default selection fall through to the Robinhood rail (OPENZOO_RAIL=robinhood forces it without this)
configOPENZOO_MAX_USD_PER_CALLthe per-call cap (, default $0.50) still applies;
configOPENZOO_MODELS
configOPENZOO_MODEL_LIMIT
configOPENZOO_NO_CONTEXT_CACHEOpt out with =1 (always ship the full body); tune the threshold with OPENZOO_CONTEXT_MIN_CHARS (default 16384 chars).
configOPENZOO_PORT8402 proxy port
configOPENZOO_PROFILE
configOPENZOO_RAIL(unset) force a rail: solana \ base \ robinhood. Errors if the live 402 doesn't offer it
configOPENZOO_RH_RPC
configOPENZOO_RPCmainnet-beta public RPC Solana RPC
configOPENZOO_SUPPORTED_URL
🔐 secretOPENZOO_TOKEN(internal) preferred 402 rail — leave unset
configOPENZOO_TUNNEL_MAX_USDa session ceiling stops all spending at (default $1.00);
configOPENZOO_TUNNEL_STRICT
🔐 secretOPENZOO_TUNNEL_TOKENPin the key with if your IDE stores it. Keys never leave your machine either way — the tunnel forwards to the same local proxy, which signs with the same local wallet.
configOPENZOO_WALLET~/.openzoo/wallet.json wallet path
// 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

6/6 tools missing one or more hints — zoo_ask (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); zoo_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); zoo_models (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 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

Only 2/6 tool handlers declare input schemas (33%)

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

Tool test coverage

Only 0/6 tools referenced in tests (0%)

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

Shell command execution

10 child_process/subprocess calls in production code — runs shell commands (lib/cursorcfg.js:37, lib/cursorcfg.js:50, lib/cursorcfg.js:73)

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

Secrets never reach shell commands

2 secret values passed to shell commands — possible command injection

Never pass secrets through shell commands. Use library APIs that accept credentials as arguments.

Secrets not logged

7 secret values sent to console.log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.12.0 (high), @modelcontextprotocol/sdk@1.12.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

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 8 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 Verified](https://m8ven.ai/badge/mcp/staccdotsol-openzoo-t8oh6a?variant=verified)](https://m8ven.ai/mcp/staccdotsol-openzoo-t8oh6a)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: abf68d478d71867658c1366825fc843d0a8359e0
code hash: 2bacb40cbf0bb62f46d64589bb65f146aa92da181a896978ae51c6e2c955f67d
verified: 8/15/2026, 9:36:23 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