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/OctoPerf/octoperf-claude-pluginsWrote 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/octoperf/octoperf-claude-plugins/octoperf-octoperf)<a href="https://agentmods.dev/mcp/octoperf/octoperf-claude-plugins/octoperf-octoperf"><img src="https://agentmods.dev/badge/mcp/octoperf/octoperf-claude-plugins/octoperf-octoperf/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/octoperf/octoperf-claude-plugins/octoperf-octoperf"><img src="https://agentmods.dev/badge/mcp/octoperf/octoperf-claude-plugins/octoperf-octoperf.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
octoperf 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 11d 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
{
"octoperf": {
"type": "http",
"url": "https://api.octoperf.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.
- 11d ago First seen · 6 lines scan A 70d4cce399bf
octoperf is an MCP server published in the GitHub repository OctoPerf/octoperf-claude-plugins (0 stars, last pushed 4d ago), licensed Apache-2.0. 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
python-code-validator
MCP server "python-code-validator", hosted remotely at api.statemind.ai, as configured in jkanselaar/python-code-validator.
mcp
AI-powered test automation: run tests, analyze failures, query results across mabl workspaces. Remote server at mcp.mabl.com.
rtblint
Validate OpenRTB bid requests and responses against IAB specs. ARTF, Rust core. Remote server at rtblint.org.
hookray-mcp
Webhook testing for AI agents. Runs locally from the hookray-mcp npm package.
playwright-axe-mcp
MCP server "playwright-axe-mcp" as configured in PashaBoiko/playwright-axe-mcp. Runs locally from the playwright-axe-mcp npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.