# Cite Files (remote · citefiles.com)

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

- Trust score: 82/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `citefiles.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/com-citefiles-citefiles/citefiles.md), [page](https://verifymcp.io/servers/com-citefiles-citefiles/citefiles)

## Channel facts

- Endpoint: `https://citefiles.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 716 tokens (~143/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Cite Files MCP server?

Cite Files is a hosted endpoint at https://citefiles.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-citefiles-citefiles 'https://citefiles.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-citefiles-citefiles": {
      "url": "https://citefiles.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-citefiles-citefiles": {
      "type": "http",
      "url": "https://citefiles.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-citefiles-citefiles]
url = "https://citefiles.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-citefiles-citefiles": {
      "type": "remote",
      "url": "https://citefiles.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-citefiles-citefiles --url 'https://citefiles.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-citefiles-citefiles:
    url: "https://citefiles.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-citefiles-citefiles": {
      "Transport": "http",
      "Url": "https://citefiles.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-citefiles-citefiles -t streamable-http -u 'https://citefiles.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-citefiles-citefiles": {
      "type": "http",
      "url": "https://citefiles.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 82, 0)

- [security] Stability: 0.97 → pass

### 2026-11-04 (score 82, 0)

- [functional] Stability: pass → 0.97

### 2026-11-03 (score 82, 0)

- [security] Stability: 0.97 → pass

### 2026-11-02 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `citefiles_scan` (~121 tokens)

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.

Input parameters:

- `url` (string, required): The public website address, e.g. example.com or https://example.com

### `citefiles_fix_prompt` (~123 tokens)

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.

Input parameters:

- `style` (string): Prose instruction (claude) or a task list with acceptance criteria (codex). Defaults to claude.
- `url` (string, required): The public website address.

### `citefiles_check_files` (~111 tokens)

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.

Input parameters:

- `url` (string, required): The public website address.

### `citefiles_crawler_access` (~125 tokens)

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.

Input parameters:

- `url` (string, required): The public website address.

### `citefiles_agent_commerce` (~150 tokens)

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.

Input parameters:

- `scan` (string, required): The scan's public id, from a citefiles.com/report/<id> URL.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-citefiles-citefiles/citefiles#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 80
- 2026-10-29: 80
- 2026-10-28: 79
- 2026-10-27: 79
- 2026-10-26: 78
- 2026-10-25: 78
- 2026-10-24: 77
- 2026-10-23: 77
- 2026-10-22: 76
- 2026-10-21: 76
- 2026-10-20: 76
- 2026-10-19: 75
- 2026-10-18: 75
- 2026-10-17: 74
- 2026-10-16: 74
- 2026-10-15: 73
- 2026-10-14: 73
- 2026-10-13: 72
- 2026-10-12: 72
- 2026-10-10: 71
- 2026-10-09: 70
- 2026-10-07: 69
- 2026-10-06: 69
- 2026-10-04: 68

## Common questions

### What is the Cite Files MCP server?

Cite Files is an MCP server listed in the public MCP registry as com.citefiles/citefiles. Check whether AI assistants can reach, read and cite a public website. No account for 4 of 5 tools. This page covers its hosted endpoint (https://citefiles.com/mcp).

### Is the Cite Files MCP server safe to use?

Cite Files scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Cite Files MCP server expose?

Cite Files exposes 5 tools: citefiles_scan, citefiles_fix_prompt, citefiles_check_files, citefiles_crawler_access, citefiles_agent_commerce. Their descriptions and schemas cost roughly 630 tokens of context every time the server is loaded.

### Does the Cite Files MCP server require authentication?

No. We connected to Cite Files without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Cite Files MCP server still maintained?

Cite Files is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Cite Files MCP server?

VerifyMCP ran 12 checks on Cite Files, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Cite Files: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://citefiles.com/mcp
- Website: https://citefiles.com/integrations
- Changelog RSS feed: https://verifymcp.io/servers/com-citefiles-citefiles/citefiles.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-citefiles-citefiles/citefiles/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-citefiles-citefiles/citefiles.json
- HTML version of this page: https://verifymcp.io/servers/com-citefiles-citefiles/citefiles