
Cite Files MCP server
Which servers in the official MCP registry are Cite Files's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-24
- Registry namecom.citefiles/citefilesverified in the MCP registry
The registry name sits under citefiles.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-24
- Tools5
- Server calls itselfcitefiles
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 196 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 3 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
- Answeredmeasuring3 of the 7 daily checks it takes to print a share
- Median first answer802 ms
- Space in an agent's context≈ 837 tokensthe definitions of all its tools (5), which an agent carries on every turn
- Tool definitionsB · 83 of 100
- Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once
- Not saying whether it only reads or can destroy: 5 of 5
What an agent can do with it
- not sure · check whether AI crawlers receive the same homepage as browsers
- can do · audit robots.txt rules for AI crawler access
- not sure · generate llms.txt files from the site's own pages
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
citefiles_scanCheck 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…
citefiles_fix_promptGet 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…
citefiles_check_filesCheck 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…
citefiles_crawler_accessTest 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…
citefiles_agent_commerceRequires 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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"citefiles": {
"type": "http",
"url": "https://citefiles.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http citefiles https://citefiles.com/mcpclaude.ai, ChatGPT and other clients: add https://citefiles.com/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.