Proofsource
co.proofsource/proofsourceVersion 1.0.0AI visibility: which buyer questions name your brand in ChatGPT, Perplexity, Claude, AI Overviews.
Status
Responds229 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:43 UTC
- Latency
- 229 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://app.proofsource.co/v1/mcpResponds229 msNo sign-in
Claude Code
claude mcp add --transport http proofsource https://app.proofsource.co/v1/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: proofsource
Remote MCP server URL: https://app.proofsource.co/v1/mcpCursor
{
"mcpServers": {
"proofsource": {
"url": "https://app.proofsource.co/v1/mcp"
}
}
}VS Code
code --add-mcp '{"name":"proofsource","type":"http","url":"https://app.proofsource.co/v1/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
15 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
add_brandStart measuring a brand: does ChatGPT, Perplexity, Claude or Google AI mention it, and who does AI recommend instead? Give the brand's website (or its app store, Google Maps, YouTube or Instagram link). It reads the site, picks the buyer questions, and starts the first scan across the AI engines. Reading the site takes 1-2 minutes; if it is still running, call again with the same link and it picks up the same run, never a second one. Returns the brand_id; then use get_scan_status. | No | No | Yes | Yes |
create_promptAdds a buyer question to a topic so it is asked on every engine in the plan from the next run. Counts toward the plan's question limit. Calling again with the same text returns the existing question, never a duplicate. | No | No | Yes | No |
get_changesWhat moved over the window: the daily mention-rate trend, how much the engines' answers changed, notable changes on competitors' websites, and new pages about the category. | No | Yes | Yes | No |
get_citationsThe websites AI answers cite for the brand's buyer questions, ranked by share of citations and by how many answers cite them, and where the brand's own site ranks. | No | Yes | Yes | No |
get_competitorsThe competitors AI answers name for the brand's buyer questions, per engine, with each one's share of voice against the brand and how it changed over the window. | No | Yes | Yes | No |
get_fix_verificationEach fix marked shipped for the brand with its mention rate before and after and a verdict: moved (beyond normal answer churn), within_noise, or awaiting_samples. Fixes marked "Not a fix" are left out; auto-detected page changes carry source auto_detected. | No | Yes | Yes | No |
get_loopThe brand's loop, oldest first: each buyer question tracked, gap found, content draft created, fix published to the brand's site, fix shipped, change seen on the brand's own pages, and fix checked after it ships: a first check on day 28, re-checks on days 45, 60 and 75 and a final check on day 90 (whether it is still live and how citations, mentions and AI-referral traffic moved, each with its sample size; a horizon appears only once it has been measured). The first page also lists before_window: each question's newest draft, publish and shipped fix from before since, its current state. At most 90 days per call (the last N days is since = today minus N-1, today counted); page with next_cursor. | No | Yes | Yes | No |
get_report_linkA link to the brand's AI visibility report to share with a team or client: how often AI answers mention the brand, which competitors they name instead, and which sources they cite. Returns the newest finished report's own unlisted link. Reports are built automatically after a brand's first scan. | No | Yes | Yes | No |
get_scan_statusProgress of a brand's first scan after add_brand: the stage, how many AI answers are in out of how many expected, per engine, and when it should finish. Once complete, use get_visibility for the results. | No | Yes | Yes | No |
get_visibilityHow often ChatGPT, Perplexity, Claude and Google AI mention the brand when buyers ask about its category. by=engine (default): mention rate, share of voice, average position, citation share and sentiment per engine, with the change from the previous period. by=question: each buyer question's mention rate and rank. A brand measured in several locations also gets locations: each location's mention rate, change and the competitor AI names most there, weakest first. | No | Yes | Yes | No |
list_brandsThe brands this workspace tracks in AI answers, with ids and websites. Call first; every other tool takes a brand_id. | No | Yes | Yes | No |
list_fix_opportunitiesThe gaps that keep AI engines from citing or recommending the brand, each with its evidence and the suggested fix. Gives the gap_id mark_fix_shipped needs. | No | Yes | Yes | No |
list_topicsThe topics and buyer questions this workspace asks ChatGPT, Perplexity, Claude and Google AI for a brand. Gives the topic_id create_prompt needs. | No | Yes | Yes | No |
mark_fix_shippedRecords that a fix shipped, against a gap_id from list_fix_opportunities or a published content_draft_id, so get_fix_verification can measure whether it moved the brand's mention rate. Calling again with the same fix and description returns the existing record. | No | No | Yes | No |
see_exampleShows what Proofsource measures, without signing in: a real visibility card for one example brand (Tesla), from answers collected from ChatGPT, Perplexity, Claude and Google AI Overviews. It shows how often AI answers mention the brand, per engine, which competitors they name instead, and sample answers. Use it when someone asks whether their brand shows up in AI answers and has not signed in. It always shows the example brand; to check their own brand they sign in. | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Oct 13, 2026
- Updated
- Oct 13, 2026
- Categories (suggested)
- AI modelsMarketing and SEOSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared