Cited
REMOTE · CITED-API-PRODUCTION.UP.RAILWAY.APP
AI-answer-engine visibility scans for local businesses, as agent tools
Available components
Last scanned (9 hours ago)
Scores higher than 69% of remote servers
Unreachable for 1 day in a row. Last reached 4 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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 15 Oct 26 0
- Stability: 0.97 → pass security
- 14 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.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 70 to 83. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 70. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 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
- 25 Sept 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
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 5 Nov 2026 · Probed https://cited-api-production.up.railway.app/mcp/
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of cited-api-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cited-api-production.up.railway.app/mcp/ | Unreachable | ||
| http (plaintext) | http://cited-api-production.up.railway.app/mcp/ | HTTPS enforced |
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 →
cited_api_docs ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | – |
No output schema declared.
No examples provided.
cited_examples ~57
Complete, runnable recipe for a common Cited integration pattern. Args: pattern: "python_scan" (REST scan + verdict parsing) | "agent_watch" (MCP client connect + prompt)
| Name | Type | Req | Description |
|---|---|---|---|
| pattern | string | – | – |
No output schema declared.
No examples provided.
cited_health ~17
Liveness check for the Cited API.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cited_report ~29
Re-fetch a previous scan result by its shareable scan_id.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_id | string | yes | – |
No output schema declared.
No examples provided.
cited_scan ~160
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).
| Name | Type | Req | Description |
|---|---|---|---|
| business | string | yes | – |
| category | string | – | – |
| city | string | yes | – |
No output schema declared.
No examples provided.
cited_stats ~20
Funnel counters: page views, scans run, paid registrations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cited_watch_status ~28
Check whether a business is on the paid weekly monitoring plan.
| Name | Type | Req | Description |
|---|---|---|---|
| business | string | yes | – |
No output schema declared.
No examples provided.
read_skill ~57
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| uri | string | yes | – |
No output schema declared.
No examples provided.
skills_list_tool ~51
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`.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Cited MCP server?
Cited is a hosted endpoint at https://cited-api-production.up.railway.app/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 · cited-api-production.up.railway.app
claude mcp add --transport http entradox-cited-visibility-scanner 'https://cited-api-production.up.railway.app/mcp/'
What is the Cited MCP server?
Cited is an MCP server listed in the public MCP registry as io.github.entradox/cited-visibility-scanner. AI-answer-engine visibility scans for local businesses, as agent tools. This page covers its hosted endpoint (https://cited-api-production.up.railway.app/mcp/).
Is the Cited MCP server safe to use?
Cited 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 Cited MCP server expose?
Cited exposes 9 tools: cited_health, cited_scan, cited_report, cited_watch_status, cited_stats, and 4 more. Their descriptions and schemas cost roughly 513 tokens of context every time the server is loaded.
Does the Cited MCP server require authentication?
Its publisher declares no required credentials for Cited. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Cited MCP server still maintained?
Cited is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.