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/AutomateLab-tech/ai-seo-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/automatelab-tech/ai-seo-mcp/ai-seo)<a href="https://agentmods.dev/mcp/automatelab-tech/ai-seo-mcp/ai-seo"><img src="https://agentmods.dev/badge/mcp/automatelab-tech/ai-seo-mcp/ai-seo/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/automatelab-tech/ai-seo-mcp/ai-seo"><img src="https://agentmods.dev/badge/mcp/automatelab-tech/ai-seo-mcp/ai-seo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ai-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 12d 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
{
"ai-seo": {
"command": "npx",
"args": [
"-y",
"@automatelab/ai-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.
- 12d ago First seen · 9 lines scan A a6f6b0d777bd
ai-seo is an MCP server published in the GitHub repository AutomateLab-tech/ai-seo-mcp (3 stars, last pushed 3mo 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
citation-intelligence
What LLMs cite, for agents. MCP server: check what Perplexity, Claude, ChatGPT, Gemini, Bing, and Google AI Overviews cite for any query. Self-hosted, BYO API key. Runs locally from the @automatelab/citation-intelligence npm package.
mcp-geo
DigestSEO GEO Tracker: track brand citations across five AI search engines. Runs locally from the @digestseo/mcp-geo npm package.
digestseo-geo
MCP server "digestseo-geo", hosted remotely at geo-mcp.digestseo.com, as configured in AKzar1el/mcp-geo.
aiseo-audit
Audit web pages for AI search readiness (ChatGPT, Claude, Perplexity, Gemini). Runs locally from the aiseo-audit-mcp npm package.
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.
aivis
MCP server "aivis" as configured in krisdiallo/ecom-agent. Launched with https://github.com/krisdiallo/ecom-agent/releases/download/v1.5.3/aivis.mcpb.