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/SEOSiri-Official/aeo-geo-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/seosiri-official/aeo-geo-mcp/seosiri-aeo-geo-mcp)<a href="https://agentmods.dev/mcp/seosiri-official/aeo-geo-mcp/seosiri-aeo-geo-mcp"><img src="https://agentmods.dev/badge/mcp/seosiri-official/aeo-geo-mcp/seosiri-aeo-geo-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/seosiri-official/aeo-geo-mcp/seosiri-aeo-geo-mcp"><img src="https://agentmods.dev/badge/mcp/seosiri-official/aeo-geo-mcp/seosiri-aeo-geo-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
seosiri-aeo-geo-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
{ "seosiri-aeo-geo-mcp": { "command": "uvx", "args": [ "seosiri-aeo-geo-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 684af9aae86f
seosiri-aeo-geo-mcp is an MCP server published in the GitHub repository SEOSiri-Official/aeo-geo-mcp (0 stars, last pushed 26d 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-09-01.
Other mcp servers, from other repositories
seo-audit
Free SEO & AI-search (AEO) audits for any site or Shopify store, with emailed weekly score reports. Remote server at inxy.ai.
vantage
Checks whether ChatGPT, Gemini and Perplexity cite your site, and who they cite instead. Remote server at vantagemcp.dev.
kansei-link
MCP server "kansei-link" as configured in kansei-link/kansei-mcp-server. Runs C:/Users/HP/KanseiLINK/kansei-link-mcp/dist/index.js with node. Needs 1 environment variable to run.
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.
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.
optiqra-mcp
MCP server exposing OptiQra's website audit tools: SEO, GEO, AEO, and AI-generated fixes. Runs locally from the optiqra-mcp npm package. Needs 3 environment variables to run.