mcpbeat Sign in

Xither — AI vendor record MCP Server

not responding

Xither — AI vendor record is listed as active in the registry but did not answer our last check. It exposes 4 tools.

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

Uptime history 39 days of history · worst day 0%
39 days agonow
1.1%
Uptime 24h
1 of 91 checks
4
Tools
read from the server
1060 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 1 November 2026. No other catalogue keeps this.

1 Nov a tool description was rewritten lookup_vendor

Xither — AI vendor record does not always answer

Over the last week it answered 2.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add record --transport http https://www.xither.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://www.xither.com/mcp
~/.codex/config.toml
[mcp_servers.record]
url = "https://www.xither.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "record": {
      "url": "https://www.xither.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "record": {
      "type": "http",
      "url": "https://www.xither.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

lookup
lookup_vendor
The 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.
notice
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
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.
vendors
search_vendors
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.

Endpoints

URLTransportStateLatencyChecked
https://www.xither.com/mcp streamable-http answering 111 ms 13 min ago

Alternatives to Xither — AI vendor record

same job, measured the same way
Minutes of AI
by minutesofai

Read-only AI news with sources, Model Tracker prices, releases and retirement dates.

20 tools answering
W
Weather of Record
by weatherofrecord

Published weather records for a U.S. address and date, with provenance, and current NWS forecasts.

4 tools answering
TenderDelta
by netlify-tenderdelta

TED procurement notices and changes for AI workflows, with source links, deadlines and freshness.

answering
modelright
by modelright

Live registry of AI model specs, context windows, and per-token pricing.

6 tools answering
Marketplace Ad Pros: Amazon Ads & Seller Central
by marketplaceadpros

Amazon Ads, Seller Central, Vendor Central and AMC data for AI agents. Read-only by default.

answering
Nooscape MCP
by runtimeadmin

Read-only facts with dates about AI agents, wallets and endpoints from Nooscape's public record.

421 installs/wk local only
I
Isitdeprecated
by isitdeprecated

Check if an AI model is deprecated, retiring, or silently changed price or context window.

4 tools answering
Most Recommended Books
by mostrecommendedbooks

Read-only MCP server for verified book recommendations and reading lists.

6 tools answering

Xither — AI vendor record — questions

Answers built from our own checks of this server.

What can Xither — AI vendor record do?
It exposes 4 tools, read directly from the server on our last check. Among them: lookup_vendor, notice_windows, search_vendors, upcoming_model_retirements. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Xither — AI vendor record working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 1 of 91 checks got a reply (1.1%), average response time 1060 ms. The bar chart above shows every period we have measured.
The registry lists Xither — AI vendor record as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Xither — AI vendor record?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Xither — AI vendor record need an API key?
No. Xither — AI vendor record completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Xither — AI vendor record?
It answers our handshake in 1060 ms on average, which is faster than 3% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.