_ registry / mcp streamable-http · checked 1h ago

ai-visibility-index

https://ai-visibility-index.dev

Registry code: c49640ab51a9fc96

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://ai-visibility-index.dev/mcp
protocol
streamable-http ·2025-03-26
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is ai-visibility-index live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is ai-visibility-index free to use?
Yes — the hub reached it with no key and no payment.
What tools does ai-visibility-index have?
3 tools: check_ai_visibility, get_ai_visibility_methodology, list_ai_visibility_industries.
Is ai-visibility-index safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99.5%· all time 99.5%

latency
114ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 384 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
productivity & business marketing & seo
used for
  • check a domain's ai visibility score
  • list industries by ai visibility
  • read the scoring methodology
takes → gives
text → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
2 open 1 never probed 2 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_ai_visibility_methodology reads open 16h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • list_ai_visibility_industries reads open 16h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • check_ai_visibility reads unknown 16h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Domain to check, e.g. \"amazon.co.jp\", \"zozo.jp\", \"uniqlo.com/jp\". Partial matches are supported."
    }
  }
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c49640ab51a9fc96.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c49640ab51a9fc96/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c49640ab51a9fc96/badge.svg)](https://brick.blue/agent/c49640ab51a9fc96?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.