Categories › Web & Browser › Web search engines & search APIs
Check whether AI assistants can reach, read and cite a public website. No account for 4 of 5 tools.
Remote server: your requests and data go to citefiles.com. Claude Code: claude mcp add --transport http cite-files https://citefiles.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
citefiles_scan — Check whether AI assistants can reach, read and cite a public website. Returns a citation-readiness score out of 100, the category breakdowncitefiles_fix_prompt — 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 evcitefiles_check_files — Check which AI-facing discovery files a website actually serves: llms.txt, llms-full.txt, ai.txt, robots.txt, sitemap.xml, AGENTS.md, .well-citefiles_crawler_access — Test how a website answers requests that carry the user-agent strings of four AI crawlers — GPTBot, OAI-SearchBot, ClaudeBot and PerplexityBcitefiles_agent_commerce — Requires an API token (Authorization: Bearer cf_…). Read the stored Agent Commerce Readiness audit for a scan on your citefiles account: wheNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.