# recall-check (remote · recalls.bot2botlabs.com)

U.S. CPSC/NHTSA recall status with agency links and a signed receipt.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `recalls.bot2botlabs.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-bot2botlabs-recall-check/recalls.md), [page](https://verifymcp.io/servers/com-bot2botlabs-recall-check/recalls)

## Channel facts

- Endpoint: `https://recalls.bot2botlabs.com/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**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 355 tokens (~177/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 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 recall-check MCP server?

recall-check is a hosted endpoint at https://recalls.bot2botlabs.com/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 com-bot2botlabs-recall-check 'https://recalls.bot2botlabs.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-bot2botlabs-recall-check": {
      "url": "https://recalls.bot2botlabs.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-bot2botlabs-recall-check": {
      "type": "http",
      "url": "https://recalls.bot2botlabs.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-bot2botlabs-recall-check]
url = "https://recalls.bot2botlabs.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-bot2botlabs-recall-check": {
      "type": "remote",
      "url": "https://recalls.bot2botlabs.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-bot2botlabs-recall-check --url 'https://recalls.bot2botlabs.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-bot2botlabs-recall-check:
    url: "https://recalls.bot2botlabs.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-bot2botlabs-recall-check": {
      "Transport": "http",
      "Url": "https://recalls.bot2botlabs.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-bot2botlabs-recall-check -t streamable-http -u 'https://recalls.bot2botlabs.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-bot2botlabs-recall-check": {
      "type": "http",
      "url": "https://recalls.bot2botlabs.com/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 68, +1)

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

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

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

### 2026-11-16 (score 66, +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-11-15 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 65)

First indexed and scored.

## MCP tools (2)

### `check_recall` (~296 tokens)

Checks U.S. government recall records and returns the status with the agency's own links and a signed receipt. Give `product` (a name, matched against CPSC recall titles) or `vehicle` (model year, make, model, looked up at NHTSA). Returns status recalls_found with the newest recalls (id, title, date, summary, hazard, remedy, link) or none_found; confidence says how far to trust the search (CPSC matches title words; NHTSA is exact per model). Confidence unknown when the agency's answer could not be read. Call it before advising on a used product or vehicle, or when asked whether something has been recalled.

Input parameters:

- `product` (string): Consumer product to check with the U.S. CPSC. Words matched against recall titles, which read like "Peloton Recalls Tread+ Treadmills", so use the brand or the product name, not both: "Tread+" or "Ro…
- `since` (string): Products only: ignore CPSC recalls announced before this date (YYYY-MM-DD). Narrows the list; it does not make a slow CPSC search faster.
- `vehicle` (object): Vehicle to check with the U.S. NHTSA by model year, make and model. Give either product or vehicle, not both.

### `get_receipt` (~59 tokens)

Fetch a receipt issued by check_recall (format v1, signed, software-only TRACE record). The same document is served at https://recalls.bot2botlabs.com/receipts/{receipt_id}.

Input parameters:

- `receipt_id` (string, required)

## Diagnostics

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

## Score history

- 2026-11-21: 68
- 2026-11-20: 68
- 2026-11-19: 67
- 2026-11-18: 67
- 2026-11-17: 66
- 2026-11-16: 66
- 2026-11-15: 65
- 2026-11-14: 65

## Common questions

### What is the recall-check MCP server?

recall-check is an MCP server listed in the public MCP registry as com.bot2botlabs/recall-check. U.S. CPSC/NHTSA recall status with agency links and a signed receipt. This page covers its hosted endpoint (https://recalls.bot2botlabs.com/mcp).

### Is the recall-check MCP server safe to use?

recall-check scores 68 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 recall-check MCP server expose?

recall-check exposes 2 tools: check_recall, get_receipt. Their descriptions and schemas cost roughly 355 tokens of context every time the server is loaded.

### Does the recall-check MCP server require authentication?

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

### Is the recall-check MCP server still maintained?

recall-check 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 recall-check MCP server?

VerifyMCP ran 12 checks on recall-check, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about recall-check: Authorization. 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://recalls.bot2botlabs.com/mcp
- Website: https://recalls.bot2botlabs.com/agents/recall-check
- Changelog RSS feed: https://verifymcp.io/servers/com-bot2botlabs-recall-check/recalls.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-bot2botlabs-recall-check/recalls/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-bot2botlabs-recall-check/recalls.json
- HTML version of this page: https://verifymcp.io/servers/com-bot2botlabs-recall-check/recalls
