Measures brand visibility, competitors, citations, changes, and fix outcomes across major AI answer engines.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
Clients with native remote MCP support can connect directly to this URL instead of the install method above.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Proofsource.
list_brandsThe brands this Proofsource workspace tracks in AI answers, with ids and websites. Call first; every other tool takes a brand_id.
list_topicsThe topics and buyer questions Proofsource asks ChatGPT, Perplexity, Claude and Google AI for a brand. Gives the topic_id create_prompt needs.
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.
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.
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.
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.
The Proofsource MCP server measures how often AI-generated answers mention or recommend a tracked brand. It works across ChatGPT, Perplexity, Claude, and Google AI Overviews, using buyer questions associated with the brand's tracked topics.
Results include mention rate, share of voice, average position, citation share, and sentiment. You can examine results by engine or by individual buyer question. Additional tools identify competitors named instead of the brand, the websites cited in answers, changes during a selected period, and gaps that may prevent AI systems from citing or recommending the brand.
A workspace can also record shipped fixes and later compare mention rates before and after the change. Verification classifies the result as moved, within normal answer variation, or awaiting enough samples.
Start by listing the brands in the workspace. Most brand-specific tools require the returned brand_id. Topics and buyer questions are available through list_topics; create_prompt can add a question to a topic for future engine runs, subject to the plan's question limit.
For a new measurement, add_brand accepts a website or an app store, Google Maps, YouTube, or Instagram link. Proofsource reads the supplied source, selects buyer questions, and begins an initial scan. get_scan_status reports progress by stage and engine. Once the scan is complete, visibility, competitor, citation, and change tools can retrieve the results.
The see_example tool provides an unsigned example using Tesla. It is intended to demonstrate the type of visibility data available; checking a user's own brand requires signing in.
The remote MCP endpoint is https://app.proofsource.co/v1/mcp. It uses OAuth 2.1 and a Proofsource email with a one-time sign-in code. In Claude, add the endpoint as a custom connector. In Claude Code, add it with the HTTP transport and then authenticate through /mcp. Cursor, VS Code, Cline, Windsurf, and other MCP clients can add it as a remote Streamable HTTP server.
Claude users can also install the supplied plugin through the Claude plugin marketplace. The plugin provides an AI visibility audit and a fix-planning skill, and its setup then asks the user to select the Proofsource MCP server and sign in.
New accounts using a work email receive two free scans. Personal email addresses can create an account but do not receive scans.
Read tools cover:
Write tools cover adding a brand, creating a buyer question, and marking a fix as shipped. These actions apply to the user's workspace and are restricted by the account's plan and role. Repeating an identical brand addition, prompt, or shipped fix does not create a duplicate record.
The initial site-reading step can take one to two minutes. A scan must finish before its visibility results are available, and report links are generated from the newest completed report. Added questions run from the next engine run rather than changing past measurements.
Fix verification depends on subsequent samples and may remain awaiting samples or fall within normal answer churn. The service measures the engines and questions configured in the Proofsource plan; adding questions counts toward the plan's limit.
Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/proofsource)<a href="https://allmcps.com/mcp/proofsource"><img src="https://allmcps.com/api/badge/proofsource?style=directory" alt="Proofsource on AllMCPs" /></a>