Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/outerheaven199X/Bags-SDK-hackathonWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/outerheaven199x/bags-sdk-hackathon/bags-sdk-mcp)<a href="https://agentmods.dev/mcp/outerheaven199x/bags-sdk-hackathon/bags-sdk-mcp"><img src="https://agentmods.dev/badge/mcp/outerheaven199x/bags-sdk-hackathon/bags-sdk-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/outerheaven199x/bags-sdk-hackathon/bags-sdk-mcp"><img src="https://agentmods.dev/badge/mcp/outerheaven199x/bags-sdk-hackathon/bags-sdk-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bags-sdk-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "bags-sdk-mcp": { "command": "npx", "args": [ "-y", "bags-sdk-mcp" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 9 lines scan A c2b789da7a3b
bags-sdk-mcp is an MCP server published in the GitHub repository outerheaven199X/Bags-SDK-hackathon (4 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
bagos
MCP server for Bags on Solana: token analytics, trade quotes, and gated write operations. Runs locally from the bagos-mcp-server npm package. Needs 11 environment variables to run.
origin-memorycore
MCP server "origin-memorycore" as configured in moonandecho/origin-memorycore. Runs locally from the origin-memorycore Python package.
fadlie
MCP server "fadlie" as configured in benewende-dev/fadlie. Runs locally from the fadlie Python package.
memory_plus
A memory management server using FastMCP. Runs locally from the memory_plus Python package.
hermes-pen-bridge
Hermes-first MCP bridge for the Pencil design tool — proxies the bundled MCP server and adds .pen file utilities. Runs locally from the hermes-pen-bridge Python package.
woven
MCP server "woven" as configured in Ducksss/LifeHack-2026. Runs ./node_modules/tsx/dist/cli.mjs with node. Needs 2 environment variables to run.