Apibara Vehicle Auction Data
REMOTE · APIBARA.TECH
Read-only MCP for Copart and IAA/IAAI search, history, filters, locations, shipping, and usage.
Available components
Last scanned (20 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 4 Nov 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1637 tokens (~204/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Oct 26 0
- “search_auction_vehicles” added an optional parameter “auction_date_pending” cosmetic
- “search_auction_vehicles” reworded the description of “odometer_from” cosmetic
- “search_auction_vehicles” reworded the description of “odometer_to” cosmetic
- “search_auction_vehicles” reworded the description of “units” cosmetic
4 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 23 Oct 26 +1
- Stability: fail → pass ▲ security
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 89 to 92.
- 17 Oct 26 0
- “search_auction_vehicles” added an optional parameter “vin_prefix” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 79 to 82.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 72 to 76.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 66 to 72.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 56 to 66.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://apibara.tech/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=apibara.tech | CN=WE1,O=Google Trust Services,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 70f797195469589e0e611243230444f2 |
| SANs: apibara.tech, *.apibara.tech | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of apibara.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| apibara.tech. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://apibara.tech/mcp | Verified | 200 | |
| http (plaintext) | http://apibara.tech/mcp | HTTPS enforced | 301 | https://apibara.tech/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
calculate_shipping Calculate auction-to-port shipping ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lot_number | string | – | Auction lot number. Provide this or vin. |
| port | string | – | Optional destination port name supported by the shipping endpoint. |
| port_id | integer|string | – | Optional destination port identifier when known. |
| vin | string | – | Vehicle Identification Number. Provide this or lot_number. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | – |
No examples provided.
get_api_usage Get API usage ~38
Use to inspect request usage and current plan limits for the supplied X-API-Key. This is account/API-quota metadata, not vehicle data.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
No examples provided.
get_related_vehicles Get related vehicles ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | VIN, lot number or slug_vin accepted by the canonical vehicle detail endpoint. |
| per_page | integer | – | Maximum related records to return. Effective limits are plan-dependent. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | – |
| meta | object | – | Pagination metadata. Treat cursor values as opaque. |
No examples provided.
get_vehicle Get vehicle ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | VIN, lot number or slug_vin accepted by the canonical vehicle detail endpoint. |
| include | array | – | Optional related data to embed in the vehicle detail result. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
No examples provided.
get_vehicle_filters Get vehicle filters ~56
Use before building a dynamic search UI or validating source-backed filter choices. Returns current filter metadata; it does not search inventory itself.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | Optional readable auction-source selector. Omit to retrieve combined supported filter metadata. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
No examples provided.
get_vehicle_history Get vehicle auction history ~62
Use for retained Copart + IAAI auction appearances for one supported vehicle. This is auction-specific history, not complete ownership, registration or accident history.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | VIN, lot number or slug_vin accepted by the canonical vehicle detail endpoint. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | – |
| meta | object | – | Pagination metadata. Treat cursor values as opaque. |
No examples provided.
list_auction_locations List auction locations ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional country filter supported by the locations endpoint. |
| platform | string | – | Optional source selector: Copart or IAA / IAAI. |
| s | string | – | Free-text location search, such as a facility name, city or supported location term. |
| state | string | – | Optional state or region filter, for example FL. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | – |
| meta | object | – | Pagination metadata. Treat cursor values as opaque. |
No examples provided.
search_auction_vehicles Search auction vehicles ~1,056
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.
| Name | Type | Req | Description |
|---|---|---|---|
| auction_date_from | string | – | Start auction date in YYYY-MM-DD format. |
| auction_date_pending | boolean | – | Auction date pending filter for GET /vehicles. |
| auction_date_to | string | – | End auction date in YYYY-MM-DD format. |
| auction_type | integer | – | Numeric compatibility source selector: 0=all, 1=Copart, 2=IAAI. If both auction_type and platform are supplied, auction_type takes precedence; prefer platform for new integrations. |
| body_style | – | – | Filter by vehicle_specs.body_style. A string or array is accepted; multiple values are OR-ed. IAAI uses VehicleClass and Copart uses the source-backed Body Style field. |
| body_type | – | – | Deprecated compatibility alias for body_style. A string or array is accepted; prefer body_style for new integrations. |
| color | string | – | Color filter for GET /vehicles. |
| cursor | string | – | Opaque pagination cursor returned by the API. Send next_cursor back unchanged; do not decode or synthesize it. |
| cylinders | integer | – | Cylinders filter for GET /vehicles. |
| damage | string | – | Primary damage category filter. |
| drive_type | string | – | Drive type filter for GET /vehicles. |
| engine_size_from | number | – | Engine size from filter for GET /vehicles. |
| engine_size_to | number | – | Engine size to filter for GET /vehicles. |
| engine_type | string | – | Engine type filter for GET /vehicles. |
| facility_id | string | – | Auction facility identifier used to restrict results to one supported facility. |
| fuel_type | string | – | Fuel type filter for GET /vehicles. |
| generation | string | – | Generation filter for GET /vehicles. |
| generation_id | string | – | Generation ID filter for GET /vehicles. |
| has_key | string | – | Key-availability filter using the documented values No, All or With. |
| has_shipping_price | boolean | – | When true, return only vehicles with supported shipping-price data. |
| include_total | boolean | – | Include exact total filter for GET /vehicles. |
| loc_state | string | – | Auction location state or region, for example FL. |
| lot_status | string | – | Auction mode filter: All, Timed or Buy Now. |
| lot_sub_status | string | – | Normalized auction state: Open for active/open lots, Live for currently live supported lots, Ended for closed/ended lots. |
| make | string | – | Make filter for GET /vehicles. |
| model | string | – | Model filter for GET /vehicles. |
| odometer_from | number | – | Odometer from (miles) filter for GET /vehicles. |
| odometer_to | number | – | Odometer to (miles) filter for GET /vehicles. |
| office_name | string | – | Auction office or branch name filter. |
| per_page | integer | – | Requested page size. Effective maximum is subscription-plan dependent; common public plan limits are 20, 30 or 40 and custom plans may differ. |
| platform | string | – | Readable auction-source selector: copart or iaai. Omit for combined supported sources. |
| price_max | number | – | Price max filter for GET /vehicles. |
| price_min | number | – | Price min filter for GET /vehicles. |
| radius | integer | – | Search radius around zip, interpreted using the selected units. |
| run_cond | string | – | Normalized run-condition filter. |
| s | string | – | Search by VIN, lot number or vehicle title/model text. |
| sale_document_pending | boolean | – | When true, restrict results to records with a pending sale document state when supported. |
| sale_document_type | string | – | Sale/title document type filter; values are source-backed and can vary. |
| seller_type | string | – | Normalized seller type: dealer, finance, insurance or non_insurance. |
| series | string | – | Series / model family filter for GET /vehicles. |
| today_only | boolean | – | When true, restrict results to the endpoint current-day auction logic. |
| transmission | string | – | Transmission filter for GET /vehicles. |
| type | string | – | Vehicle type filter for GET /vehicles. |
| units | string | – | Geographic distance unit system: mi or km. Odometer filter boundaries are always miles. |
| upcoming | string | – | Upcoming selector: all=no upcoming restriction, only=upcoming eligible lots only, without=exclude upcoming lots. |
| updated_within_minutes | integer | – | Incremental-sync window. Return records whose updated_at changed within this many minutes; supported range is 1..525600. Use with cursor pagination and an overlap window. |
| vin_prefix | string | – | VIN prefix(es) filter for GET /vehicles. |
| year_from | integer | – | Year from filter for GET /vehicles. |
| year_to | integer | – | Year to filter for GET /vehicles. |
| zip | string | – | ZIP/postal code used with radius for supported proximity search. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | – | – |
| meta | object | – | Pagination metadata. Treat cursor values as opaque. |
No examples provided.
How do I install the Apibara Vehicle Auction Data MCP server?
Apibara Vehicle Auction Data is a hosted endpoint at https://apibara.tech/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · apibara.tech
claude mcp add --transport http tech-apibara-vehicle-auction 'https://apibara.tech/mcp'
What is the Apibara Vehicle Auction Data MCP server?
Apibara Vehicle Auction Data is an MCP server listed in the public MCP registry as tech.apibara/vehicle-auction. Read-only MCP for Copart and IAA/IAAI search, history, filters, locations, shipping, and usage. This page covers its hosted endpoint (https://apibara.tech/mcp).
Is the Apibara Vehicle Auction Data MCP server safe to use?
Apibara Vehicle Auction Data scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Apibara Vehicle Auction Data MCP server expose?
Apibara Vehicle Auction Data exposes 8 tools: search_auction_vehicles, get_vehicle, get_vehicle_history, get_related_vehicles, get_vehicle_filters, and 3 more. Their descriptions and schemas cost roughly 1,617 tokens of context every time the server is loaded.
Does the Apibara Vehicle Auction Data MCP server require authentication?
No. We connected to Apibara Vehicle Auction Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Apibara Vehicle Auction Data MCP server still maintained?
Apibara Vehicle Auction Data is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.