com.frontstat/visibility
REMOTE · FRONTSTAT.COM
See whether ChatGPT, Claude and Gemini recommend a startup's product, and who they name instead.
Available components
Last scanned (15 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 21 Nov 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 Security80
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 529 tokens (~88/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 13 Nov 26 0
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 12 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Nov 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “cited_sites” rewrote its description, which is the text the model reads security
- Tool “get_visibility” rewrote its description, which is the text the model reads security
- Tool “list_buyer_questions” rewrote its description, which is the text the model reads security
- Tool “visibility_history” rewrote its description, which is the text the model reads security
- Tool “who_wins_instead” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Nov 2026 · Probed https://frontstat.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=frontstat.com | CN=YR2,O=Let's Encrypt,C=US | 18 Nov 2026 | 16 Feb 2027 | RSA 2048 | SHA256-RSA | 6fb1d059e1d24eba4ac023a31887ccbaaf0 |
| SANs: frontstat.com, www.frontstat.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of frontstat.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| frontstat.com. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://frontstat.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://frontstat.com/api/mcp | HTTPS enforced | 308 | https://frontstat.com/api/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 →
check_public_launch Check a launch FrontStat tracks ~116
Look up a product launch that FrontStat already tracks: its name, its rank on this week's or this month's launch board, its visibility score (0 to 100), and whether ChatGPT, Claude and Gemini recommend it for its buyer question, with the products they name instead. Returns a link to its public FrontStat page. If FrontStat does not track the domain yet, says so and links to the free report. No token needed.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The product's domain or URL, for example example.com. |
No output schema declared.
No examples provided.
cited_sites Sites AI search engines cite ~73
The sites the AI search engines cite most when they answer your buyer questions, with how many answers cite each one, your own domain left out. These are the pages to get mentioned on. Needs a FrontStat plan (Lite or Pro): send your dashboard token as a Bearer token. Covers the domain on your subscription.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_visibility Your AI visibility today ~83
Your latest FrontStat report: date, visibility score, whether each AI search engine recommends your product for your main buyer question and who it names instead, and for your buyer questions how many answers recommend you (X of Y) per assistant. Needs a FrontStat plan (Lite or Pro): send your dashboard token as a Bearer token. Covers the domain on your subscription.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_buyer_questions Your buyer questions ~65
Each buyer question FrontStat asks the AI search engines about your market, with yes or no per engine: does the answer recommend your product. Needs a FrontStat plan (Lite or Pro): send your dashboard token as a Bearer token. Covers the domain on your subscription.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
visibility_history Your visibility over 30 days ~69
One point per day for the last 30 days: your visibility score and how many answers recommend your product. Use it to see whether your changes moved AI search engines. Needs a FrontStat plan (Lite or Pro): send your dashboard token as a Bearer token. Covers the domain on your subscription.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
who_wins_instead Who wins instead of you ~70
The products the AI search engines name instead of yours, and the sites they cite, each with how many answers it appears in, from your latest Pro report. Needs a FrontStat plan (Lite or Pro): send your dashboard token as a Bearer token. Covers the domain on your subscription.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the com.frontstat/visibility MCP server?
com.frontstat/visibility is a hosted endpoint at https://frontstat.com/api/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 · frontstat.com
claude mcp add --transport http com-frontstat-visibility 'https://frontstat.com/api/mcp'
What is the com.frontstat/visibility MCP server?
com.frontstat/visibility is an MCP server listed in the public MCP registry as com.frontstat/visibility. See whether ChatGPT, Claude and Gemini recommend a startup's product, and who they name instead. This page covers its hosted endpoint (https://frontstat.com/api/mcp).
Is the com.frontstat/visibility MCP server safe to use?
com.frontstat/visibility scores 87 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 com.frontstat/visibility MCP server expose?
com.frontstat/visibility exposes 6 tools: check_public_launch, get_visibility, list_buyer_questions, who_wins_instead, cited_sites, visibility_history. Their descriptions and schemas cost roughly 476 tokens of context every time the server is loaded.
Does the com.frontstat/visibility MCP server require authentication?
No. We connected to com.frontstat/visibility without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.frontstat/visibility MCP server still maintained?
com.frontstat/visibility is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the com.frontstat/visibility MCP server?
VerifyMCP ran 13 checks on com.frontstat/visibility, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.