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/Bigsupe55/geo-inspector-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/bigsupe55/geo-inspector-mcp/geo-inspector-mcp)<a href="https://agentmods.dev/mcp/bigsupe55/geo-inspector-mcp/geo-inspector-mcp"><img src="https://agentmods.dev/badge/mcp/bigsupe55/geo-inspector-mcp/geo-inspector-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/bigsupe55/geo-inspector-mcp/geo-inspector-mcp"><img src="https://agentmods.dev/badge/mcp/bigsupe55/geo-inspector-mcp/geo-inspector-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
geo-inspector-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 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-inspector-mcp": {
"command": "npx",
"args": [
"-y",
"geo-inspector-mcp"
],
"env": {}
}
}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 · 10 lines scan A e04c828030b8
geo-inspector-mcp is an MCP server published in the GitHub repository Bigsupe55/geo-inspector-mcp (0 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-31.
Other mcp servers, from other repositories
next-devtools
Next.js development tools MCP server with stdio transport. Runs locally from the next-devtools-mcp npm package.
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.
mcp-seo-audit
MCP server for technical SEO audits powered by the detail.web engine: site health score, issues across 8 categories and a GEO (AI-search visibility) sub-score. Runs locally from the atomno-mcp-seo-audit Python package. Needs 1 environment variable to run.
maxaeo-ai-visibility-mcp
Local-first MCP server for AI visibility, GEO/AEO, llms.txt, and AI crawler readiness audits. Runs locally from the maxaeo-ai-visibility-mcp npm package.
mcp-compteparticulier
Guides de connexion aux espaces clients français de compteparticulier.com (MCP, lecture seule). Remote server at mcp-compteparticulier.ads-particulier-tn.workers.dev.
target5
Read and post to target5.net, where a claim is not a proof. Rules ride in the tools. Runs locally from the target5-mcp npm package. Needs 1 environment variable to run.