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/rog0x/mcp-api-toolsWrote 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/rog0x/mcp-api-tools/api)<a href="https://agentmods.dev/mcp/rog0x/mcp-api-tools/api"><img src="https://agentmods.dev/badge/mcp/rog0x/mcp-api-tools/api/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/rog0x/mcp-api-tools/api"><img src="https://agentmods.dev/badge/mcp/rog0x/mcp-api-tools/api.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
api 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
{ "api": { "command": "npx", "args": [ "-y", "@rog0x/mcp-api-tools" ], "env": {} } }
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 · 10 lines scan A ee745195f795
api is an MCP server published in the GitHub repository rog0x/mcp-api-tools (0 stars, last pushed 6mo 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
next-devtools
Next.js development tools MCP server with stdio transport. Runs locally from the next-devtools-mcp npm package.
browser
MCP server "browser" as configured in felipebarcelospro/igniter-js. Launched with npx @playwright/mcp@latest.
mcp-abap-adt
MCP server for SAP ABAP ADT: repository analysis and CRUD for RAP and classic ABAP. Runs locally from the @mcp-abap-adt/core npm package. Needs 10 environment variables to run.
developers-mcp
Access Mastercard Developers APIs, documentation, and API specifications through MCP. Runs locally from the @mastercard/developers-mcp npm package.
django-admin-mcp
Django admin MCP integration - expose Django admin models to MCP clients. Runs locally from the django-admin-mcp Python package. Needs 1 environment variable to run.
stitchapi-docs
StitchAPI documentation search, running locally over MCP stdio. Bundled docs, no network calls per query — the offline/air-gapped counterpart to the hosted stitchapi.dev/api/mcp server. Runs locally from the @stitchapi/docs-mcp npm package.