AI Visibility Index
REMOTE · AI-VISIBILITY-INDEX.DEV · SCANNED SEP 22
AI visibility rankings for 104 Japanese EC companies across ChatGPT, Claude, Gemini, Perplexity.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 321 tokens (~107/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the AI Visibility Index MCP server?
AI Visibility Index is a hosted endpoint at https://ai-visibility-index.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ai-visibility-index.dev
claude mcp add --transport http pulse-digital-dev-mcp-ai-visibility-index 'https://ai-visibility-index.dev/mcp'
{
"mcpServers": {
"pulse-digital-dev-mcp-ai-visibility-index": {
"url": "https://ai-visibility-index.dev/mcp"
}
}
} {
"servers": {
"pulse-digital-dev-mcp-ai-visibility-index": {
"type": "http",
"url": "https://ai-visibility-index.dev/mcp"
}
}
} [mcp_servers.pulse-digital-dev-mcp-ai-visibility-index] url = "https://ai-visibility-index.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pulse-digital-dev-mcp-ai-visibility-index": {
"type": "remote",
"url": "https://ai-visibility-index.dev/mcp",
"enabled": true
}
}
} openclaw mcp add pulse-digital-dev-mcp-ai-visibility-index --url 'https://ai-visibility-index.dev/mcp' --transport streamable-http
mcp_servers:
pulse-digital-dev-mcp-ai-visibility-index:
url: "https://ai-visibility-index.dev/mcp" {
"McpServers": {
"pulse-digital-dev-mcp-ai-visibility-index": {
"Transport": "http",
"Url": "https://ai-visibility-index.dev/mcp"
}
}
} assistant mcp add pulse-digital-dev-mcp-ai-visibility-index -t streamable-http -u 'https://ai-visibility-index.dev/mcp'
{
"mcpServers": {
"pulse-digital-dev-mcp-ai-visibility-index": {
"type": "http",
"url": "https://ai-visibility-index.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://ai-visibility-index.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ai-visibility-index.dev | CN=WE1,O=Google Trust Services,C=US | 20 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | f5569b832b977ae50e1ba3de947c25de |
| SANs: ai-visibility-index.dev, *.ai-visibility-index.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ai-visibility-index.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| ai-visibility-index.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://www.google-analytics.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: https:; connect-src 'self' https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com https://analytics.google.com https://stats.g.doubleclick.net https://api.web3forms.com https://ai-visibility-index.dev; frame-ancestors 'none'; base-uri 'self'; object-src 'none'; form-action 'self' https://api.web3forms.com https://checkout.stripe.com |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ai-visibility-index.dev/mcp | Verified | 200 | |
| http (plaintext) | http://ai-visibility-index.dev/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_ai_visibility ~156
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 monthly scan of 104 Japanese EC companies. Useful for LLMO (Large Language Model Optimization) and GEO (Generative Engine Optimization) analysis. | 日本EC企業104社のAI検索可視性スコアをドメイン指定で照会。
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check, e.g. "amazon.co.jp", "zozo.jp", "uniqlo.com/jp". Partial matches are supported. |
No output schema declared.
No examples provided.
get_ai_visibility_methodology ~86
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. | スコアリング方法論（計算式・対象エンジン・クエリ種別・データ更新頻度）。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_ai_visibility_industries ~79
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可視性スコア平均・企業数・スコア範囲を一覧表示。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the AI Visibility Index MCP server?
AI Visibility Index is an MCP server listed in the public MCP registry as io.github.pulse-digital-dev/mcp-ai-visibility-index. AI visibility rankings for 104 Japanese EC companies across ChatGPT, Claude, Gemini, Perplexity. This page covers its hosted endpoint (https://ai-visibility-index.dev/mcp).
Is the AI Visibility Index MCP server safe to use?
AI Visibility Index scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AI Visibility Index MCP server expose?
AI Visibility Index exposes 3 tools: check_ai_visibility, list_ai_visibility_industries, get_ai_visibility_methodology. Their descriptions and schemas cost roughly 321 tokens of context every time the server is loaded.
Does the AI Visibility Index MCP server require authentication?
No. We connected to AI Visibility Index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AI Visibility Index MCP server still maintained?
AI Visibility Index is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.