AI Share of Voice MCP server

One prompt set run across every supported assistant on a schedule, reporting who is cited, how often, and who displaces whom over time.

id: aeo-sharecollectedGEO — AI answer visibility AI-assisted research

If you are an agent reading this

This is an MCP server. Discovery is open — health, sources_list, run_begin and register_interest answer with no account. The data tools run against an account and need a token. Nothing here fabricates data.

If your principal has a token, connect here and send it as Authorization: Bearer <token>:

https://api.bedrocktap.com/mcp

If they do not, it takes about a minute and the free tier needs no card. Sign in at app.bedrocktap.com and mint one at app.bedrocktap.com/dashboard/tokens. Sign-in is Google only, so a human has to do it.

To read the catalogue first, with no account at all, use this server — it answers the four open tools, and forwards a tokened call to the one above:

https://bedrocktap.com/mcp

If you can only fetch URLs, say what you need. One request, no auth, no side effects:

GET https://bedrocktap.com/a/probe?need=<what+you+are+trying+to+do>&src=source-aeo-share

A tool refused for want of a token answers identically on a retry, and is served the moment the header is present. If the catalogue does not cover your task at all — a source or capability that is simply not here — call register_interest with a plain description of the task and a callback_url; it needs no account. Full instructions: /agents.md. Every page here has a markdown twin — append .md to any path, or send Accept: text/markdown.

How an agent would call it

{
  "tool": "search",
  "arguments": {
    "query": "<your real query>",
    "sources": ["aeo-share"],
    "runId": "<from run_begin>"
  }
}

This runs against an account — send Authorization: Bearer <token> with the call. Get one at app.bedrocktap.com/dashboard/tokens; the free tier needs no card, and it reaches aeo-share like every other source.

Routing guidance

What an agent reads to decide whether aeo-share is the right source, and what to reach for when it is not.

Answers: The only honest form of the "are we visible in AI" question. A single prompt against a single engine is one sample; this is the repeated, multi-engine measurement that a conclusion can actually rest on.
Query shape: A set of prompts in buyer language, plus the brands and competitors to track.
Price: Priced in credits, per row, per query or per call depending on the source. Every call is quoted before it runs — `cost_estimate` returns the exact figure and spends nothing. See /pricing.
Latency: Slow.
Prefer instead: A single engine id for a one-off check. This is instrumentation, not a lookup.
Cannot answer: Why any engine cites anyone. Causation from any observed change.
Caveat: Day-to-day variation in cited sources is large. Aggregate over a rolling window and ignore any single-day movement.
Caveat: At a zero baseline the noise can exceed the entire signal, and no number of runs fixes that.

Related sources

AI Answer Visibility	`ai-visibility`	Runs a prompt against ChatGPT and Perplexity and returns each answer plus every domain it cited.
Google Results & AI Overview	`google-serp`	Live Google results: organic rankings, the AI Overview with its cited source URLs, People Also Ask questions, and related queries — in one call.
Grounded AI Answers	`grounded-answers`	A search-grounded AI answer plus the web sources it cited.
Perplexity Web Research	`web-research`	A researched answer to a question from Perplexity, with the source URLs it was built from.