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/aadilr/costbench-mcpWrote 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/aadilr/costbench-mcp/costbench)<a href="https://agentmods.dev/mcp/aadilr/costbench-mcp/costbench"><img src="https://agentmods.dev/badge/mcp/aadilr/costbench-mcp/costbench.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
costbench 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 7d 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
{
"costbench": {
"type": "http",
"url": "https://costbench.com/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.
- 7d ago First seen · 6 lines scan A e47e93924986
costbench is an MCP server published in the GitHub repository aadilr/costbench-mcp (0 stars, last pushed 14d 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
topalternativesto
Compare software: verified pricing with its source and date, and ranked alternatives. Remote server at topalternatives.to.
comparedge-mcp
Verified pricing, alternatives, and comparisons for 495+ SaaS and AI tools. Runs locally from the @comparedge/mcp-server npm package.
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.0). Needs 6 environment variables to run.
apibase
327 tools, 92 providers. Pay per call via x402 + MPP. One MCP endpoint. Runs locally from the apibase-mcp-client npm package.
astravue-mcp
Manage projects, tasks, time tracking, and team collaboration through natural language. Remote server at api.astravue.com.