Findings on what compounds and supplements do in the body, with evidence strength, quote and paper.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 699 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Other
Read-only record of AI vendor sub-processor lists, DPA notice windows and model retirements
1 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 3 | 1 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using Xither — AI vendor record
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http xither-ai-vendor-record https://www.xither.com/mcpCapabilities
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.
DiscoveredEvery 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.
DiscoveredFind 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.
DiscoveredModel 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.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 532 ms | 4 |