# Zovo VIN Recall Check (remote · vehicle-recalls.zovo.one)

Check recalls by VIN with live public vehicle records and downloadable XLSX and CSV reports.

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `vehicle-recalls.zovo.one`: 75/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-vehicle-recalls/vehicle-recalls.md), [page](https://verifymcp.io/servers/theluckystrike-vehicle-recalls/vehicle-recalls)

## Channel facts

- Endpoint: `https://vehicle-recalls.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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-10-23.

- **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**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 253 tokens (~84/item across 3 items; 2 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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.
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo VIN Recall Check MCP server?

Zovo VIN Recall Check is a hosted endpoint at https://vehicle-recalls.zovo.one/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 theluckystrike-vehicle-recalls 'https://vehicle-recalls.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-vehicle-recalls": {
      "url": "https://vehicle-recalls.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-vehicle-recalls": {
      "type": "http",
      "url": "https://vehicle-recalls.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-vehicle-recalls]
url = "https://vehicle-recalls.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-vehicle-recalls": {
      "type": "remote",
      "url": "https://vehicle-recalls.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-vehicle-recalls --url 'https://vehicle-recalls.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-vehicle-recalls:
    url: "https://vehicle-recalls.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-vehicle-recalls": {
      "Transport": "http",
      "Url": "https://vehicle-recalls.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-vehicle-recalls -t streamable-http -u 'https://vehicle-recalls.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-vehicle-recalls": {
      "type": "http",
      "url": "https://vehicle-recalls.zovo.one/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-10-23 (score 75, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-22 (score 75)

First indexed and scored.

## MCP tools (2)

### `check_vin_recalls` (~120 tokens)

Check VIN recalls

Use this when the user wants a vin decoder, recall check by vin, or batch vin decoder with vehicle recalls and XLSX and CSV reports from public NHTSA data. Up to 50 VINs and 40 source requests per call; campaigns apply to the year, make and model. Do not use for VIN-specific repair status or booking repairs.

Input parameters:

- `vins` (array, required): VIN list to decode and check, e.g. ["1HGCV1F35JA000000"]. Up to 50 entries; duplicates are checked once.

Output parameters:

- `downloads` (object)
- `source` (string)
- `summary` (object)
- `truncated` (boolean)
- `vehicles` (array)

### `find_recalls_by_vehicle` (~117 tokens)

Find recalls by vehicle

Use this when the user wants a car recall lookup, vehicle recalls, or fleet recall check by model year, make and model without a VIN, with public NHTSA data and XLSX and CSV reports. Up to 20 vehicles and 40 source requests per call. Do not use for VIN-specific repair status or booking repairs.

Input parameters:

- `vehicles` (array, required): Vehicles to check, e.g. [{"model_year":2018,"make":"make from title","model":"model from title"}]. Up to 20 entries.

Output parameters:

- `downloads` (object)
- `source` (string)
- `summary` (object)
- `truncated` (boolean)
- `vehicles` (array)

## Diagnostics

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

## Score history

- 2026-10-23: 75
- 2026-10-22: 75

## Common questions

### What is the Zovo VIN Recall Check MCP server?

Zovo VIN Recall Check is an MCP server listed in the public MCP registry as io.github.theluckystrike/vehicle-recalls. Check recalls by VIN with live public vehicle records and downloadable XLSX and CSV reports. This page covers its hosted endpoint (https://vehicle-recalls.zovo.one/mcp).

### Is the Zovo VIN Recall Check MCP server safe to use?

Zovo VIN Recall Check scores 75 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 Zovo VIN Recall Check MCP server expose?

Zovo VIN Recall Check exposes 2 tools: check_vin_recalls, find_recalls_by_vehicle. Their descriptions and schemas cost roughly 237 tokens of context every time the server is loaded.

### Does the Zovo VIN Recall Check MCP server require authentication?

No. We connected to Zovo VIN Recall Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zovo VIN Recall Check MCP server still maintained?

Zovo VIN Recall Check is still listed as active in the MCP registry. We last reached this channel on 23 October 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://vehicle-recalls.zovo.one/mcp
- Website: https://vehicle-recalls.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-vehicle-recalls/vehicle-recalls.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-vehicle-recalls/vehicle-recalls.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-vehicle-recalls/vehicle-recalls