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/AgentSEO-dev/agentseo-clientsWrote 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/agentseo-dev/agentseo-clients/mcp-server-agentseo-mcp)<a href="https://agentmods.dev/mcp/agentseo-dev/agentseo-clients/mcp-server-agentseo-mcp"><img src="https://agentmods.dev/badge/mcp/agentseo-dev/agentseo-clients/mcp-server-agentseo-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/agentseo-dev/agentseo-clients/mcp-server-agentseo-mcp"><img src="https://agentmods.dev/badge/mcp/agentseo-dev/agentseo-clients/mcp-server-agentseo-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agentseo-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 today.
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
{
"agentseo-mcp": {
"command": "npx",
"args": [
"-y",
"@agentseo/mcp-server"
],
"env": {
"AGENTSEO_API_KEY": "",
"AGENTSEO_API_URL": "",
"AGENTSEO_PROJECT_ID": "",
"AGENTSEO_WORKFLOW_ID": ""
}
}
}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.
- today First seen · 15 lines scan A 03d212f6bb2f
agentseo-mcp is an MCP server published in the GitHub repository AgentSEO-dev/agentseo-clients (0 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-11-04.
Other mcp servers, from other repositories
mcp-search-console
Google Search Console integration for Model Context Protocol (MCP). Runs locally from the mcp-search-console Python package. Needs 3 environment variables to run.
search-console-mcp
Google Search Console + Bing + GA4 + AdSense — unified SEO intelligence for AI agents. Runs locally from the search-console-mcp npm package. Needs 3 environment variables to run.
pipefy
MCP server "pipefy", hosted remotely at mcp.pipefy.com, as configured in pipefy/ai-toolkit.
screaming-frog-mcp
Headless MCP server for Screaming Frog SEO Spider: run crawls, export and analyze crawl data via the CLI, no GUI session required. Built for scheduled audits, CI, and AI agents. Runs locally from the screaming-frog-mcp Python package. Needs 1 environment variable to run.
rampify-mcp
SEO MCP server: crawl your site, find AI-visibility gaps, and ship the fix from your coding agent. Remote server at www.rampify.dev.
mcp
Track keyword rankings, research SEO opportunities, and manage bisibility projects with AI agents. Runs locally from the @bisibility/mcp npm package. Needs 5 environment variables to run.