askedthrice
Registry code: aa5f23c366012134
Measure whether AI assistants actually recommend a brand, from measured answers.
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.askedthrice.com/mcp
- protocol
- http-sse ·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 askedthrice live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is askedthrice free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does askedthrice have?
- 2 tools: start_visibility_check, get_visibility_check.
- Is askedthrice 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 99.7%· all time 99.7%
last good check
of 2 tools
- degraded → live
- used for
- check if ai assistants recommend a brand
- measure brand visibility in ai answers
- takes → gives
- text → data
- tools
- 2 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
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
start_visibility_check reads unknown never probed
Measure whether a brand shows up when buyers ask AI assistants for a recommendation. Asks real buyer questions to OpenAI, Anthropic and Gemini and reports what they answered, not what they claim they would answer. Free, no signup, one measurement per domain every 30 days. Returns a runId: call get_visibility_check with it after about a minute. If the domain was already measured this month the response says quota_reached and includes when it ran.
{ "type": "object", "required": [ "brand", "website", "category" ], "properties": { "brand": { "type": "string", "$schema": "https://json-schema.org/draft/2020-12/schema", "maxLength": 80, "minLength": 2, "description": "Brand name as customers write it" }, "website": { "type": "string", "$schema": "https://json-schema.org/draft/2020-12/schema", "maxLength": 160, "description": "Domain, like yourbrand.com" }, "category": { "type": "string", "$schema": "https://json-schema.org/draft/2020-12/schema", "maxLength": 120, "minLength": 2, "description": "What the business sells, in plain words" }, "language": { "enum": [ "en", "es" ], "type": "string", "$schema": "https://json-schema.org/draft/2020-12/schema", "description": "Language the buyer questions are asked in" }, "location": { "type": "string", "$schema": "https://json-schema.org/draft/2020-12/schema", "maxLength": 80, "description": "Where the business competes, like 'Cordoba, Argentina'" }, "competitors": { "type": "string", "$schema": "https://json-schema.org/draft/2020-12/schema", "maxLength": 220, "description": "Up to 5 real competitors, comma separated" } } }arguments 51 linesget_visibility_check reads unknown 18h ago
Collect the result of a measurement started with start_visibility_check. Returns status running while the providers are still answering, so poll every 20 to 30 seconds. When ready it reports a verdict, how many of the buyer questions the brand won, which competitors were named instead, and which providers actually answered.
{ "type": "object", "required": [ "runId" ], "properties": { "runId": { "type": "string", "$schema": "https://json-schema.org/draft/2020-12/schema", "description": "From start_visibility_check" } } }arguments 13 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 idaa5f23c366012134.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/aa5f23c366012134/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/aa5f23c366012134?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.