AI Visibility Index
REMOTE · AI-VISIBILITY-INDEX.DEV · SCANNED AUG 3
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 →
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 Usability77
- 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · ai-visibility-index.dev
claude mcp add --transport http pulse-digital-dev-mcp-ai-visibility-index 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": {
"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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +2
- 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
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 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
- 26 Jul 26 64
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 3 Aug 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 | 22 Jun 2026 | 20 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 3bcf41c39f42b391131009b42685b6fb |
| 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 |
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=() |
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.
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.