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/scavio-ai/scavio-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/scavio-ai/scavio-mcp/scavio)<a href="https://agentmods.dev/mcp/scavio-ai/scavio-mcp/scavio"><img src="https://agentmods.dev/badge/mcp/scavio-ai/scavio-mcp/scavio/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/scavio-ai/scavio-mcp/scavio"><img src="https://agentmods.dev/badge/mcp/scavio-ai/scavio-mcp/scavio.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
scavio 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 10d 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
{
"scavio": {
"type": "http",
"url": "https://mcp.scavio.dev/mcp",
"headers": {
"x-api-key": "${SCAVIO_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.
- 10d ago First seen · 9 lines scan A b8a8a4942332
scavio is an MCP server published in the GitHub repository scavio-ai/scavio-mcp (7 stars, last pushed yesterday), 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
google-search
Google SERP as JSON: organic, AI Overview, People Also Ask, AI Mode, news, shopping. No Cloud setup. Runs locally from the @hasdata/google-search-mcp npm package. Needs 1 environment variable to run.
listinggood
MCP server "listinggood", hosted remotely at listinggood.com, as configured in DedeGroup/listinggood-skills.
seo
Spot keyword demand rising or fading. Trend volume and growth signals. Free key at trendsmcp.ai. Remote server at seo.api.trendsmcp.ai.
sportscore-mcp
Live scores, standings, top scorers, brackets for football, basketball, cricket, tennis. Free API. Runs locally from the sportscore-mcp npm package. Needs 2 environment variables to run.
openclaw-control-mcp
MCP server bridging Claude Code to the OpenClaw gateway management plane via JSON-RPC. Runs locally from the openclaw-control-mcp npm package.
presentation-md
MCP server exposing all 14 presentation-md tools (render/export/audit/judge/scaffold/share/deploy/import/preview) to any MCP-compatible AI agent. Runs locally from the @presentation-md/mcp-server npm package.