Xither — AI vendor record
Server Details
Read-only record of AI vendor sub-processor lists, DPA notice windows and model retirements
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: vendor search, single-vendor record lookup, cross-vendor notice-window comparison, and cross-vendor model retirement lookup. The descriptions explicitly cross-reference each other to steer agents away from overlapping uses, such as partial-name searches or cross-vendor comparisons.
All names use snake_case and are readable, but they do not follow one consistent pattern: lookup_vendor and search_vendors are verb_noun, while notice_windows and upcoming_model_retirements are descriptive noun phrases. This is mixed convention rather than a predictable verb_noun pattern.
Four tools is well-scoped for a read-only vendor intelligence record. Each tool covers a distinct access pattern: search, single-vendor lookup, notice-window comparison, and retirement-date lookup.
The core lifecycle is covered: find vendors, inspect one vendor's record, compare notice windows, and review upcoming retirements. Minor gaps remain, such as no obvious way to enumerate all vendors or view changes across vendors, but most workflows have a workable path.
Available Tools
4 toolslookup_vendorLook up one vendor's recordARead-onlyIdempotentInspect
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.
Inputs: vendor (required).
notice_windowsSub-processor notice windowsARead-onlyIdempotentInspect
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.
Inputs: no named parameters.
search_vendorsFind vendors by nameARead-onlyIdempotentInspect
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.
Inputs: query (required).
upcoming_model_retirementsUpcoming model retirementsARead-onlyIdempotentInspect
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.
Inputs: vendor, within_days.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Run deterministic SaaS contract redlining, GDPR Art. 28 DPA & EU AI Act compliance audits.
Run deterministic SaaS contract redlining, GDPR Art. 28 DPA & EU AI Act compliance audits.
Check a vendor before you sign: DPA coverage, subprocessors, certifications, data locations, AI use.
Read-only MCP: free OpenAI security evidence ledger (55 fields) + SaaSDossier release register.
Related MCP Servers
- AlicenseBqualityDmaintenanceTracks AI regulations, deadlines, risk assessments, and policy updates across multiple global jurisdictions, helping users stay compliant with evolving AI laws.69 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables querying a source-cited index of AI vendors' data practices—training on inputs, retention, and opt-out options—with tools to get a cited verdict for one vendor or compare a field across all 11 products.-
- AlicenseNot gradedqualityBmaintenanceRead-only lookups of open, cited AI law obligations for 17 regimes, including the EU AI Act, plus upcoming deadlines, a scope check, and tools that check or draft an AI_GOVERNANCE.md file. 8 tools over stdio, no AI model inside. Draft, dated data; not legal advice.2Apache 2.0
- AlicenseAqualityCmaintenanceSource-verified regulatory and compliance intelligence: 10,000+ obligations across 39 pillars, each grounded in a primary legal source with a content hash. Covers the EU AI Act, GDPR, DORA, NIS2, HIPAA, Basel III and the MITRE ATT&CK/ATLAS families.251MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.