SurfacedBy AI Visibility & GEO Audit
REMOTE · API.SURFACEDBY.COM
Free AI visibility and GEO audit: see what AI reads on your site and whether its answers cite you.
Available components
Last scanned (19 hours ago)
Scores higher than 63% of remote servers
Reachable. Last reached 22 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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- 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 1256 tokens (~251/item across 5 items; 5 tools + 0 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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 0
- Schema quality: 187 → 251 ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +7
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- 16 Oct 26 −6
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Tool “surfacedby_analyze_answer_evidence” rewrote its description, which is the text the model reads security
- Tool “surfacedby_inspect_page_evidence” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: 100 functional
- Schema quality: fair → good functional
- New prompt “check_ai_answers” functional
- New prompt “compare_with_competitors” functional
- New prompt “fix_ai_crawler_access” functional
- New prompt “full_ai_visibility_audit” functional
- New resource “ai-visibility-audit-method” functional
- New resource “ai-visibility-research-findings” functional
- Server version: 1.27.2 → 1.28.1 functional
- New tool “surfacedby_check_ai_crawler_access” functional
- New tool “surfacedby_get_ai_source_landscape” functional
- New tool “surfacedby_plan_ai_visibility_audit” functional
- “surfacedby_analyze_answer_evidence” added an optional parameter “competitor_domains” cosmetic
- “surfacedby_analyze_answer_evidence” added an optional parameter “platform” cosmetic
- Tool “surfacedby_analyze_answer_evidence” changed its title: Analyze visible answer evidence → Check whether an AI answer cites or names you cosmetic
- Tool “surfacedby_inspect_page_evidence” changed its title: Inspect website facts for AI visibility → Audit website pages the way AI reads them cosmetic
- 12 Oct 26 66
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 22 Oct 2026 · Probed https://api.surfacedby.com/api/v1/mcp/public/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=surfacedby.com | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 659fb87eec9de46e0e489001626ec316 |
| SANs: surfacedby.com, *.surfacedby.com | ||||||
| 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 api.surfacedby.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| surfacedby.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.surfacedby.com/api/v1/mcp/public/ | Verified | 200 | |
| http (plaintext) | http://api.surfacedby.com/api/v1/mcp/public/ | HTTPS enforced | 301 | https://api.surfacedby.com/api/v1/mcp/public/ |
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 →
surfacedby_analyze_answer_evidence Check whether an AI answer cites or names you ~145
Check one AI answer the user pasted: whether it cites the business with a link, names it without one, or leaves it out. Classifies every cited source, such as review sites, best-of lists, forums, competitors and the business's own pages, reads Google and Gemini redirect links to the pages they point to, summarizes which source types dominate, and gives the likely reason and fix when the business is not cited. Runs no AI queries of its own.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | – |
| brand_name | – | – | – |
| business_url | string | yes | – |
| competitor_domains | array | – | – |
| language | – | – | – |
| platform | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| answer_sha256 | string | yes | – |
| brand_name_ambiguous | boolean | yes | – |
| business_citations | array | yes | – |
| cited_sources | array | – | – |
| diagnosis | – | – | – |
| evidence_kind | string | – | – |
| limitations | array | – | – |
| matched_terms | array | yes | – |
| next_steps | array | – | – |
| platform | – | – | – |
| presence | string | yes | – |
| source_concentration | – | – | – |
| visible_citations | array | yes | – |
No examples provided.
surfacedby_check_ai_crawler_access Check AI crawler access ~107
Check which AI crawlers a site allows, restricts or blocks in robots.txt, what that means for each AI platform and the search index it reads, where to submit pages, whether a security challenge answers an ordinary request, homepage noindex, llms.txt and Content-Signal, with copy-ready fixes. Reads the site's public files and one ordinary page request; firewall rules keyed to crawlers' own IP addresses are not visible.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| budget | – | – | – |
| citation_crawlers_blocked | array | – | – |
| content_signal | – | yes | – |
| crawlers | array | yes | – |
| domain | string | yes | – |
| evidence_kind | string | – | – |
| evidence_provider | string | – | – |
| fixes | – | yes | – |
| homepage | – | yes | – |
| limitations | array | – | – |
| llms_txt | – | yes | – |
| next_steps | array | – | – |
| observed_at | string | yes | – |
| platforms | array | yes | – |
| robots_txt | – | yes | – |
No examples provided.
surfacedby_get_ai_source_landscape See where AI platforms get their answers ~90
Show, for each AI platform, the mix of source types it cites, recent shifts in specific sources and how its answers cite, from SurfacedBy's published AI Search Index, with the data date, the public page and related research findings with links. Rates are pooled across many brands and describe each platform, not any one business.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | – | – | – |
| topic | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| corpus_answers | – | – | – |
| corpus_citations | – | – | – |
| data_through | – | – | – |
| evidence_kind | string | – | – |
| limitations | array | – | – |
| next_steps | array | – | – |
| platforms | array | – | – |
| research_findings | array | – | – |
| source_url | string | yes | – |
| status | string | yes | – |
| window_days | – | – | – |
No examples provided.
surfacedby_inspect_page_evidence Audit website pages the way AI reads them ~103
Read up to five public pages the way an AI crawler receives them, without running JavaScript. Returns sourced sections, table cells, internal and outside links and declared structured data, plus each page's type, source type and readiness findings with the documentation behind them, repeated declared facts to review, and the remaining request budget. Partial or unreadable pages are reported as such. Runs no AI queries and measures no visibility.
| Name | Type | Req | Description |
|---|---|---|---|
| urls | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| budget | – | – | – |
| declaration_review | – | – | – |
| evidence_kind | string | – | – |
| evidence_provider | string | – | – |
| limitations | array | – | – |
| next_steps | array | – | – |
| pages | array | yes | – |
| status | string | yes | – |
No examples provided.
surfacedby_plan_ai_visibility_audit Plan an AI visibility audit ~100
Return the ordered checklist for an AI visibility audit of a business website: each step, the tools for it, the quality bar for the result, the rules to follow, the published research findings that apply to the goal, and the remaining request budget. Makes no request to the website.
| Name | Type | Req | Description |
|---|---|---|---|
| business_url | string | yes | – |
| competitors | array | – | – |
| goal | – | – | – |
| language | – | – | – |
| market | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| budget | – | – | – |
| business_url | string | yes | – |
| evidence_kind | string | – | – |
| goal | string | yes | – |
| goal_description | string | yes | – |
| goal_label | string | yes | – |
| guardrails | array | yes | – |
| interpreting_results | array | yes | – |
| known_competitors | array | – | – |
| language | – | – | – |
| market | – | – | – |
| method_version | string | yes | – |
| next_steps | array | – | – |
| quality_bar | array | yes | – |
| research_findings | array | yes | – |
| steps | array | yes | – |
| tracking | – | yes | – |
| workflow_rule | string | yes | – |
No examples provided.
How do I install the SurfacedBy AI Visibility & GEO Audit MCP server?
SurfacedBy AI Visibility & GEO Audit is a hosted endpoint at https://api.surfacedby.com/api/v1/mcp/public/, 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 · api.surfacedby.com
claude mcp add --transport http com-surfacedby-ai-visibility 'https://api.surfacedby.com/api/v1/mcp/public/'
What is the SurfacedBy AI Visibility & GEO Audit MCP server?
SurfacedBy AI Visibility & GEO Audit is an MCP server listed in the public MCP registry as com.surfacedby/ai-visibility. Free AI visibility and GEO audit: see what AI reads on your site and whether its answers cite you. This page covers its hosted endpoint (https://api.surfacedby.com/api/v1/mcp/public/).
Is the SurfacedBy AI Visibility & GEO Audit MCP server safe to use?
SurfacedBy AI Visibility & GEO Audit scores 72 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 SurfacedBy AI Visibility & GEO Audit MCP server expose?
SurfacedBy AI Visibility & GEO Audit exposes 5 tools: surfacedby_inspect_page_evidence, surfacedby_analyze_answer_evidence, surfacedby_check_ai_crawler_access, surfacedby_get_ai_source_landscape, surfacedby_plan_ai_visibility_audit. Their descriptions and schemas cost roughly 545 tokens of context every time the server is loaded.
Does the SurfacedBy AI Visibility & GEO Audit MCP server require authentication?
No. We connected to SurfacedBy AI Visibility & GEO Audit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SurfacedBy AI Visibility & GEO Audit MCP server still maintained?
SurfacedBy AI Visibility & GEO Audit is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.