NestDaddy

Apibara Vehicle Auction Data

tech.apibara/vehicle-auction · v1.0.0

Read-only MCP for Copart and IAA/IAAI search, history, filters, locations, shipping, and usage.

Connect Remote server

Terminal
claude mcp add --transport http vehicle-auction https://apibara.tech/mcp --header "X-API-Key: <X_API_KEY>"
~/.cursor/mcp.json
{
  "mcpServers": {
    "vehicle-auction": {
      "url": "https://apibara.tech/mcp",
      "headers": {
        "X-API-Key": "<X_API_KEY>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "vehicle-auction": {
      "type": "http",
      "url": "https://apibara.tech/mcp",
      "headers": {
        "X-API-Key": "<X_API_KEY>"
      }
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://apibara.tech/mcp

Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.

Tools 8 found in our last check

  • search_auction_vehicles

    Use for broad inventory discovery, filtering and incremental synchronization across supported Copart and IAA / IAAI records. For one known VIN or lot use get_vehicle; for retained auction appearances use get_vehicle_history.

  • get_vehicle

    Use when the user already has a VIN, lot number or supported slug and needs the current normalized vehicle record. Request include history and/or vin_lots when the same tool call should also return retained sale history or other known auction lots for the same VIN.

  • get_vehicle_history

    Use for retained Copart + IAAI auction appearances for one supported vehicle. This is auction-specific history, not complete ownership, registration or accident history.

  • get_related_vehicles

    Use after identifying a specific vehicle to retrieve related supported auction records for comparison or discovery. Do not use as a substitute for a broad filtered inventory search.

  • get_vehicle_filters

    Use before building a dynamic search UI or validating source-backed filter choices. Returns current filter metadata; it does not search inventory itself.

  • list_auction_locations

    Use to resolve supported auction yards, branches or facilities and their location metadata. Use calculate_shipping when the user needs auction-to-port pricing instead.

  • calculate_shipping

    Use when the user asks for supported auction-to-port shipping pricing for a known vehicle. Supply either VIN or lot_number; optionally narrow the destination with port or port_id. Availability depends on auction location and route data.

  • get_api_usage

    Use to inspect request usage and current plan limits for the supplied X-API-Key. This is account/API-quota metadata, not vehicle data.

Headers

NameDescription
X-API-Key
Required, secret
Apibara API key.

Details

Endpointhttps://apibara.tech/mcp (Streamable HTTP)
First published18 Sep 2026
Last updated18 Sep 2026
Registry nametech.apibara/vehicle-auction

More search and web servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.