D
Caution
52/100
13 days ago

Bags-SDK-hackathon

Launch a coin in 3 steps from your terminal. 43 MCP tools. Fee splits, claims, Dexscreener, agent auth. Your AI handles the rest.

Caution. Specific findings reduced this grade. They are listed on the page. 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

outerheaven199X

Source: github_code · also listed on 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
🚨
Secret credentials may flow to a network call
5 flows detected: BAGS_API_BASE, NOUS_API_KEY, ANTHROPIC_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 2 critical, 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 6 credentials: ANTHROPIC_API_KEY, BAGS_API_KEY, FAL_API_KEY, MCP_HTTP_TOKEN, NOUS_API_KEY, REPLICATE_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 critical3 high

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

criticalvitest@3.0.0GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

criticalvitest@3.0.0GHSA-9crc-q9x8-hgqq

Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening

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.
configAGENT_WALLET_PUBKEYAgent mode —
🔐 secretANTHROPIC_API_KEYRequires NOUS_API_KEY and .
configBAGS_API_BASENo https://public-api-v2.bags.fm/api/v1
🔐 secretBAGS_API_KEYclaude mcp add bags-sdk-mcp -e =your-key -- npx bags-sdk-mcp
🔐 secretFAL_API_KEYScout mode —
configIMAGE_GEN_PROVIDERScout mode fal
configMCP_HTTP_HOST
🔐 secretMCP_HTTP_TOKEN
🔐 secretNOUS_API_KEYRequires and ANTHROPIC_API_KEY.
🔐 secretREPLICATE_API_KEYScout mode —
configSCOUT_INTERVALScout mode 1800
configSCOUT_MAX_IDEASScout mode 3
configSCOUT_SOURCESScout mode bags,news
configSOLANA_RPC_URLNo mainnet-beta
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

46/46 tools missing one or more hints — bags_agent_auth_init (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); bags_agent_auth_login (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); bags_agent_bootstrap (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +43 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 0/46 tool handlers declare input schemas (0%)

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

Tool handlers catch errors

45/46 tool handlers wrap calls in try/catch (98%)

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

Tool test coverage

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

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

Secrets not logged

12 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.

Dev dependencies

2 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

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/outerheaven199x-bags-sdk-hackathon-1g59os?variant=verified)](https://m8ven.ai/mcp/outerheaven199x-bags-sdk-hackathon-1g59os)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 05eec8ebd8f9e60663fefdce78e65fee8bbc485b
code hash: 887cf7b475381d32659c981141dc3d11558f6a96f75dfe8f15b852dbca5d0e88
verified: 8/9/2026, 7:25:08 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