Xither — AI vendor record is an MCP server published by com.xither, hosted at www.xither.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 4 tools, including lookup_vendor, search_vendors, notice_windows, upcoming_model_retirements.
Read-only record of AI vendor sub-processor lists, DPA notice windows and model retirements
667 connections through 4 shared values. Tap any node.
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.
| Parameter | Type | Description |
|---|---|---|
| vendor * | string | A vendor name, slug or domain, for example "HubSpot", "hubspot" or "hubspot.com". |
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
{
"name": "lookup_vendor",
"title": "Look up one vendor's record",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"vendor"
],
"properties": {
"vendor": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "A vendor name, slug or domain, for example \"HubSpot\", \"hubspot\" or \"hubspot.com\"."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Look up one vendor's record",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| query * | string | Part of a vendor name, a slug or a domain. |
{
"name": "search_vendors",
"title": "Find vendors by name",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"maxLength": 100,
"minLength": 2,
"description": "Part of a vendor name, a slug or a domain."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Find vendors by name",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
No parameters.
{
"name": "notice_windows",
"title": "Sub-processor notice windows",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"title": "Sub-processor notice windows",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| vendor | string | Optional vendor name, slug or domain. |
| within_days | integer | How many days ahead to look, from today. |
{
"name": "upcoming_model_retirements",
"title": "Upcoming model retirements",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"vendor": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Optional vendor name, slug or domain."
},
"within_days": {
"type": "integer",
"default": 90,
"maximum": 365,
"minimum": 1,
"description": "How many days ahead to look, from today."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Upcoming model retirements",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Xither keeps dated, hashed copies of the pages AI and SaaS vendors publish: sub-processor lists, data processing agreements, trust pages and deprecation schedules. Every fact these tools return is a stored reading with its source URL and the date Xither read it; cite both when you repeat it. Xither reports what a page says, not what it means. Use search_vendors when unsure of a vendor's slug, then lookup_vendor for one vendor.
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.