RecallDB
REMOTE · RECALLDB.APP
Official recalls from NHTSA, CPSC, FDA, USDA, Canada, UK, EU and Australia; VIN and barcode lookup.
Available components
Last scanned (14 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
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 Security83
- 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. 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. 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 Nov 26 +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.
- 18 Nov 26 +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.
- 16 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 15 Nov 26 72
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 21 Nov 2026 · Probed https://recalldb.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=recalldb.app | CN=WE1,O=Google Trust Services,C=US | 12 Nov 2026 | 10 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 39465929a10cba1130f4cd642a8440f |
| SANs: recalldb.app, *.recalldb.app | ||||||
| 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 secure
Validation of recalldb.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| recalldb.app. | DS published | 2371 | 13 | Verified |
| recalldb.app. | Verified address RRset verified with the apex keys |
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 |
| content-security-policy | script-src 'self' 'nonce-/qw2i2VBjMccE/YSjDH7xA==' https://challenges.cloudflare.com; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), serial=(), bluetooth=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://recalldb.app/mcp | Verified | 200 | |
| http (plaintext) | http://recalldb.app/mcp | HTTPS enforced | 301 | https://recalldb.app/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 →
barcode_lookup Look up a barcode ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The barcode number, digits only or with spaces and dashes. |
No output schema declared.
No examples provided.
get_recall Get a recall ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The recall id as returned by search_recalls, for example 21V215000 (NHTSA), cpsc-27064 or fda-98506. |
No output schema declared.
No examples provided.
search_recalls Search recalls ~267
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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). |
No output schema declared.
No examples provided.
vehicle_recalls Vehicle recalls by model and year ~110
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).
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | yes | The make, for example Honda. |
| model | string | yes | The model, for example Civic. |
| year | integer | yes | The model year, for example 2019. |
No output schema declared.
No examples provided.
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.
remote · recalldb.app
claude mcp add --transport http app-recalldb-recalldb 'https://recalldb.app/mcp'
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.