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/nycsav/notion-geo-auditWrote 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/nycsav/notion-geo-audit/geo-audit)<a href="https://agentmods.dev/mcp/nycsav/notion-geo-audit/geo-audit"><img src="https://agentmods.dev/badge/mcp/nycsav/notion-geo-audit/geo-audit/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/nycsav/notion-geo-audit/geo-audit"><img src="https://agentmods.dev/badge/mcp/nycsav/notion-geo-audit/geo-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
geo-audit 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
{
"geo-audit": {
"command": "node",
"args": [
"./dist/mcp.js"
]
}
}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 · 8 lines scan A d7492502320c
geo-audit is an MCP server published in the GitHub repository nycsav/notion-geo-audit (0 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
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.
geo-tool-check
Is this page readable for AI search? Checks crawler access, structure and citability for ChatGPT, Perplexity, Claude and Google AI. CLI and MCP server, runs entirely on your machine. Runs locally from the geo-tool-check npm package.
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.
shopify-geo-audit
Audit any Shopify store for AI search (GEO/AEO) readiness and generate the fixes. No signup. Runs locally from the shopify-geo-audit-mcp npm package.
seonix-seo-mcp
MCP server "seonix-seo-mcp" as configured in seonix-ai/seonix-mcp. Runs locally from the seonix-seo-mcp npm package.
geoseo-mcp
MCP server "geoseo-mcp" as configured in Rachit8484/geoseo-mcp. Runs locally from the geoseo-mcp Python package.