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/AKzar1el/mcp-geoWrote 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/akzar1el/mcp-geo/digestseo-geo)<a href="https://agentmods.dev/mcp/akzar1el/mcp-geo/digestseo-geo"><img src="https://agentmods.dev/badge/mcp/akzar1el/mcp-geo/digestseo-geo/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/akzar1el/mcp-geo/digestseo-geo"><img src="https://agentmods.dev/badge/mcp/akzar1el/mcp-geo/digestseo-geo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
digestseo-geo 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 11d 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
{
"digestseo-geo": {
"url": "https://geo-mcp.digestseo.com/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.
- 11d ago First seen · 5 lines scan A 90846c8235b6
digestseo-geo is an MCP server published in the GitHub repository AKzar1el/mcp-geo (44 stars, last pushed today), 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-30.
Other mcp servers, from other repositories
ai-visibility
Track brand visibility across ChatGPT, Perplexity, Claude, and Gemini. Runs locally from the ai-visibility-mcp npm package.
crazyseo
Audit whether ChatGPT, Gemini and Perplexity recommend your site — 11 technical checks with no API keys, plus blind multi-engine visibility. Open-source GEO/AEO auditor + MCP server. Runs locally from the crazyseo npm package.
unifapi
MCP server "unifapi", hosted remotely at mcp.unifapi.com, as configured in unifapi-agent/agents.
optifeed-radar
AI visibility checker: does AI recommend your brand? GEO/AEO, runs locally, BYO keys. CLI + MCP. Runs locally from the optifeed-radar npm package. Needs 4 environment variables to run.
afterlaunch
MCP server "afterlaunch", hosted remotely at afterlaunch.io, as configured in afterlaunch/mcp.
agentic-growth-marketing
Growth marketing, SEO and GEO as agent tools: ranked moves, ship them, AI answer visibility. Remote server at afterlaunch.io.