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/PavloSEO/seohead-seotoolsInstalling this writes the configuration, not the program: `seohead` has to be on your PATH already, or the server will not start.
Wrote 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/pavloseo/seohead-seotools/seohead)<a href="https://agentmods.dev/mcp/pavloseo/seohead-seotools/seohead"><img src="https://agentmods.dev/badge/mcp/pavloseo/seohead-seotools/seohead/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/pavloseo/seohead-seotools/seohead"><img src="https://agentmods.dev/badge/mcp/pavloseo/seohead-seotools/seohead.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
seohead 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
{
"seohead": {
"command": "seohead",
"args": [
"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 · 8 lines scan A efaec9b65fc2
seohead is an MCP server published in the GitHub repository PavloSEO/seohead-seotools (0 stars, last pushed 1mo 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-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.
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-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.
cituna-mcp
Track how 7 AI engines cite your brand, daily, with live Google Search Console. Runs locally from the cituna-mcp npm package. Needs 2 environment variables to run.
seosiri-aeo-geo-mcp
A sovereign, local-first MCP server for AI Engine Optimization (AEO), Generative Engine Optimization (GEO), llm.txt auditing, and content stickiness analytics. Runs locally from the seosiri-aeo-geo-mcp Python 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.