# Xither — AI vendor record (remote · www.xither.com)

Read-only record of AI vendor sub-processor lists, DPA notice windows and model retirements

- Trust score: 77/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-06

## Components

- remote · `www.xither.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-xither-record/www.md), [page](https://verifymcp.io/servers/com-xither-record/www)

## Channel facts

- Endpoint: `https://www.xither.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-10-06.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 572 tokens (~143/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Xither — AI vendor record MCP server?

Xither — AI vendor record is a hosted endpoint at https://www.xither.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-xither-record 'https://www.xither.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-xither-record": {
      "url": "https://www.xither.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-xither-record]
url = "https://www.xither.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-xither-record:
    url: "https://www.xither.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-xither-record": {
      "type": "http",
      "url": "https://www.xither.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-10-06 (score 77, +1)

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

### 2026-10-04 (score 76, +1)

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

### 2026-10-02 (score 75, +1)

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

### 2026-10-01 (score 74, 0)

- [security] Tool “notice_windows” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-09-30 (score 74)

First indexed and scored.

## MCP tools (4)

### `lookup_vendor` (~158 tokens)

Look up one vendor's record

The Xither record for one vendor: where it publishes its sub-processor list and data processing agreement and when Xither last read each page (or why a page cannot be read), the notice window its agreement states for new sub-processors (quoted, with source URL and read date), its public changes to either document with permalinks, and model retirement dates it publishes for the next 365 days. One vendor per call; accepts a name, slug or domain. Changes appear 30 days after Xither records them; subscribers get them the same morning at www.xither.com/pricing.

Input parameters:

- `vendor` (string, required): A vendor name, slug or domain, for example "HubSpot", "hubspot" or "hubspot.com".

### `search_vendors` (~73 tokens)

Find vendors by name

Find vendors in the Xither record by name, slug or domain. Returns up to 10 matches, each with its name, slug and record URL, and no record data. Pass a slug to lookup_vendor for the record.

Input parameters:

- `query` (string, required): Part of a vendor name, a slug or a domain.

### `notice_windows` (~127 tokens)

Sub-processor notice windows

Every sub-processor notice window Xither can quote: the number of days (business days where the clause says so) each vendor's own terms state for a new sub-processor, and what that number counts (basis: 'objection' = time to object once told, 'notice' = notice before the change, 'unstated' = the clause does not settle it), with the verbatim clause, its source URL and the date Xither read it. The same table as www.xither.com/notice-windows. A vendor not listed has no window Xither could quote.

### `upcoming_model_retirements` (~118 tokens)

Upcoming model retirements

Model and API retirement dates from the retirement tables vendors publish, as Xither last read them, soonest first: model, date, the replacement the vendor names, the verbatim table row, source URL and read date. Optional vendor filter; within_days defaults to 90, maximum 365; at most 50 rows. Covers only vendors whose retirement tables Xither reads.

Input parameters:

- `vendor` (string): Optional vendor name, slug or domain.
- `within_days` (integer): How many days ahead to look, from today.

## Diagnostics

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

## Score history

- 2026-10-06: 77
- 2026-10-04: 76
- 2026-10-03: 75
- 2026-10-02: 75
- 2026-10-01: 74
- 2026-09-30: 74

## Common questions

### What is the Xither — AI vendor record MCP server?

Xither — AI vendor record is an MCP server listed in the public MCP registry as com.xither/record. Read-only record of AI vendor sub-processor lists, DPA notice windows and model retirements. This page covers its hosted endpoint (https://www.xither.com/mcp).

### Is the Xither — AI vendor record MCP server safe to use?

Xither — AI vendor record scores 77 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 Xither — AI vendor record MCP server expose?

Xither — AI vendor record exposes 4 tools: lookup_vendor, search_vendors, notice_windows, upcoming_model_retirements. Their descriptions and schemas cost roughly 476 tokens of context every time the server is loaded.

### Does the Xither — AI vendor record MCP server require authentication?

No. We connected to Xither — AI vendor record without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Xither — AI vendor record MCP server still maintained?

Xither — AI vendor record is still listed as active in the MCP registry. We last reached this channel on 6 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.xither.com/mcp
- Website: https://www.xither.com/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/com-xither-record/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-xither-record/www.json
- HTML version of this page: https://verifymcp.io/servers/com-xither-record/www