Proofsource
REMOTE · APP.PROOFSOURCE.CO
AI visibility: which buyer questions name your brand in ChatGPT, Perplexity, Claude, AI Overviews.
Available components
Last scanned (7 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1992 tokens (~132/item across 15 items; 14 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 0
- “mark_fix_shipped” added an optional parameter “acknowledge_unfilled_gaps” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “add_brand” rewrote its description, which is the text the model reads security
- Tool “create_prompt” rewrote its description, which is the text the model reads security
- Tool “list_brands” rewrote its description, which is the text the model reads security
- Tool “list_topics” rewrote its description, which is the text the model reads security
- Tool “see_example” rewrote its description, which is the text the model reads security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 13 Oct 26 81
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://app.proofsource.co/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=proofsource.co | CN=WE1,O=Google Trust Services,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b61f7275d7c6695c0e7bff383c42432d |
| SANs: proofsource.co, *.proofsource.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.proofsource.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| proofsource.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://app.proofsource.co/.well-known/oauth-protected-resource/v1/mcp"
Bearer resource_metadata="https://app.proofsource.co/.well-known/oauth-protected-resource/v1/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=() |
Protected resource metadata
| Document | https://app.proofsource.co/.well-known/oauth-protected-resource/v1/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://app.proofsource.co/v1/mcp |
| Authorisation server | https://app.proofsource.co |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.proofsource.co/v1/mcp | Verified | 400 | |
| http (plaintext) | http://app.proofsource.co/v1/mcp | HTTPS enforced | 301 | https://app.proofsource.co/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_brand Check my brand in AI answers ~180
Start 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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional: what the brand sells, in a sentence. Only needed when add_brand says it couldn't read the website. |
| link | string | yes | The brand's website, like acme.com, or its app store, Google Maps, YouTube or Instagram link. |
No output schema declared.
No examples provided.
create_prompt Track a new buyer question ~133
Adds 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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_new_engines | boolean | – | Set true to confirm using an engine this workspace has never used before. |
| target_engines | array | – | Optional: limit to these engines. Omit for the plan's engines. |
| text | string | yes | The question, phrased the way a buyer would ask an AI assistant. |
| topic_id | string | yes | Topic id from list_topics. |
No output schema declared.
No examples provided.
get_changes What changed in my AI visibility? ~88
What 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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. May be omitted when the workspace tracks a single brand. |
| window_days | integer | – | Trailing window in whole UTC days ending today. Default 30. |
No output schema declared.
No examples provided.
get_citations Which sources do AI answers cite? ~170
The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. May be omitted when the workspace tracks a single brand. |
| engines | array | – | Optional: only these engines (e.g. openai, perplexity, anthropic, google_aio). Default: the engines the dashboard headline counts (ChatGPT, Perplexity, Claude, Google AI Overviews, plus any the plan… |
| limit | integer | – | Max sites per ranking. Default 25. |
| window_days | integer | – | Trailing window in whole UTC days ending today. Default 30. |
No output schema declared.
No examples provided.
get_competitors Who does AI recommend instead of me? ~154
The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. May be omitted when the workspace tracks a single brand. |
| engines | array | – | Optional: only these engines (e.g. openai, perplexity, anthropic, google_aio). Default: the engines the dashboard headline counts (ChatGPT, Perplexity, Claude, Google AI Overviews, plus any the plan… |
| window_days | integer | – | Trailing window in whole UTC days ending today. Default 30. |
No output schema declared.
No examples provided.
get_fix_verification Did my fix work? ~121
Each 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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. May be omitted when the workspace tracks a single brand. |
| fix_event_id | string | – | Optional: just this fix. |
| limit | integer | – | Most recent fixes to return. Default 20. |
No output schema declared.
No examples provided.
get_report_link Get a shareable AI visibility report ~96
A 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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands or add_brand. May be omitted when the workspace tracks a single brand. |
No output schema declared.
No examples provided.
get_scan_status Is my brand's scan done? ~82
Progress 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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands or add_brand. May be omitted when the workspace tracks a single brand. |
No output schema declared.
No examples provided.
get_visibility Is my brand mentioned in AI answers? ~200
How 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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. May be omitted when the workspace tracks a single brand. |
| by | string | – | engine (default) or question. |
| engines | array | – | Optional: only these engines (e.g. openai, perplexity, anthropic, google_aio). Default: the engines the dashboard headline counts (ChatGPT, Perplexity, Claude, Google AI Overviews, plus any the plan… |
| window_days | integer | – | Trailing window in whole UTC days ending today. Default 30. |
No output schema declared.
No examples provided.
list_brands List my tracked brands ~34
The brands this workspace tracks in AI answers, with ids and websites. Call first; every other tool takes a brand_id.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_fix_opportunities What should I fix to show up in AI answers? ~88
The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. May be omitted when the workspace tracks a single brand. |
| include_closed | boolean | – | Also return gaps that were checked and no longer apply. Default false. |
No output schema declared.
No examples provided.
list_topics Which buyer questions are tracked? ~64
The topics and buyer questions this workspace asks ChatGPT, Perplexity, Claude and Google AI for a brand. Gives the topic_id create_prompt needs.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. May be omitted when the workspace tracks a single brand. |
No output schema declared.
No examples provided.
mark_fix_shipped I shipped a fix ~216
Records 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.
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledge_unfilled_gaps | boolean | – | A content draft that still has [INSERT ...] gaps is refused and the gaps listed. Set true only after the user confirms the shipped page has them filled. |
| brand_id | string | – | Brand id from list_brands. May be omitted when the workspace tracks a single brand. |
| content_draft_id | string | – | A published content draft (one of gap_id or content_draft_id). |
| description | string | yes | What shipped, in one or two sentences. |
| gap_id | string | – | The gap finding the fix addresses (one of gap_id or content_draft_id). |
| shipped_at | string | – | When it shipped: RFC 3339 timestamp or YYYY-MM-DD. Default now. |
No output schema declared.
No examples provided.
see_example See an example AI visibility card ~139
Shows 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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | Optional: the brand the person asked about. The example card is shown either way, with a note to sign in to check that brand. |
No output schema declared.
No examples provided.
How do I install the Proofsource MCP server?
Proofsource is a hosted endpoint at https://app.proofsource.co/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · app.proofsource.co
claude mcp add --transport http co-proofsource-proofsource 'https://app.proofsource.co/v1/mcp'
What is the Proofsource MCP server?
Proofsource is an MCP server listed in the public MCP registry as co.proofsource/proofsource. AI visibility: which buyer questions name your brand in ChatGPT, Perplexity, Claude, AI Overviews. This page covers its hosted endpoint (https://app.proofsource.co/v1/mcp).
Is the Proofsource MCP server safe to use?
Proofsource scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Proofsource MCP server expose?
Proofsource exposes 14 tools: list_brands, list_topics, get_visibility, get_competitors, get_citations, and 9 more. Their descriptions and schemas cost roughly 1,765 tokens of context every time the server is loaded.
Does the Proofsource MCP server require authentication?
Yes. Proofsource asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Proofsource MCP server still maintained?
Proofsource is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.