frontstat
Registry code: 939da622342dff17
FrontStat measures whether AI search engines (ChatGPT, Claude, Gemini) recommend a startup's product. check_public_launch works for anyone. The other tools read the caller's own FrontStat reports and need their dashboard token as a Bearer token.
- endpoint
- https://frontstat.com/api/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is frontstat live?
- Yes — it answered the hub's last check (checked 3h ago). It answered 98% of checks over the last 30 days.
- Is frontstat free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does frontstat have?
- 6 tools: check_public_launch, list_buyer_questions, cited_sites, who_wins_instead, visibility_history, get_visibility.
- Is frontstat safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 98.5%· all time 98.5%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- down → live
- degraded → down· HTTP 402: vercel DEPLOYMENT_DISABLED
- live → degraded· HTTP 402: vercel DEPLOYMENT_DISABLED
- used for
- check if ai search recommends a product
- list sites ai engines cite
- track ai visibility score
- find competitors named instead
- takes → gives
- text → data
- tools
- 6 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_buyer_questions reads auth-required never probed
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.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linescited_sites reads auth-required 3h ago
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.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 lineswho_wins_instead reads auth-required 3h ago
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.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesvisibility_history reads auth-required 19h ago
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.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_visibility reads auth-required 3h ago
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.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linescheck_public_launch reads unknown 19h ago
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.
{ "type": "object", "required": [ "domain" ], "properties": { "domain": { "type": "string", "maxLength": 300, "description": "The product's domain or URL, for example example.com." } }, "additionalProperties": false }arguments 14 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id939da622342dff17.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/939da622342dff17/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/939da622342dff17?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.