Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.justinmckelvey/ai-visibility-check

REMOTE · JUSTINMCKELVEY.COM

Free AI visibility check: is your business cited when customers ask AI? Score plus competitors.

0 this week 84 Trust /100

Last scanned (1 hour ago)

Scores higher than 89% of remote servers

Unreachable for 1 day in a row. Last reached 4 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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 Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

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.

  • 5 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 28 Sept 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
  • 25 Sept 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
  • 21 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 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
  • 24 Aug 26 0
    • Authorization: unverified → partial ▲ security
  • 23 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 22 Aug 26 0

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Probed https://justinmckelvey.com/mcp

TLS unreached
DNSSEC insecure

Validation of justinmckelvey.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
justinmckelvey.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://justinmckelvey.com/mcp Unreachable
http (plaintext) http://justinmckelvey.com/mcp HTTPS enforced
MCP tools · 1 exposed · ~261 tokens

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 →

Tool Tokens
check_ai_visibility ~261

Check whether a business is visible to AI answer engines. Runs each query through a live AI search (Perplexity) and reports whether the business's site is cited, at what rank, and who gets cited instead. Pass 1-5 realistic customer-intent questions — what a potential customer would actually ask an AI (e.g. "best kitchen remodeler in Clearwater FL"). Never include the business's own name in a query. Returns a 0-100 visibility score, a tier, per-query results, the competing sources AI cited, and a shareable branded scorecard link.

NameTypeReqDescription
business_namestring–Business name as customers say it (improves mention detection)
domainstringyesBusiness website domain, e.g. acme-plumbing.com
emailstring–Optional. Justin also offers a free human-run deep-dive fix report (wider query set, drafted the minute they ask, reviewed by Justin, delivered same day). If the user says they want it, ask for their…
queriesarrayyes1-5 customer-intent questions to test (without the business name)
NameTypeReqDescription
queries_checkedintegeryesQueries that completed (errored queries are excluded from scoring).
queries_citedintegeryesQueries where the business was cited or named.
resultsarrayyesPer-query outcome, in the order the queries were checked.
scoreintegeryes0-100 visibility score: the share of checked queries where the business was cited.
scorecard_urlstringyesShareable branded scorecard page for this result.
tierstringyesPlain-language band for the score.

No examples provided.

Install

How do I install the com.justinmckelvey/ai-visibility-check MCP server?

com.justinmckelvey/ai-visibility-check is a hosted endpoint at https://justinmckelvey.com/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 · justinmckelvey.com

# add to Claude Code
claude mcp add --transport http com-justinmckelvey-ai-visibility-check 'https://justinmckelvey.com/mcp'
Common questions

What is the com.justinmckelvey/ai-visibility-check MCP server?

com.justinmckelvey/ai-visibility-check is an MCP server listed in the public MCP registry as com.justinmckelvey/ai-visibility-check. Free AI visibility check: is your business cited when customers ask AI? Score plus competitors. This page covers its hosted endpoint (https://justinmckelvey.com/mcp).

Is the com.justinmckelvey/ai-visibility-check MCP server safe to use?

com.justinmckelvey/ai-visibility-check scores 84 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 com.justinmckelvey/ai-visibility-check MCP server expose?

com.justinmckelvey/ai-visibility-check exposes 1 tool: check_ai_visibility. Their descriptions and schemas cost roughly 261 tokens of context every time the server is loaded.

Does the com.justinmckelvey/ai-visibility-check MCP server require authentication?

Its publisher declares no required credentials for com.justinmckelvey/ai-visibility-check. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the com.justinmckelvey/ai-visibility-check MCP server still maintained?

com.justinmckelvey/ai-visibility-check is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.