Connect AI Visibility Index and your agent gets 3 tools, among them check_ai_visibility, get_ai_visibility_methodology, list_ai_visibility_industries. It answers at https://ai-visibility-index.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 23 October 2026, succeeded.
AI visibility rankings for 104 Japanese EC companies across ChatGPT, Claude, Gemini, Perplexity.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
check_ai_visibility | Check the AI visibility (LLMO/GEO) score for a specific domain. Returns the overall score (0-100), scores from 4 AI engines (ChatGPT, Claude, Gemini, Perplexity), citation rate, and industry ranking. Data is based on the AI Visibility Index Inputs: domain |
get_ai_visibility_methodology | Get the AI Visibility Index scoring methodology: how LLMO/GEO scores are calculated, which AI engines are tested (ChatGPT, Claude, Gemini, Perplexity), query types, scoring formula, and data freshness. | スコアリング方法論（計算式・対象エンジン・クエリ種別・データ更新頻度）。 |
list_ai_visibility_industries | List all industries covered by the AI Visibility Index with their average LLMO/GEO scores, company counts, and score ranges. Currently covers 9 Japanese EC industries with 104 companies total. | 9業界のAI可視性スコア平均・企業数・スコア範囲を一覧表示。 |
Every block below points at https://ai-visibility-index.dev/mcp. Pick your client and copy.
claude mcp add --transport http ai-visibility-index https://ai-visibility-index.dev/mcp
{
"mcpServers": {
"ai-visibility-index": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://ai-visibility-index.dev/mcp"]
}
}
}{
"mcpServers": {
"ai-visibility-index": {
"url": "https://ai-visibility-index.dev/mcp"
}
}
}{
"servers": {
"ai-visibility-index": {
"type": "http",
"url": "https://ai-visibility-index.dev/mcp"
}
}
}{
"context_servers": {
"ai-visibility-index": {
"url": "https://ai-visibility-index.dev/mcp"
}
}
}{
"mcpServers": {
"ai-visibility-index": {
"serverUrl": "https://ai-visibility-index.dev/mcp"
}
}
}{
"mcpServers": {
"ai-visibility-index": {
"url": "https://ai-visibility-index.dev/mcp"
}
}
}name: AI Visibility Index
version: 0.0.1
schema: v1
mcpServers:
- name: AI Visibility Index
type: streamable-http
url: https://ai-visibility-index.dev/mcp{
"mcpServers": {
"ai-visibility-index": {
"httpUrl": "https://ai-visibility-index.dev/mcp"
}
}
}{
"mcpServers": {
"ai-visibility-index": {
"type": "http",
"url": "https://ai-visibility-index.dev/mcp"
}
}
}{
"mcpServers": {
"ai-visibility-index": {
"url": "https://ai-visibility-index.dev/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fai-visibility-index.dev%2Fmcp&type=streamable_http&id=ai-visibility-index&name=AI%20Visibility%20Index
It answered our last check on 23 October 2026 in 143 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
3, as returned by the server's own tools/list on 20 September 2026: check_ai_visibility, get_ai_visibility_methodology, list_ai_visibility_industries.
It answered our last check on 23 October 2026 in 143 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://ai-visibility-index.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.pulse-digital-dev. Endpoint host: ai-visibility-index.dev. ARD identifier: urn:air:io.github.pulse-digital-dev:mcp:mcp-ai-visibility-index.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.