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/geo-tool-com/geo-tool-checkWrote 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/geo-tool-com/geo-tool-check/geo-tool-check-geo-tool-check)<a href="https://agentmods.dev/mcp/geo-tool-com/geo-tool-check/geo-tool-check-geo-tool-check"><img src="https://agentmods.dev/badge/mcp/geo-tool-com/geo-tool-check/geo-tool-check-geo-tool-check/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/geo-tool-com/geo-tool-check/geo-tool-check-geo-tool-check"><img src="https://agentmods.dev/badge/mcp/geo-tool-com/geo-tool-check/geo-tool-check-geo-tool-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
geo-tool-check 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 12d 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-tool-check": {
"command": "npx",
"args": [
"-y",
"geo-tool-check",
"--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.
- 12d ago First seen · 10 lines scan A 2ba0c6ad5b36
geo-tool-check is an MCP server published in the GitHub repository geo-tool-com/geo-tool-check (2 stars, last pushed 11d 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.
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.
geo-optimizer
MCP server "geo-optimizer" as configured in Auriti-Labs/geo-optimizer-skill. Launched with .venv/bin/geo-mcp. Needs 1 environment variable to run.
seo-geo
MCP server for SEO and GEO (Generative Engine Optimization) audits — on-page SEO, structured data, robots.txt, sitemaps, hreflang, and AI-crawler access for ChatGPT, Claude, Perplexity and Gemini. No API keys required. Runs locally from the seo-geo-mcp-server npm package.
growth-mcp
MCP server for growth marketing — campaign design, retention analysis, churn prediction. Runs locally from the growth-mcp Python package.
collimer-mcp
Free AI-search visibility scan for any website — score, top findings, ranked-fix-plan upgrade. Runs locally from the collimer-mcp npm package.