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/IBazylchuk/paparats-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/ibazylchuk/paparats-mcp/paparats)<a href="https://agentmods.dev/mcp/ibazylchuk/paparats-mcp/paparats"><img src="https://agentmods.dev/badge/mcp/ibazylchuk/paparats-mcp/paparats/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/ibazylchuk/paparats-mcp/paparats"><img src="https://agentmods.dev/badge/mcp/ibazylchuk/paparats-mcp/paparats.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
paparats 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
{
"paparats": {
"type": "http",
"url": "http://localhost:9876/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 2fb70fc165ab
paparats is an MCP server published in the GitHub repository IBazylchuk/paparats-mcp (10 stars, last pushed 8d 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
model-id-cheatsheet
MCP server "model-id-cheatsheet", hosted remotely at universal-model-registry-production.up.railway.app, as configured in aezizhu/Model-ID-Cheatsheet.
dex-core
MCP server "dex-core" as configured in davekilleen/Dex. Runs ${CLAUDE_PLUGIN_ROOT}/bin/dex-python.mjs with node.
llm-bus
Coordinate multiple AI agents over MCP: atomic claims, leases, shared ledger, handoffs, tasks. Remote server at mcp.llm-bus.com.
mcp
Provision Postgres databases + webhooks from AI coding agents in one HTTP call. Runs locally from the @instanode/mcp npm package. Needs 2 environment variables to run.
veilmail-mcp
MCP server "veilmail-mcp" as configured in Resonia-Health/veilmail-mcp. Runs locally from the @resonia/veilmail-mcp npm package.
devpilot-ai
Dev server supervisor for AI coders. Runs locally from the devpilot-ai Python package.