Apibara Vehicle Auction Data
REMOTE · APIBARA.TECH · SCANNED SEP 20
Read-only MCP for Copart and IAA/IAAI search, history, filters, locations, shipping, and usage.
Available components
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 Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 507 tokens (~63/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 13% of tool parameters carry a description.Partial
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
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'
{
"mcpServers": {
"tech-apibara-vehicle-auction": {
"url": "https://apibara.tech/mcp"
}
}
} {
"servers": {
"tech-apibara-vehicle-auction": {
"type": "http",
"url": "https://apibara.tech/mcp"
}
}
} [mcp_servers.tech-apibara-vehicle-auction] url = "https://apibara.tech/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tech-apibara-vehicle-auction": {
"type": "remote",
"url": "https://apibara.tech/mcp",
"enabled": true
}
}
} openclaw mcp add tech-apibara-vehicle-auction --url 'https://apibara.tech/mcp' --transport streamable-http
mcp_servers:
tech-apibara-vehicle-auction:
url: "https://apibara.tech/mcp" {
"McpServers": {
"tech-apibara-vehicle-auction": {
"Transport": "http",
"Url": "https://apibara.tech/mcp"
}
}
} assistant mcp add tech-apibara-vehicle-auction -t streamable-http -u 'https://apibara.tech/mcp'
{
"mcpServers": {
"tech-apibara-vehicle-auction": {
"type": "http",
"url": "https://apibara.tech/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +5
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- 18 Sept 26 66
First indexed and scored.
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 20 Sept 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 | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | e29138d5ea06f8710e5c222c4b043184 |
| 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 ~59
Retrieve supported auction-to-port shipping information by VIN or lot number when location and route data are available.
| Name | Type | Req | Description |
|---|---|---|---|
| lot_number | string | – | – |
| port | string | – | – |
| port_id | integer|string | – | – |
| vin | string | – | – |
No output schema declared.
No examples provided.
get_api_usage Get API usage ~25
Retrieve authenticated API usage and current plan limits for the supplied X-API-Key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_related_vehicles Get related vehicles ~43
Retrieve related supported auction vehicles.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | VIN or slug_vin accepted by the canonical vehicle detail endpoint. |
| per_page | integer | – | – |
No output schema declared.
No examples provided.
get_vehicle Get vehicle ~46
Retrieve one supported vehicle record by the VIN or slug_vin accepted by the canonical detail endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | VIN or slug_vin accepted by the canonical vehicle detail endpoint. |
No output schema declared.
No examples provided.
get_vehicle_filters Get vehicle filters ~28
Retrieve current supported filter metadata for search UIs and integrations.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | – |
No output schema declared.
No examples provided.
get_vehicle_history Get vehicle auction history ~55
Retrieve retained Copart + IAAI auction history for one supported vehicle when available. This is not a complete ownership or accident history.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | VIN or slug_vin accepted by the canonical vehicle detail endpoint. |
No output schema declared.
No examples provided.
list_auction_locations List auction locations ~45
Retrieve supported auction facilities and locations.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| platform | string | – | – |
| s | string | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
search_auction_vehicles Search auction vehicles ~186
Search supported Copart and IAAI vehicle auction records. Use exact documented filters; fields can be nullable and source-dependent.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| facility_id | integer|string | – | – |
| has_shipping_price | boolean | – | – |
| loc_state | string | – | – |
| lot_status | string | – | – |
| lot_sub_status | string | – | – |
| make | string | – | – |
| model | string | – | – |
| per_page | integer | – | – |
| platform | string | – | – |
| price_max | number | – | – |
| price_min | number | – | – |
| s | string | – | VIN, lot number or title search. |
| today_only | boolean | – | – |
| upcoming | string | – | – |
| updated_within_minutes | integer | – | – |
| year_from | integer | – | – |
| year_to | integer | – | – |
No output schema declared.
No examples provided.
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 72 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 487 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.