# RecallDB (remote · recalldb.app)

Official recalls from NHTSA, CPSC, FDA, USDA, Canada, UK, EU and Australia; VIN and barcode lookup.

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

## Components

- remote · `recalldb.app`: 75/100 (this document), [markdown](https://verifymcp.io/servers/app-recalldb-recalldb/recalldb.md), [page](https://verifymcp.io/servers/app-recalldb-recalldb/recalldb)

## Channel facts

- Endpoint: `https://recalldb.app/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-11-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 746 tokens (~186/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the RecallDB MCP server?

RecallDB is a hosted endpoint at https://recalldb.app/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 app-recalldb-recalldb 'https://recalldb.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-recalldb-recalldb": {
      "url": "https://recalldb.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-recalldb-recalldb": {
      "type": "http",
      "url": "https://recalldb.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-recalldb-recalldb]
url = "https://recalldb.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-recalldb-recalldb": {
      "type": "remote",
      "url": "https://recalldb.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-recalldb-recalldb --url 'https://recalldb.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-recalldb-recalldb:
    url: "https://recalldb.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-recalldb-recalldb": {
      "Transport": "http",
      "Url": "https://recalldb.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-recalldb-recalldb -t streamable-http -u 'https://recalldb.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-recalldb-recalldb": {
      "type": "http",
      "url": "https://recalldb.app/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-11-20 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-15 (score 72)

First indexed and scored.

## MCP tools (4)

### `search_recalls` (~267 tokens)

Search recalls

Full-text search of recall notices by product name, brand, model number, recall number or UPC across vehicles, motorcycles, RVs, car seats, tires, equipment, consumer products, food, supplements, pet food, cosmetics, drugs and medical devices. Returns up to 50 results a page, each with an id for get_recall and a link to the official notice.

Input parameters:

- `agency` (string): Only this agency.
- `category` (string): Only this category.
- `from` (string): Only recalls dated on or after this day (YYYY-MM-DD).
- `fuzzy` (boolean): Default true: if nothing matches, names (makes, brands, companies, products) are tried with a corrected spelling and corrected_query says so. Recall numbers, UPCs and model numbers are always exact.…
- `page` (integer): Page number (default 1).
- `query` (string, required): What to search for, for example "bunk bed", "Graco car seat" or a model number.
- `state` (string): A U.S. state code such as TX: keeps recalls sold nationwide, in that state or with no clear distribution.
- `to` (string): Only recalls dated on or before this day (YYYY-MM-DD).

### `get_recall` (~91 tokens)

Get a recall

The full record for one recall: the official problem, consequence and remedy text, the issuing company, units, official codes as listed, and the agency, its own number and a link to the official notice.

Input parameters:

- `id` (string, required): The recall id as returned by search_recalls, for example 21V215000 (NHTSA), cpsc-27064 or fda-98506.

### `barcode_lookup` (~128 tokens)

Look up a barcode

Recalls whose official notice lists a barcode (UPC-A, EAN-13, GTIN-14, UPC-E or EAN-8; the check digit must be right). Each match includes the notice's own text and the lot codes, best-by dates and serial numbers written near the barcode. A match means the code appears in a notice; the user must verify lot codes and dates against the official notice. No match does not mean there is no recall: not every recall lists barcodes.

Input parameters:

- `code` (string, required): The barcode number, digits only or with spaces and dashes.

### `vehicle_recalls` (~110 tokens)

Vehicle recalls by model and year

NHTSA recalls for a car make, model and model year, as listed by the recall notices. Recalls are by model, not by individual vehicle: this does not say whether one specific car has an open recall (the owner checks the VIN with NHTSA or the carmaker).

Input parameters:

- `make` (string, required): The make, for example Honda.
- `model` (string, required): The model, for example Civic.
- `year` (integer, required): The model year, for example 2019.

## Diagnostics

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

## Score history

- 2026-11-21: 75
- 2026-11-20: 75
- 2026-11-19: 74
- 2026-11-18: 74
- 2026-11-17: 73
- 2026-11-16: 73
- 2026-11-15: 72

## Common questions

### What is the RecallDB MCP server?

RecallDB is an MCP server listed in the public MCP registry as app.recalldb/recalldb. Official recalls from NHTSA, CPSC, FDA, USDA, Canada, UK, EU and Australia; VIN and barcode lookup. This page covers its hosted endpoint (https://recalldb.app/mcp).

### Is the RecallDB MCP server safe to use?

RecallDB 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 RecallDB MCP server expose?

RecallDB exposes 4 tools: search_recalls, get_recall, barcode_lookup, vehicle_recalls. Their descriptions and schemas cost roughly 596 tokens of context every time the server is loaded.

### Does the RecallDB MCP server require authentication?

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

### Is the RecallDB MCP server still maintained?

RecallDB is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the RecallDB MCP server?

VerifyMCP ran 13 checks on RecallDB, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://recalldb.app/mcp
- Authorisation metadata: https://recalldb.app/.well-known/oauth-protected-resource/mcp
- Website: https://recalldb.app/mcp
- Changelog RSS feed: https://verifymcp.io/servers/app-recalldb-recalldb/recalldb.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-recalldb-recalldb/recalldb/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-recalldb-recalldb/recalldb.json
- HTML version of this page: https://verifymcp.io/servers/app-recalldb-recalldb/recalldb
