_ registry / mcp http-sse · checked 5h ago

Chaiz

https://mcp.chaiz.com

Registry code: eafe49aab6f3eb41

api record

Search live vehicle service contract (extended warranty) quotes from Chaiz by VIN, license plate, or make/model/year — plus the vehicle's mileage and US state. These tools are read-only: they return plan prices, coverage details, ratings, and chaiz.com links to view a plan or continue to checkout; they never place an order. Ask the user for any missing required field (such as mileage or state) rather than guessing. When mileage is missing, ask for the vehicle's exact current odometer reading as a single whole number (for example 78000), not a range or approximation. Presenting results: show…

endpoint
https://mcp.chaiz.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Chaiz live?
Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.
Is Chaiz free to use?
Yes — the hub reached it with no key and no payment.
What tools does Chaiz have?
6 tools: lookup_vehicle, search_plans_by_vin, search_plans_by_license_plate, search_plans_by_vehicle, list_vehicle_models, list_vehicle_makes.
Is Chaiz safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.5%

90 days 99.3%· all time 99.3%

latency
868ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 668 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
topic
iot & hardware vehicles & automotive
used for
  • get extended warranty quotes for a vehicle
  • search vehicle service contracts by vin or license plate
  • look up supported vehicle makes and models
takes → gives
text → data
tools
6 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
1 open 5 never probed 1 of 6 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.

  • list_vehicle_makes reads open 5h ago

    List the vehicle makes (manufacturers) Chaiz supports. Use this to map a user's make to its id before listing models.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • lookup_vehicle reads unknown 22h ago

    Fuzzy-match a vehicle by make (and optional model/year) to confirm it exists and correct spelling before a plan search. Use this when the user's make/model looks misspelled or uncertain.

    mcp-tool

    {
  "type": "object",
  "required": [
    "make"
  ],
  "properties": {
    "make": {
      "type": "string",
      "description": "Vehicle make to match, e.g. \"toyota\". Spelling does not need to be exact."
    },
    "year": {
      "type": [
        "integer",
        "null"
      ],
      "default": null,
      "description": "Optional model year to narrow the match."
    },
    "model": {
      "type": [
        "string",
        "null"
      ],
      "default": null,
      "description": "Optional vehicle model to narrow the match."
    }
  },
  "additionalProperties": false
}
    arguments 29 lines
  • search_plans_by_vin reads unknown 22h ago

    Search Chaiz for vehicle service contract plans by VIN. The VIN is decoded to the vehicle automatically. Results are 36-month (3-year) term plans. VIN, mileage, and state are required. If mileage or state is missing, ASK the user — never guess.

    mcp-tool

    {
  "type": "object",
  "required": [
    "vin",
    "mileage",
    "state"
  ],
  "properties": {
    "vin": {
      "type": "string",
      "description": "17-character Vehicle Identification Number. Ask the user to re-check if invalid; never guess."
    },
    "zip": {
      "type": [
        "string",
        "null"
      ],
      "default": null,
      "description": "Optional 5-digit US ZIP code for more precise pricing."
    },
    "sort": {
      "type": [
        "string",
        "null"
      ],
      "default": null,
      "description": "Optional ordering of results: \"rating\" (Chaiz expert rating, the default), \"recommended\", \"price_low\", or \"price_high\". Omit to use the default ordering."
    },
    "state": {
      "type": "string",
      "description": "Two-letter US state code where the vehicle is registered, e.g. \"TX\". Ask the user; never guess."
    },
    "mileage": {
      "type": "integer",
      "description": "The vehicle's exact current odometer reading in miles as a single whole number, 1-250000, e.g. 78000 — not a range or approximation. Ask the user; never guess."
    }
  },
  "additionalProperties": false
}
    arguments 39 lines
  • search_plans_by_license_plate reads unknown 5h ago

    Search Chaiz for vehicle service contract plans by US license plate. The plate plus state is used to identify the vehicle. Results are 36-month (3-year) term plans. License plate, state, and mileage are required. If mileage is missing, ASK the user — never guess.

    mcp-tool

    {
  "type": "object",
  "required": [
    "licensePlate",
    "state",
    "mileage"
  ],
  "properties": {
    "zip": {
      "type": [
        "string",
        "null"
      ],
      "default": null,
      "description": "Optional 5-digit US ZIP code for more precise pricing."
    },
    "sort": {
      "type": [
        "string",
        "null"
      ],
      "default": null,
      "description": "Optional ordering of results: \"rating\" (Chaiz expert rating, the default), \"recommended\", \"price_low\", or \"price_high\". Omit to use the default ordering."
    },
    "state": {
      "type": "string",
      "description": "Two-letter US state code where the plate is registered, e.g. \"TX\". Ask the user; never guess."
    },
    "mileage": {
      "type": "integer",
      "description": "The vehicle's exact current odometer reading in miles as a single whole number, 1-250000, e.g. 78000 — not a range or approximation. Ask the user; never guess."
    },
    "licensePlate": {
      "type": "string",
      "description": "License plate number, 1-8 characters."
    }
  },
  "additionalProperties": false
}
    arguments 39 lines
  • search_plans_by_vehicle reads unknown 5h ago

    Search Chaiz for vehicle service contract (extended warranty) plans by make, model, and year. Results are 36-month (3-year) term plans. Returns plan cards with monthly and total price, coverage term, coverage level, rating, and links to chaiz.com. All of make, model, year, mileage, and state are required. If any are missing, ASK the user for them — never guess the mileage or state.

    mcp-tool

    {
  "type": "object",
  "required": [
    "make",
    "model",
    "year",
    "mileage",
    "state"
  ],
  "properties": {
    "zip": {
      "type": [
        "string",
        "null"
      ],
      "default": null,
      "description": "Optional 5-digit US ZIP code for more precise pricing."
    },
    "make": {
      "type": "string",
      "description": "Vehicle manufacturer, e.g. \"Toyota\". Ask the user if unknown."
    },
    "sort": {
      "type": [
        "string",
        "null"
      ],
      "default": null,
      "description": "Optional ordering of results: \"rating\" (Chaiz expert rating, the default), \"recommended\", \"price_low\", or \"price_high\". Omit to use the default ordering."
    },
    "year": {
      "type": "integer",
      "description": "Model year, 1999-2030. Ask the user; never guess."
    },
    "model": {
      "type": "string",
      "description": "Vehicle model, e.g. \"Tundra\". Ask the user if unknown."
    },
    "state": {
      "type": "string",
      "description": "Two-letter US state code where the vehicle is registered, e.g. \"TX\". Ask the user; never guess."
    },
    "mileage": {
      "type": "integer",
      "description": "The vehicle's exact current odometer reading in miles as a single whole number, 1-250000, e.g. 78000 — not a range or approximation. Ask the user; never guess."
    }
  },
  "additionalProperties": false
}
    arguments 49 lines
  • list_vehicle_models reads unknown 22h ago

    List the models (and the years available) for a given Chaiz make id. Get the make id from list_vehicle_makes.

    mcp-tool

    {
  "type": "object",
  "required": [
    "makeId"
  ],
  "properties": {
    "makeId": {
      "type": "integer",
      "description": "The Chaiz make id returned by list_vehicle_makes."
    }
  },
  "additionalProperties": false
}
    arguments 13 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.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id eafe49aab6f3eb41.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/eafe49aab6f3eb41/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/eafe49aab6f3eb41/badge.svg)](https://brick.blue/agent/eafe49aab6f3eb41?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

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.