Xither — AI vendor record

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

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
80%
Naming quality
85%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~757Tokens (tool definitions)
~603 BTypical response size
Moderate attention impact (0.59% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

https://www.xither.com/mcpstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢lookup_vendor(vendor)

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 Schema

{
  "type": "object",
  "properties": {
    "vendor": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "A vendor name, slug or domain, for example \"HubSpot\", \"hubspot\" or \"hubspot.com\"."
    }
  },
  "required": [
    "vendor"
  ],
  "additionalProperties": false
}
🟢search_vendors(query)

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 Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 2,
      "maxLength": 100,
      "description": "Part of a vendor name, a slug or a domain."
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}
🟢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.

Input Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢upcoming_model_retirements(vendor, within_days)

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 Schema

{
  "type": "object",
  "properties": {
    "vendor": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Optional vendor name, slug or domain."
    },
    "within_days": {
      "type": "integer",
      "minimum": 1,
      "maximum": 365,
      "default": 90,
      "description": "How many days ahead to look, from today."
    }
  },
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools