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/sergey-goncharenko/redpill-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/sergey-goncharenko/redpill-mcp/redpill)<a href="https://agentmods.dev/mcp/sergey-goncharenko/redpill-mcp/redpill"><img src="https://agentmods.dev/badge/mcp/sergey-goncharenko/redpill-mcp/redpill/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/sergey-goncharenko/redpill-mcp/redpill"><img src="https://agentmods.dev/badge/mcp/sergey-goncharenko/redpill-mcp/redpill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
redpill 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
{
"redpill": {
"command": "npx",
"args": [
"-y",
"redpill-mcp"
],
"env": {
"REDPILL_ALLOW_DECLINE": "0",
"REDPILL_OBSERVE_ONLY": "0",
"REDPILL_PERSONA_BACKEND": "stub"
}
}
}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 · 14 lines scan A 06c98c37b971
redpill is an MCP server published in the GitHub repository sergey-goncharenko/redpill-mcp (0 stars, last pushed 2d 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
proton-bridge-mcp
MCP server "proton-bridge-mcp" as configured in Considus/proton-bridge-mcp. Launched with https://github.com/Considus/proton-bridge-mcp/releases/download/v1.2.2/proton-br.
mcp
Create and manage Linkonda short links and QR codes, with no per-visitor tracking. Runs locally from the @veranoapp/linkonda-mcp npm package. Needs 2 environment variables to run.
opentor-mcp
MCP server "opentor-mcp" as configured in Medamine-cheddadi/opentor-mcp. Runs locally from the opentor-mcp Python package.
reed-mcp
MCP server "reed-mcp" as configured in Ulzuhan/reed-mcp. Runs locally from the reed-mcp Python package.
plausible-mcp-server
MCP server for Plausible Analytics — privacy-friendly web analytics. 12 tools for traffic, conver... Runs locally from the plausible-mcp-server npm package.
hypermnesia-mcp
Scientifically-grounded memory system based on computational neuroscience research. Runs locally from the hypermnesia-mcp Python package.