citefiles
Registry code: b7b141db729587c8
Cite Files measures whether AI assistants can reach, read and cite a public website, and tells you exactly what to change. Free, no account needed for these tools. Typical use: citefiles_scan to measure, citefiles_fix_prompt to plan the work, then citefiles_scan again to verify — do not claim a site improved without re-running it. Full docs at https://citefiles.com/llms.txt
- endpoint
- https://citefiles.com/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
90 days 100%· all time 100%
last good check
of 5 tools
- unknown → live
The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.
distinct, expensive to fake
successful, last 30 days
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.
citefiles_scan unknown never probed
Check whether AI assistants can reach, read and cite a public website. Returns a citation-readiness score out of 100, the category breakdown, and the specific problems found — crawler blocks, missing llms.txt/ai.txt/sitemap, thin or JavaScript-only content, missing structured data. Use this before changing a site for AI visibility, and again afterwards to check the change worked. Scans of the same site within six hours are reused.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "The public website address, e.g. example.com or https://example.com" } } }arguments 12 linescitefiles_fix_prompt unknown never probed
Get a task list for making a website readable and citable by AI assistants, derived from a real scan of it. Returns the findings with the evidence behind each, and the rules to follow while fixing them — most importantly that you must not invent facts about the business, and must leave a visible TODO instead. Use this to plan the work after citefiles_scan.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "The public website address." }, "style": { "enum": [ "claude", "codex" ], "type": "string", "description": "Prose instruction (claude) or a task list with acceptance criteria (codex). Defaults to claude." } } }arguments 20 linescitefiles_check_files unknown never probed
Check which AI-facing discovery files a website actually serves: llms.txt, llms-full.txt, ai.txt, robots.txt, sitemap.xml, AGENTS.md, .well-known/mcp.json and others. Distinguishes a real file from a single-page app returning its HTML shell for every unknown path, which is the usual reason a file appears to exist but does not. Use this to verify a file you just published is being served correctly.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "The public website address." } } }arguments 12 linescitefiles_agent_commerce unknown never probed
Requires an API token (Authorization: Bearer cf_…). Read the stored Agent Commerce Readiness audit for a scan on your citefiles account: whether an AI agent can authenticate without a human's password, discover an API, read prices as text, and be offered a machine-payable challenge — as a tier from T0 to T5. Create a token at https://citefiles.com/account. Only returns audits for scans your account owns. This tool never runs a new audit — run it from the scan's report page first, then call this tool to read the result.
{ "type": "object", "required": [ "scan" ], "properties": { "scan": { "type": "string", "description": "The scan's public id, from a citefiles.com/report/<id> URL." } } }arguments 12 linescitefiles_crawler_access unknown never probed
Test how a website answers requests that carry the user-agent strings of four AI crawlers — GPTBot, OAI-SearchBot, ClaudeBot and PerplexityBot — by requesting its homepage as a browser and again as each, then comparing. The requests come from our server, not the vendors' networks, so a rule that checks the sender's address is not tested. Catches CDN and WAF rules that block assistants without the owner knowing. Use when a site looks correct but is not being cited.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "The public website address." } } }arguments 12 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 idb7b141db729587c8.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/b7b141db729587c8/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/b7b141db729587c8?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.