Cite Files
Check whether AI assistants can reach, read and cite a public website. No account for 4 of 5 tools.
我該用這個嗎
品質與安全性
發現項目(4)
- HIGH
- MEDIUM在 citefiles_fix_prompt 中
- MEDIUM在 citefiles_agent_commerce 中
- INFO在 citefiles_fix_prompt 中
根據工具定義與協定合規性的自動化分析。
上下文成本
這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。
安裝
一鍵安裝
將以下內容加入你的 `claude_desktop_config.json` 檔案:
{
"mcpServers": {
"citefiles": {
"url": "https://citefiles.com/mcp"
}
}
}遠端端點
https://citefiles.com/mcpstreamable-http它能做什麼
工具清單
工具(5)
🟡citefiles_scan(url)
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",
"properties": {
"url": {
"type": "string",
"description": "The public website address, e.g. example.com or https://example.com"
}
},
"required": [
"url"
]
}🟢citefiles_fix_prompt(url, style)
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",
"properties": {
"url": {
"type": "string",
"description": "The public website address."
},
"style": {
"type": "string",
"enum": [
"claude",
"codex"
],
"description": "Prose instruction (claude) or a task list with acceptance criteria (codex). Defaults to claude."
}
},
"required": [
"url"
]
}🟢citefiles_check_files(url)
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",
"properties": {
"url": {
"type": "string",
"description": "The public website address."
}
},
"required": [
"url"
]
}⚪citefiles_crawler_access(url)
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",
"properties": {
"url": {
"type": "string",
"description": "The public website address."
}
},
"required": [
"url"
]
}🟡citefiles_agent_commerce(scan)
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",
"properties": {
"scan": {
"type": "string",
"description": "The scan's public id, from a citefiles.com/report/<id> URL."
}
},
"required": [
"scan"
]
}社群
證據