# Apibara Vehicle Auction Data (remote · apibara.tech)

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

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `apibara.tech`: 72/100 (this document), [markdown](https://verifymcp.io/servers/tech-apibara-vehicle-auction/apibara.md), [page](https://verifymcp.io/servers/tech-apibara-vehicle-auction/apibara)

## Channel facts

- Endpoint: `https://apibara.tech/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 507 tokens (~63/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 13% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http tech-apibara-vehicle-auction 'https://apibara.tech/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tech-apibara-vehicle-auction": {
      "url": "https://apibara.tech/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tech-apibara-vehicle-auction": {
      "type": "http",
      "url": "https://apibara.tech/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tech-apibara-vehicle-auction]
url = "https://apibara.tech/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tech-apibara-vehicle-auction": {
      "type": "remote",
      "url": "https://apibara.tech/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tech-apibara-vehicle-auction --url 'https://apibara.tech/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tech-apibara-vehicle-auction:
    url: "https://apibara.tech/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tech-apibara-vehicle-auction": {
      "Transport": "http",
      "Url": "https://apibara.tech/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tech-apibara-vehicle-auction -t streamable-http -u 'https://apibara.tech/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 72, +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.

### 2026-09-19 (score 71, +5)

- [security improvement] HTTPS: unverified → pass
- [functional improvement] Stability: unverified → 0.03

### 2026-09-18 (score 66)

First indexed and scored.

## MCP tools (8)

### `search_auction_vehicles` (~186 tokens)

Search auction vehicles

Search supported Copart and IAAI vehicle auction records. Use exact documented filters; fields can be nullable and source-dependent.

Input parameters:

- `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)

### `get_vehicle` (~46 tokens)

Get vehicle

Retrieve one supported vehicle record by the VIN or slug_vin accepted by the canonical detail endpoint.

Input parameters:

- `identifier` (string, required): VIN or slug_vin accepted by the canonical vehicle detail endpoint.

### `get_vehicle_history` (~55 tokens)

Get vehicle auction history

Retrieve retained Copart + IAAI auction history for one supported vehicle when available. This is not a complete ownership or accident history.

Input parameters:

- `identifier` (string, required): VIN or slug_vin accepted by the canonical vehicle detail endpoint.

### `get_related_vehicles` (~43 tokens)

Get related vehicles

Retrieve related supported auction vehicles.

Input parameters:

- `identifier` (string, required): VIN or slug_vin accepted by the canonical vehicle detail endpoint.
- `per_page` (integer)

### `get_vehicle_filters` (~28 tokens)

Get vehicle filters

Retrieve current supported filter metadata for search UIs and integrations.

Input parameters:

- `platform` (string)

### `list_auction_locations` (~45 tokens)

List auction locations

Retrieve supported auction facilities and locations.

Input parameters:

- `country` (string)
- `platform` (string)
- `s` (string)
- `state` (string)

### `calculate_shipping` (~59 tokens)

Calculate auction-to-port shipping

Retrieve supported auction-to-port shipping information by VIN or lot number when location and route data are available.

Input parameters:

- `lot_number` (string)
- `port` (string)
- `port_id` (integer|string)
- `vin` (string)

### `get_api_usage` (~25 tokens)

Get API usage

Retrieve authenticated API usage and current plan limits for the supplied X-API-Key.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tech-apibara-vehicle-auction/apibara#diagnostics

## Score history

- 2026-09-20: 72
- 2026-09-19: 71
- 2026-09-18: 66

## Common questions

### 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.

## Links

- Remote endpoint: https://apibara.tech/mcp
- Authorisation metadata: https://apibara.tech/.well-known/oauth-protected-resource/mcp
- Website: https://apibara.tech/en/vehicle-auction-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/tech-apibara-vehicle-auction/apibara.xml
- Changelog JSON feed: https://verifymcp.io/servers/tech-apibara-vehicle-auction/apibara.json
- HTML version of this page: https://verifymcp.io/servers/tech-apibara-vehicle-auction/apibara