Read-only access to Copart and IAA/IAAI vehicle auction search, history, filters, locations, and shipping data.
What you can do
This remote MCP server gives an assistant read-only tools for vehicle auction data from Copart and IAA/IAAI. It covers auction search, vehicle history, filters, locations, and shipping information, plus usage details. It is intended for looking up and comparing auction listings rather than managing accounts or placing bids.
When to use it
Use it when an assistant needs to look up vehicle auction listings, check a vehicle's auction history, filter results by criteria, or find auction locations and shipping information from Copart and IAA/IAAI. It suits research and comparison tasks, not bidding or account management.
Requirements
A remote streamable HTTP endpoint at reachable over the network. A required Apibara API key supplied in the X-API-Key header. No local runtime, package, or environment variables are declared.
Before you install
The server is read-only, so it does not bid, buy, or change auction records. It requires an API key sent in the X-API-Key header; treat that key as a secret and avoid exposing it in shared logs or client configurations. Auction data comes from third-party sources (Copart and IAA/IAAI), so queries and results are shared with the provider.
Connect X-API-Key credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/tech.apibara%2Fvehicle-auction/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Parametersszipmaketypecolormodelunitscursordamageradiusserieshas_key+37 more
get_vehicle
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.
Parametersincludeidentifierrequired
get_vehicle_history
Get vehicle auction history
Use for retained Copart + IAAI auction appearances for one supported vehicle. This is auction-specific history, not complete ownership, registration or accident history.
Parametersidentifierrequired
get_related_vehicles
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.
Parametersper_pageidentifierrequired
get_vehicle_filters
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.
Parametersplatform
list_auction_locations
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.
Parameterssstatecountryplatform
calculate_shipping
Calculate auction-to-port 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.
Parametersvinportport_idlot_number
get_api_usage
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.
Takes no parameters.
Version history
1
v1.0.0LatestSep 18, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.