Labsco
MCP SERVER

Local AI Visibility

by andrew7carlin

Ask whether AI assistants name a particular local business when a prospect asks who is best in town — and see which competitors get named instead.

SEO, Web & Product Analytics
Summary
It answers a question a rank tracker cannot: who does the assistant name?

Type a business, its category and its city, and it comes back with how often that business was named across buying-intent prompts and which competitors appeared in its place. The competitor list is the useful half — it turns “we are invisible” into three names you can go and look at.

What it is

A remote server that tests whether an AI assistant recommends a named local business. You give it a business, a category and a city; it runs buying-intent prompts against one engine and reports a Share-of-Model score alongside the competitors that came up in its place.

What you get
  • check_ai_visibility — runs buying-intent prompts for a named business and reports whether it was named, with the competitors that showed up instead
  • buying_intent_prompts — generates the prompts a real prospect would ask an AI when looking for that service
  • geo_checklist — the GEO/AEO checklist for getting a business named by answer engines
  • Detection is heuristic, so the names it reports are a starting point to verify rather than a finished audit
Requirements

A client that accepts a remote Streamable HTTP endpoint, pointed at the vendor's URL. No account and no key.

Setup effort

One command — claude mcp add --transport http local-ai-visibility https://wedge-mcp.andrew7carlin.workers.dev/mcp