Chaiz MCP

Live vehicle warranty (service contract) quotes by VIN, plate, or make/model/year.

Should I use this

Quality & Safety

A
Description quality
97%
Schema completeness
88%
Naming quality
97%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~1,382Tokens (tool definitions)
~1.7 KBTypical response size
Moderate attention impact (1.08% 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": {
    "mcp": {
      "url": "https://mcp.chaiz.com/mcp"
    }
  }
}

Remote endpoints

https://mcp.chaiz.com/mcpstreamable-http

What it can do

Tool inventory

Tools (6)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢list_vehicle_models(makeId)

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

Input Schema

{
  "type": "object",
  "properties": {
    "makeId": {
      "description": "The Chaiz make id returned by list_vehicle_makes.",
      "type": "integer"
    }
  },
  "required": [
    "makeId"
  ],
  "additionalProperties": false
}
🟢search_plans_by_vehicle(make, model, year, mileage, state, ...)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "make": {
      "description": "Vehicle manufacturer, e.g. \"Toyota\". Ask the user if unknown.",
      "type": "string"
    },
    "model": {
      "description": "Vehicle model, e.g. \"Tundra\". Ask the user if unknown.",
      "type": "string"
    },
    "year": {
      "description": "Model year, 1999-2030. Ask the user; never guess.",
      "type": "integer"
    },
    "mileage": {
      "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.",
      "type": "integer"
    },
    "state": {
      "description": "Two-letter US state code where the vehicle is registered, e.g. \"TX\". Ask the user; never guess.",
      "type": "string"
    },
    "zip": {
      "description": "Optional 5-digit US ZIP code for more precise pricing.",
      "type": [
        "string",
        "null"
      ],
      "default": null
    },
    "sort": {
      "description": "Optional ordering of results: \"rating\" (Chaiz expert rating, the default), \"recommended\", \"price_low\", or \"price_high\". Omit to use the default ordering.",
      "type": [
        "string",
        "null"
      ],
      "default": null
    }
  },
  "required": [
    "make",
    "model",
    "year",
    "mileage",
    "state"
  ],
  "additionalProperties": false
}
🟢lookup_vehicle(make, model, year)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "make": {
      "description": "Vehicle make to match, e.g. \"toyota\". Spelling does not need to be exact.",
      "type": "string"
    },
    "model": {
      "description": "Optional vehicle model to narrow the match.",
      "type": [
        "string",
        "null"
      ],
      "default": null
    },
    "year": {
      "description": "Optional model year to narrow the match.",
      "type": [
        "integer",
        "null"
      ],
      "default": null
    }
  },
  "required": [
    "make"
  ],
  "additionalProperties": false
}
🟢list_vehicle_makes

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

Input Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢search_plans_by_license_plate(licensePlate, state, mileage, zip, sort)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "licensePlate": {
      "description": "License plate number, 1-8 characters.",
      "type": "string"
    },
    "state": {
      "description": "Two-letter US state code where the plate is registered, e.g. \"TX\". Ask the user; never guess.",
      "type": "string"
    },
    "mileage": {
      "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.",
      "type": "integer"
    },
    "zip": {
      "description": "Optional 5-digit US ZIP code for more precise pricing.",
      "type": [
        "string",
        "null"
      ],
      "default": null
    },
    "sort": {
      "description": "Optional ordering of results: \"rating\" (Chaiz expert rating, the default), \"recommended\", \"price_low\", or \"price_high\". Omit to use the default ordering.",
      "type": [
        "string",
        "null"
      ],
      "default": null
    }
  },
  "required": [
    "licensePlate",
    "state",
    "mileage"
  ],
  "additionalProperties": false
}
🟢search_plans_by_vin(vin, mileage, state, zip, sort)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "vin": {
      "description": "17-character Vehicle Identification Number. Ask the user to re-check if invalid; never guess.",
      "type": "string"
    },
    "mileage": {
      "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.",
      "type": "integer"
    },
    "state": {
      "description": "Two-letter US state code where the vehicle is registered, e.g. \"TX\". Ask the user; never guess.",
      "type": "string"
    },
    "zip": {
      "description": "Optional 5-digit US ZIP code for more precise pricing.",
      "type": [
        "string",
        "null"
      ],
      "default": null
    },
    "sort": {
      "description": "Optional ordering of results: \"rating\" (Chaiz expert rating, the default), \"recommended\", \"price_low\", or \"price_high\". Omit to use the default ordering.",
      "type": [
        "string",
        "null"
      ],
      "default": null
    }
  },
  "required": [
    "vin",
    "mileage",
    "state"
  ],
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded6 tools
verifiedversion not recorded6 tools
verifiedversion not recorded6 tools
verifiedversion not recorded6 tools
verifiedversion not recorded6 tools
verifiedversion not recorded6 tools