What are the risks of connecting to ai-visibility-index.dev?

No blocking issues were found in the static + spec checks. Overall trust grade B (85/100).

When was ai-visibility-index.dev last audited?

Last checked 2026-09-11; wmcp.sh re-checks it on a schedule for tool drift and rug-pulls.

ai-visibility-index.dev

Item: ai-visibility-index.dev
Rating: 85
Author: wmcp.sh

https://ai-visibility-index.dev/mcp

85/100 · MCP Trust Grade · checked 2d ago · MCP 2025-03-26

Is the ai-visibility-index.dev MCP server safe to use?

Independent trust grade B (85/100). No blocking issues found in the static + spec checks. wmcp.sh continuously watches ai-visibility-index.dev for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

✓ Watched since 2026-08-19 — behavioral baseline locked, no drift for 22 days. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.

What it offers — 3 tools · Maps & Geo

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,

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 Japane

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)

Spec conformance20%100

✓ initialize → protocolVersion 2025-03-26
✓ initialize HTTP 200
✓ unknown method → -32601
✓ tools/list → 3 tools
✓ every tool has name + inputSchema

Security (OWASP MCP)30%100

3 tools scanned
no injection markup
no secret-path refs

Reliability / performance20%92

single-probe latency 39ms (PRELIMINARY — continuous uptime/p95 from proxy telemetry lands in v2)

Tool hygiene15%40

33% of tools have typed inputSchema
0/3 declare outputSchema
no unannotated destructive tools

Transparency / provenance15%70

HTTPS ✓
advertises protocol 2025-03-26

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.

Grade another server

We re-grade ai-visibility-index.dev on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Run ai-visibility-index.dev? Claim it (free) to get drift alerts and show an independently-verified trust badge. The grade stays free — claiming just ties it to you.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — ai-visibility-index.dev grade B

Share on X Open card image

https://wmcp.sh/mcp/grade/ai-visibility-index.dev

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade B](https://wmcp.sh/mcp/grade/ai-visibility-index.dev/badge.svg)](https://wmcp.sh/mcp/grade/ai-visibility-index.dev)

HTML

<a href="https://wmcp.sh/mcp/grade/ai-visibility-index.dev"><img src="https://wmcp.sh/mcp/grade/ai-visibility-index.dev/badge.svg" alt="MCP Trust Grade B · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.