Skip to main content
Glama

Server Details

Check whether AI assistants can reach, read and cite a public website. No account for 4 of 5 tools.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct aspect of AI-readiness auditing: scan gives an overall score, check_files verifies specific file serving, crawler_access tests crawler user-agent responses, fix_prompt generates remediation tasks, and agent_commerce reads a stored agent-commerce audit. Although scan overlaps slightly with check_files and crawler_access, the descriptions clearly separate initial vs. verification use cases.

Naming Consistency4/5

All names share the citefiles_ prefix and snake_case style, but the trailing components mix verbs (scan, check_files, fix_prompt) and nouns (agent_commerce, crawler_access). This is a minor inconsistency, though still readable and predictable in casing.

Tool Count5/5

5 tools is well-scoped for an AI-visibility auditing server. Each tool covers a distinct phase (scan, verify, test, plan, read audit) without redundancy.

Completeness4/5

Core audit workflow is covered, but there is a minor gap: the agent-commerce audit can only be read, not initiated via MCP (must run on the web report page first), and there is no tool to list past scans. This is a small dead end agents must work around.

Available Tools

5 tools
citefiles_agent_commerceAInspect

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.

Inputs: scan (required).

citefiles_check_filesAInspect

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.

Inputs: url (required).

citefiles_crawler_accessAInspect

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.

Inputs: url (required).

citefiles_fix_promptAInspect

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.

Inputs: url (required), style.

citefiles_scanAInspect

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.

Inputs: url (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Checks a site for AI crawlers: which of 11 AI crawlers its robots.txt lets in, whether its llms.txt follows llmstxt.org, and what its home page says without scripts. Findings with evidence; no scores, no model calls, no telemetry.
      5
      52 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Checks whether a website is readable and citable by AI search engines — llms.txt, Schema.org structured data, AI-bot access in robots.txt, content freshness, answer directness, E-E-A-T signals, plus a LocalBusiness Rich Results validator. Free, no API key, remote Streamable HTTP.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables checking whether a page or domain can be found and cited by AI assistants and search engines, covering page-level fixes, AI-crawler access via robots.txt, llms.txt validity, and backlink strength. It is free, read-only, and requires no account.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources