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/jonnyzzz/mcp-steroidWrote 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/jonnyzzz/mcp-steroid/rider-steroid)<a href="https://agentmods.dev/mcp/jonnyzzz/mcp-steroid/rider-steroid"><img src="https://agentmods.dev/badge/mcp/jonnyzzz/mcp-steroid/rider-steroid/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/jonnyzzz/mcp-steroid/rider-steroid"><img src="https://agentmods.dev/badge/mcp/jonnyzzz/mcp-steroid/rider-steroid.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rider-steroid 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 6d 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
{
"rider-steroid": {
"url": "http://localhost:6316/mcp",
"type": "http"
}
}What else settings.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 6d ago First seen · 6 lines scan A a7451abdaf10
rider-steroid is an MCP server published in the GitHub repository jonnyzzz/mcp-steroid (78 stars, last pushed 7d 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-09-17.
Other mcp servers, from other repositories
avvarre
Harness the true power of agentic coding. Stop re-explaining context to your AI. Just Avvarre it: persistent memory, 650+ style rules, and self-correcting autopilot loops for autonomous agents. Runs locally from the avvarre npm package.
agentbits
Machine-readable utilities and datasets for AI agents. Remote server at agentbits.dev.
agent-venue-radar
MCP server "agent-venue-radar" as configured in ItzxFin2323/agent-venue-radar. Launched with https://github.com/ItzxFin2323/agent-venue-radar/releases/download/v0.3.4/agent-.
nitpicker
MCP server "nitpicker" as configured in ivuorinen/skills. Runs ${CLAUDE_PROJECT_DIR:-.}/skills/nitpicker/scripts/mcp_server.py with python3. Needs 1 environment variable to run.
computermate
MCP server exposing computer-use tools to LLMs. Runs locally from the @one710/computermate npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.