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.
npx agentmods add mcp/rog0x/mcp-seo-tools/seogit clone --depth 1 https://github.com/rog0x/mcp-seo-toolsWrote 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/rog0x/mcp-seo-tools/seo)<a href="https://agentmods.dev/mcp/rog0x/mcp-seo-tools/seo"><img src="https://agentmods.dev/badge/mcp/rog0x/mcp-seo-tools/seo.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
seo 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 5d 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
{ "seo": { "command": "npx", "args": [ "-y", "@rog0x/mcp-seo-tools" ], "env": {} } }
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.
- 5d ago First seen · 10 lines scan A a1d6409de042
seo is an MCP server published in the GitHub repository rog0x/mcp-seo-tools (1 stars, last pushed 5mo 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
seo-tools-mcp-aparser
Bridge to a self-hosted A-Parser: SERP, suggests and 150+ parsers via its API (read-only). Runs locally from the seo-tools-mcp-aparser npm package. Needs 6 environment variables to run.
seo-tools-mcp-xmlstock
Google & Yandex SERP + Yandex Wordstat via XMLStock (read-only). Runs locally from the seo-tools-mcp-xmlstock npm package. Needs 5 environment variables to run.
seo-tools-mcp-ga4
Google Analytics 4: reports, traffic sources, landing pages, events, realtime (read-only). Runs locally from the seo-tools-mcp-ga4 npm package. Needs 6 environment variables to run.
seo-tools-mcp-gsc
Google Search Console: Search Analytics, URL Inspection, sitemaps (read-only, OAuth/service acct). Runs locally from the seo-tools-mcp-gsc npm package. Needs 6 environment variables to run.
seo-tools-mcp-metrika
MCP server for Yandex.Metrica Stat API (read-only). Runs locally from the seo-tools-mcp-metrika npm package. Needs 5 environment variables to run.
seo-tools-mcp-xmlriver
Google & Yandex SERP, image/news verticals and URL indexation checks via XMLRiver (read-only). Runs locally from the seo-tools-mcp-xmlriver npm package. Needs 4 environment variables to run.