Free MCP server
Ask your AI assistant what your vendors’ pages say.
Xither runs a Model Context Protocol (MCP) server. Add it to Claude, ChatGPT, Cursor or VS Code. No account, no key.
- You ask
Where does this vendor publish its sub-processor list?
- You ask
What notice window does its data processing agreement (DPA) state?
- You ask
Which models does it retire next?
Each answer comes from a dated copy of the vendor’s page, with the page’s address and the date Xither read it.
Endpoint
https://www.xither.com/mcp
- Read-only.
- Streamable HTTP.
- About 60 calls per 10 minutes.
- Tool calls, from one network address. Each server counts its own, so the limit is approximate.
- Your questions aren’t kept.
- What you ask is not written to our database. The rate limit counts calls per address in memory.
Four tools answer them.
lookup_vendorLook up one vendor's record
One vendor per call. Changes appear 30 days after Xither reads them.
search_vendorsFind vendors by name
Up to 10 names, slugs and record URLs.
notice_windowsSub-processor notice windows
Only windows Xither can quote from the vendor's own terms.
upcoming_model_retirementsUpcoming model retirements
90 days ahead by default, 365 at most; up to 50 rows.
lookup_vendor returns the same record as the vendor’s page on /vendors: the pages we watch with their read dates, the pages Xither can’t read and why, the quoted notice window, public changes with permalinks, and dated model retirements.
notice_windows is the notice windows table. Retirements come from the retirement tables vendors publish, as listed on model and API retirements.
Changes reach the server 30 days after Xither records them. Subscribers hear the morning we read a change that matters, with their deadlines and a drafted notice (pricing).
Add it to your assistant.
Claude (claude.ai and the desktop app)
Settings, then Connectors, then Add custom connector. Name it Xither, paste the endpoint URL, and leave the authentication fields empty.
On Team and Enterprise plans, an owner may need to add the connector for the organization first.
Claude Code
claude mcp add --transport http xither https://www.xither.com/mcp
Cursor
Add this to .cursor/mcp.json in a project, or to ~/.cursor/mcp.json for every project:
{
"mcpServers": {
"xither": { "url": "https://www.xither.com/mcp" }
}
}VS Code
Add this to .vscode/mcp.json. Or run MCP: Add Server from the Command Palette, choose HTTP, and paste the endpoint URL.
{
"servers": {
"xither": { "type": "http", "url": "https://www.xither.com/mcp" }
}
}ChatGPT
ChatGPT connects to remote MCP servers as custom connectors once developer mode is on in its settings.
The menu names have changed more than once, so look for connectors or apps under Settings. Create one with the endpoint URL and no authentication.
Other clients
Any client that speaks Streamable HTTP can use the endpoint URL directly.
A client that only launches local servers can reach it through a bridge:
npx mcp-remote https://www.xither.com/mcp
What you get back.
What the page says, with its date.
Every answer comes from a dated copy of the page: the vendor’s words, the URL of the page and the date Xither read it.
If a site refuses our reader, it says so.
A page that refused Xither’s reader is reported as refused, with the reason. Never as a page the vendor doesn’t publish.
If we don’t watch a vendor, it says so.
A vendor Xither doesn’t watch is reported as not in the record, with a link to the vendors it does watch.
How pages are read, fingerprinted and corrected: methodology.
Watch vendor pages
More for this job.
- DatasetWhere vendors publish their lists and DPAsThe page to read for each vendor's sub-processor list and DPA.Open it ›
- ExplainerThe AI Vendor Change LexiconThe window to object, silence as consent and more, with real clauses where we hold one.Open it ›
- GuideWhich vendor pages to watchTen kinds of vendor page, and which ones are worth watching.Open it ›
- DatasetWhat AI vendors have retiredEvery model and API retirement we've read, soonest first, with its source page.Open it ›