_ registry / mcp streamable-http · checked 1h ago

xither

https://www.xither.com

Registry code: f055b63f030703e6

api record

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.

endpoint
https://www.xither.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
609ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 4 tools
2 open 2 never probed 2 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • notice_windows open 1h ago

    Every sub-processor notice window Xither can quote: the number of days (business days where the clause says so) each vendor's own terms give customers to object to a new sub-processor, 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.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • upcoming_model_retirements open 1h ago

    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.

    mcp-tool

    {
  "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
}
    arguments 19 lines
  • search_vendors unknown never probed

    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.

    mcp-tool

    {
  "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
}
    arguments 15 lines
  • lookup_vendor unknown 1h ago

    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.

    mcp-tool

    {
  "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
}
    arguments 15 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f055b63f030703e6/badge.svg)](https://brick.blue/agent/f055b63f030703e6)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.