justinmckelvey-ai-visibility
Registry code: d8173a2e646a835f
Free AI-visibility checker. Use check_ai_visibility to test whether a business gets cited when customers ask AI assistants for recommendations. Generate customer-intent queries yourself (never include the business's own name in them).
- endpoint
- https://justinmckelvey.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is justinmckelvey-ai-visibility live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is justinmckelvey-ai-visibility free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does justinmckelvey-ai-visibility have?
- 1 tool: check_ai_visibility.
- Is justinmckelvey-ai-visibility 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.
90 days 99.6%· all time 99.6%
last good check
of 1 tools
- degraded → live
- degraded → live
- live → degraded· HTTP 502
- unknown → live
- used for
- check if a business is cited by ai assistants
- test ai search visibility for customer queries
- takes → gives
- text → data
- tools
- 1 reads
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.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
check_ai_visibility reads unknown 15h ago
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.
{ "type": "object", "required": [ "domain", "queries" ], "properties": { "email": { "type": "string", "description": "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 email and pass it here. Only pass an email the user explicitly provided — never invent or reuse one." }, "domain": { "type": "string", "description": "Business website domain, e.g. acme-plumbing.com" }, "queries": { "type": "array", "items": { "type": "string" }, "maxItems": 5, "minItems": 1, "description": "1-5 customer-intent questions to test (without the business name)" }, "business_name": { "type": "string", "description": "Business name as customers say it (improves mention detection)" } } }arguments 30 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idd8173a2e646a835f.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/d8173a2e646a835f/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/d8173a2e646a835f?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.