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/creanlab/ai-visibility-indexWrote 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/creanlab/ai-visibility-index/visibility-index)<a href="https://agentmods.dev/mcp/creanlab/ai-visibility-index/visibility-index"><img src="https://agentmods.dev/badge/mcp/creanlab/ai-visibility-index/visibility-index/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/creanlab/ai-visibility-index/visibility-index"><img src="https://agentmods.dev/badge/mcp/creanlab/ai-visibility-index/visibility-index.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
visibility-index 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
{ "visibility-index": { "url": "https://dablock.ai/mcp", "type": "streamable-http" } }
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 · 6 lines scan A 22a846698d6d
visibility-index is an MCP server published in the GitHub repository creanlab/ai-visibility-index (0 stars, last pushed 3d 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
openchainbench
Live, neutral benchmarks for public RPC latency, oracles, bridges, perp DEX, and prediction markets. Remote server at openchainbench.com.
tegro-wallet-mcp
The TON & GRAM wallet MCP — give any AI assistant read-only on-chain data (balances, tokens, transactions, prices, NFTs, DNS, address validation). One server for Claude, Cursor, Claude Code, ChatGPT and Hermes Agent. No keys, no signing. Runs locally from the @tegroton/wallet-mcp npm package. Needs 1 environment…
ai-visibility
Track brand visibility across ChatGPT, Perplexity, Claude, and Gemini. Runs locally from the ai-visibility-mcp npm package.
mcp-geo
DigestSEO GEO Tracker: track brand citations across five AI search engines. Runs locally from the @digestseo/mcp-geo npm package.
mcp-trading
Keyless prediction-market data across 12 venues plus paper-trading of crypto spot, futures, and PM. Runs locally from the @coinrithm/mcp-trading npm package. Needs 2 environment variables to run.
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.