Xither — AI vendor record
com.xither/recordVersion 1.0.0Read-only record of AI vendor sub-processor lists, DPA notice windows and model retirements
Status
Responds1005 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:23 UTC
- Latency
- 1005 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://www.xither.com/mcpResponds1005 msNo sign-in
Claude Code
claude mcp add --transport http record https://www.xither.com/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: record
Remote MCP server URL: https://www.xither.com/mcpCursor
{
"mcpServers": {
"record": {
"url": "https://www.xither.com/mcp"
}
}
}VS Code
code --add-mcp '{"name":"record","type":"http","url":"https://www.xither.com/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
4 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
lookup_vendorThe Xither record for one vendor. Use it when the user names a specific vendor and asks where it publishes its sub-processor list or DPA, how long its terms give to object to a new sub-processor, what it has changed, or when its models retire. Returns: 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. If the name matches several vendors it returns their slugs to call again with; if it matches none, the vendor is not in the record, which says nothing about what the vendor publishes. Use search_vendors instead when you only have part of a name, notice_windows to compare windows across vendors, and upcoming_model_retirements for retirements across vendors. Changes appear 30 days after Xither records them; subscribers get them the same morning at www.xither.com/pricing. | No | Yes | Yes | No |
notice_windowsEvery 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. | No | Yes | Yes | No |
search_vendorsFind 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. | No | Yes | Yes | No |
upcoming_model_retirementsModel 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. | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Sep 30, 2026
- Updated
- Sep 30, 2026
- Repository
- Not given
- Categories
- Uncategorized
- GDPR
- Not declared