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/User0856/snaprender-integrationsWrote 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/user0856/snaprender-integrations/snaprender)<a href="https://agentmods.dev/mcp/user0856/snaprender-integrations/snaprender"><img src="https://agentmods.dev/badge/mcp/user0856/snaprender-integrations/snaprender/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/user0856/snaprender-integrations/snaprender"><img src="https://agentmods.dev/badge/mcp/user0856/snaprender-integrations/snaprender.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
snaprender 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
{
"snaprender": {
"command": "npx",
"args": [
"-y",
"snaprender-mcp"
],
"env": {
"SNAPRENDER_API_KEY": ""
}
}
}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 · 12 lines scan A ac90e2814997
snaprender is an MCP server published in the GitHub repository User0856/snaprender-integrations (3 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
quesen
Deterministic risk-decision engine and Agent Settlement Protocol for autonomous agents. Remote server at web-production-30ab5.up.railway.app.
agent-context-token-optimizer
MCP server "agent-context-token-optimizer" as configured in DeathOVOGod/agent-context-token-optimizer. Runs locally from the agent-context-token-optimizer Python package.
gatewards
Drop-in spend governance + cross-agent dedup proxy for AI agent fleets, with x402 settlement. Runs locally from the @gatewards/mcp-server npm package. Needs 2 environment variables to run.
agentfetch
MCP server "agentfetch" as configured in SID1ART/agentfetch. Runs locally from the agentfetch Python package.
synap
Persistent memory for AI agents — log and recall conversation context over MCP. Remote server at synap-mcp.maximem.ai.
sidclaw-governance-mcp
Governance proxy for MCP servers — policy evaluation, human approval, audit trails. Runs locally from the @sidclaw/sdk npm package. Needs 5 environment variables to run.