# AI Visibility Index (remote · ai-visibility-index.dev)

AI visibility rankings for 104 Japanese EC companies across ChatGPT, Claude, Gemini, Perplexity.

- Trust score: 70/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- remote · `ai-visibility-index.dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/pulse-digital-dev-mcp-ai-visibility-index/ai-visibility-index.md), [page](https://verifymcp.io/servers/pulse-digital-dev-mcp-ai-visibility-index/ai-visibility-index)

## Channel facts

- Endpoint: `https://ai-visibility-index.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 321 tokens (~107/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http pulse-digital-dev-mcp-ai-visibility-index https://ai-visibility-index.dev/mcp
```

### Codex

```toml
[mcp_servers.pulse-digital-dev-mcp-ai-visibility-index]
url = "https://ai-visibility-index.dev/mcp"
```

### opencode

```json
{
  "$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

```bash
openclaw mcp add pulse-digital-dev-mcp-ai-visibility-index --url https://ai-visibility-index.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  pulse-digital-dev-mcp-ai-visibility-index:
    url: "https://ai-visibility-index.dev/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-04 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-03 (score 69, +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.

### 2026-07-31 (score 68, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 66, +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.

### 2026-07-27 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (3)

### `check_ai_visibility` (~156 tokens)

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検索可視性スコアをドメイン指定で照会。

Input parameters:

- `domain` (string, required): Domain to check, e.g. "amazon.co.jp", "zozo.jp", "uniqlo.com/jp". Partial matches are supported.

### `list_ai_visibility_industries` (~79 tokens)

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可視性スコア平均・企業数・スコア範囲を一覧表示。

### `get_ai_visibility_methodology` (~86 tokens)

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. | スコアリング方法論（計算式・対象エンジン・クエリ種別・データ更新頻度）。

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/pulse-digital-dev-mcp-ai-visibility-index/ai-visibility-index#diagnostics

## Score history

- 2026-08-04: 70
- 2026-08-03: 69
- 2026-08-02: 68
- 2026-08-01: 68
- 2026-07-31: 68
- 2026-07-30: 66
- 2026-07-29: 66
- 2026-07-28: 65
- 2026-07-27: 65
- 2026-07-26: 64

## Links

- Remote endpoint: https://ai-visibility-index.dev/mcp
- Repository: https://github.com/pulse-digital-dev/mcp-ai-visibility-index.git
- Website: https://ai-visibility-index.dev/
- Changelog RSS feed: https://verifymcp.io/servers/pulse-digital-dev-mcp-ai-visibility-index/ai-visibility-index/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/pulse-digital-dev-mcp-ai-visibility-index/ai-visibility-index/changelog.json
- HTML version of this page: https://verifymcp.io/servers/pulse-digital-dev-mcp-ai-visibility-index/ai-visibility-index