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/seonix-ai/seonix-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/seonix-ai/seonix-mcp/seonix-seo-mcp)<a href="https://agentmods.dev/mcp/seonix-ai/seonix-mcp/seonix-seo-mcp"><img src="https://agentmods.dev/badge/mcp/seonix-ai/seonix-mcp/seonix-seo-mcp/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/seonix-ai/seonix-mcp/seonix-seo-mcp"><img src="https://agentmods.dev/badge/mcp/seonix-ai/seonix-mcp/seonix-seo-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
seonix-seo-mcp 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
{ "seonix-seo-mcp": { "command": "npx", "args": [ "-y", "seonix-seo-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.
- 1mo ago First seen · 9 lines scan A 6d8bb0beb0b7
seonix-seo-mcp is an MCP server published in the GitHub repository seonix-ai/seonix-mcp (0 stars, last pushed 4mo 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
geoseo-mcp
MCP server for SEO + GEO: Search Console, Bing, Yandex, IndexNow, AI Overviews, and LLM citation tracking across ChatGPT, Claude, Gemini, Perplexity, Grok and Brave. Runs locally from the geoseo-mcp Python package. Needs 12 environment variables to run.
ai-readiness
MCP server "ai-readiness" as configured in epistemedeus/ai-readiness. Launched with https://github.com/epistemedeus/ai-readiness/releases/download/v1.1.3/ai-readine.
geo-audit
MCP server "geo-audit" as configured in nycsav/notion-geo-audit. Runs ./dist/mcp.js with node.
bittlebits
MCP server "bittlebits", hosted remotely at bittlebits.ai, as configured in bittlebitsai/bittlebits-plugin.
seo-performance-mcp
Per-URL SEO verdicts from GSC, GA4, Matomo, Clarity, AI citations: refresh/expand/merge/kill. Runs locally from the @automatelab/seo-performance-mcp npm package. Needs 14 environment variables to run.
ai-seo
AI Citation Toolkit - audit, score, and rewrite web pages for AI-citation eligibility. AEO/GEO/LLM visibility for any MCP client. Runs locally from the @automatelab/ai-seo-mcp npm package.