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/akua-dev/codemodeWrote 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/akua-dev/codemode/petstore)<a href="https://agentmods.dev/mcp/akua-dev/codemode/petstore"><img src="https://agentmods.dev/badge/mcp/akua-dev/codemode/petstore/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/akua-dev/codemode/petstore"><img src="https://agentmods.dev/badge/mcp/akua-dev/codemode/petstore.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
petstore 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 1mo 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
{
"petstore": {
"command": "pnpm",
"args": [
"--filter",
"@robinbraemer/codemode",
"exec",
"tsx",
"examples/petstore-mcp-server.ts"
]
}
}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.
- 1mo ago First seen · 12 lines scan A 02912d29e3cd
petstore is an MCP server published in the GitHub repository akua-dev/codemode (4 stars, last pushed 1mo 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
toolport-openapi-mcp
Turn any OpenAPI/Swagger spec into an MCP server: one tool per endpoint. A showcase for Toolport (toolport.app). Runs locally from the toolport-openapi-mcp npm package.
pricing-api
Verified SaaS, AI, and LLM pricing for 490+ tools: plans, hidden costs, TCO, and alternatives. Remote server at comparedge.com.
local-reddit-research-mcp
MCP server "local-reddit-research-mcp", hosted remotely at localhost, as configured in dialog-tools/reddit-research-mcp.
figma-mcp-rust
Figma MCP server in Rust: plugin bridge, no API token, no rate limits, 73 tools. Runs locally from the @alvinindra/figma-mcp-rust npm package.
ninjaone-mcp
MCP server "ninjaone-mcp" as configured in WYRE-AI/ninjaone-mcp. Runs in Docker (ghcr.io/wyre-ai/ninjaone-mcp:v2.3.2). Needs 6 environment variables to run.
apibase
MCP endpoint to APIbase catalog (https://apibase.pro/llms.txt). USDC: x402 Base, MPP Tempo. Runs locally from the apibase-mcp-client npm package.