MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Other

Cite Files

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

Checks passed
12 / 22

2 failed · 8 not measured

Median response
352 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
5

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
310
Publisher identityCan the publisher be traced to its source?
312

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 352 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name citefiles.

  • Pass
    Lists tools

    tools/list returned 5 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 352 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 352 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    6 of 6 parameters have a description (100%). The bar is 80%.

  • Fail
    Safety hints

    5 tools set neither readOnlyHint nor destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Fail
    Source repo linked

    No repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-10-04T10:30:41.932564Z, within 180 days.

  • Not measured
    Open-source licence

    No GitHub repository to ask about a licence.

Start using Cite Files

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

claude mcp add --transport http cite-files https://citefiles.com/mcp

Capabilities

Tools 5

citefiles_agent_commerce

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.

Discovered
citefiles_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-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.

Discovered
citefiles_crawler_access

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.

Discovered
citefiles_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 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.

Discovered
citefiles_scan

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.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected352 ms5