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/maxaeo/maxaeo-ai-visibility-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/maxaeo/maxaeo-ai-visibility-mcp/maxaeo-ai-visibility-mcp)<a href="https://agentmods.dev/mcp/maxaeo/maxaeo-ai-visibility-mcp/maxaeo-ai-visibility-mcp"><img src="https://agentmods.dev/badge/mcp/maxaeo/maxaeo-ai-visibility-mcp/maxaeo-ai-visibility-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/maxaeo/maxaeo-ai-visibility-mcp/maxaeo-ai-visibility-mcp"><img src="https://agentmods.dev/badge/mcp/maxaeo/maxaeo-ai-visibility-mcp/maxaeo-ai-visibility-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
maxaeo-ai-visibility-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
{
"maxaeo-ai-visibility-mcp": {
"command": "npx",
"args": [
"-y",
"maxaeo-ai-visibility-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 b0f128654179
maxaeo-ai-visibility-mcp is an MCP server published in the GitHub repository maxaeo/maxaeo-ai-visibility-mcp (1 stars, last pushed 16d 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
cituna-mcp
Track how 6 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.
vantage-mcp
MCP server "vantage-mcp" as configured in vantagemcp/vantage-mcp. Runs locally from the vantage-mcp Python package.
mcp-geo
DigestSEO GEO Tracker: track brand citations across five AI search engines. Runs locally from the @digestseo/mcp-geo npm package.
digestseo-geo
MCP server "digestseo-geo", hosted remotely at geo-mcp.digestseo.com, as configured in AKzar1el/mcp-geo.
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.
mcp-registry
MCP server "mcp-registry" as configured in kansei-link/kansei-mcp-server. Runs locally from the @anthropic-ai/mcp-registry npm package.