Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.frontstat/visibility

REMOTE · FRONTSTAT.COM · SCANNED OCT 6

See whether ChatGPT, Claude and Gemini recommend a startup's product, and who they name instead.

Available components

77 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 506 tokens (~84/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 Management17
  • Stability observed for 5 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 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
Install

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

# add to Claude Code
claude mcp add --transport http com-frontstat-visibility 'https://frontstat.com/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-frontstat-visibility": {
      "url": "https://frontstat.com/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-frontstat-visibility": {
      "type": "http",
      "url": "https://frontstat.com/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-frontstat-visibility]
url = "https://frontstat.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-frontstat-visibility": {
      "type": "remote",
      "url": "https://frontstat.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-frontstat-visibility --url 'https://frontstat.com/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-frontstat-visibility:
    url: "https://frontstat.com/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-frontstat-visibility": {
      "Transport": "http",
      "Url": "https://frontstat.com/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-frontstat-visibility -t streamable-http -u 'https://frontstat.com/api/mcp'
// mcp.json
{
  "mcpServers": {
    "com-frontstat-visibility": {
      "type": "http",
      "url": "https://frontstat.com/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 6 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 17. That category is still filling its 30-day observation window: 3 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.

  • 4 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.

  • 3 Oct 26 0
    • Tool “get_visibility” rewrote its description, which is the text the model reads security
  • 2 Oct 26 0
    • 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
    • Stability: unverified → 0.03 ▲ functional
    • Tool “cited_sites” changed its title: Sites the assistants cite → Sites AI search engines cite cosmetic
  • 1 Oct 26 75

    First indexed and scored.

Diagnostics

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 6 Oct 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 16 Sept 2026 15 Dec 2026 RSA 2048 SHA256-RSA 553ed46216492a0af405990c8c3c4b1964a
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. present 19718 13 Verified
frontstat.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
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
MCP tools · 6 exposed · ~452 tokens

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 →

Tool Tokens
check_public_launch ~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.

NameTypeReqDescription
domainstringyesThe product's domain or URL, for example example.com.

No output schema declared.

No examples provided.

cited_sites ~68

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 FrontStat 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 ~79

Your latest FrontStat Pro 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 FrontStat 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 ~60

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 FrontStat 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 ~64

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 FrontStat 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 ~65

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 FrontStat 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.

Common questions

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 77 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 452 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 6 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.