cited
https://cited-api-production.up.railway.app
Registry code: b9fca0806cf3c379
AI-answer-engine visibility scans for local businesses, as agent tools
from a public catalogue that lists it, not from the operator
- endpoint
- https://cited-api-production.up.railway.app/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 cited live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is cited free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does cited have?
- 9 tools: cited_report, cited_scan, cited_api_docs, cited_examples, cited_watch_status, read_skill, cited_health, cited_stats, ….
- Is cited 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.9%· all time 98.9%
last good check
of 9 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- scan a local business's ai visibility
- re-fetch a scan report
- check monitoring status
- takes → gives
- text → data
- tools
- 9 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.
cited_health reads open 22h ago
Liveness check for the Cited API.
{ "type": "object", "title": "cited_healthArguments", "properties": {} }arguments 5 linescited_stats reads open 22h ago
Funnel counters: page views, scans run, paid registrations.
{ "type": "object", "title": "cited_statsArguments", "properties": {} }arguments 5 linesskills_list_tool reads open 22h ago
List this product's skills. Each entry carries the SKILL.md URI, its name and description, verbatim frontmatter, and a per-file sha256 manifest. Read a body with `read_skill`.
{ "type": "object", "title": "skills_list_toolArguments", "properties": {} }arguments 5 linescited_report reads unknown never probed
Re-fetch a previous scan result by its shareable scan_id.
{ "type": "object", "title": "cited_reportArguments", "required": [ "scan_id" ], "properties": { "scan_id": { "type": "string", "title": "Scan Id" } } }arguments 13 linescited_scan reads unknown never probed
Run a free instant AI-visibility scan for a local business. Args: business: the business's name, e.g. "Sunshine Smiles Dentistry" city: city + state, e.g. "Austin, TX" category: the service category, default "dentist" Returns per-engine verdicts, verbatim AI evidence quotes, citations, and a `cta_teaser` on any check where the business wasn't the top recommendation — the specific fix is a paid-tier ($39/mo) feature. Rate limit: 3/IP/24h. Scan takes under 30s (single-prompt free-tier path).
{ "type": "object", "title": "cited_scanArguments", "required": [ "business", "city" ], "properties": { "city": { "type": "string", "title": "City" }, "business": { "type": "string", "title": "Business" }, "category": { "type": "string", "title": "Category", "default": "dentist" } } }arguments 23 linescited_api_docs reads unknown never probed
Self-serve documentation for Cited — quickstart, MCP tools, REST endpoints, error shapes, and agent-operator policies, as markdown. Args: topic: "quickstart" | "mcp" | "rest" | "errors" | "policies" | "all" (default "" == "all"). Unknown topics fall back to full docs.
{ "type": "object", "title": "cited_api_docsArguments", "properties": { "topic": { "type": "string", "title": "Topic", "default": "" } } }arguments 11 linescited_examples reads unknown never probed
Complete, runnable recipe for a common Cited integration pattern. Args: pattern: "python_scan" (REST scan + verdict parsing) | "agent_watch" (MCP client connect + prompt)
{ "type": "object", "title": "cited_examplesArguments", "properties": { "pattern": { "type": "string", "title": "Pattern", "default": "python_scan" } } }arguments 11 linescited_watch_status reads unknown 12h ago
Check whether a business is on the paid weekly monitoring plan.
{ "type": "object", "title": "cited_watch_statusArguments", "required": [ "business" ], "properties": { "business": { "type": "string", "title": "Business" } } }arguments 13 linesread_skill reads unknown 12h ago
Read a product skill file by its skill:// URI. Args: uri: e.g. skill://<product>/<skill-name>/SKILL.md Get valid URIs from `skills_list_tool`.
{ "type": "object", "title": "read_skillArguments", "required": [ "uri" ], "properties": { "uri": { "type": "string", "title": "Uri" } } }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 idb9fca0806cf3c379.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/b9fca0806cf3c379/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/b9fca0806cf3c379?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.