mcpbeat Sign in

RecallLens MCP Server

by trystarrynightops Your server? Claim it
answering

RecallLens is answering right now. Last checked 10 min ago. It exposes 5 tools.

US recall lookup: NHTSA vehicle and VIN recalls, FDA food, drug and device recalls, CPSC products.

Uptime history 22 hours of history
22 hours agonow
100.0%
Uptime 24h
80 of 80 checks
5
Tools
read from the server
228 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 10 November 2026. No other catalogue keeps this.

10 Nov a tool changed version

Nothing serious here today

Today is the operative word: we check RecallLens every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add recalllens --transport http https://recalls.trystarrynightops.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://recalls.trystarrynightops.com/mcp
~/.codex/config.toml
[mcp_servers.recalllens]
url = "https://recalls.trystarrynightops.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "recalllens": {
      "url": "https://recalls.trystarrynightops.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "recalllens": {
      "type": "http",
      "url": "https://recalls.trystarrynightops.com/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

vehicle
vehicle_recall_campaign
Returns one NHTSA recall campaign by its campaign number (e.g. 20V314000, 20V-314 or 23C001): manufacturer, report date, component, summary, consequence, remedy, potential number of units affected, advisories, and the makes, models and model years it covers. Works for vehicle (V), equipment (E), tire (T) and child seat (C) campaigns.
vehicle_recalls
Lists NHTSA safety recall campaigns for a US-market vehicle by make, model and model year, newest first: campaign number, report date, component, a short defect summary, the safety risk, the remedy, any "do not drive" or "park outside" advisory, and a link to the NHTSA recall page. If the model name does not match NHTSA's naming, it returns the closest NHTSA model names for that make and year. It covers campaigns issued for the model, not whether a specific vehicle has been repaired.
consumer
consumer_product_recalls
Searches US Consumer Product Safety Commission (CPSC) recalls of consumer products such as toys, cribs, strollers, furniture, heaters, e-bikes, batteries and appliances, newest first. Keywords (every word must appear) are matched against the recall title, product names, models and types, description, hazard, firm and retailer names, and UPCs; a CPSC recall number also works. Optional recall-date range. Returns recall number, date, title, products, units, hazard, remedy and the cpsc.gov link. Does not cover vehicles, food, drugs, cosmetics or medical devices.
food
food_drug_device_recalls
Searches FDA recall enforcement reports published through openFDA for food, drugs and medical devices, newest report date first. Optional filters: keywords (every word must appear in the product description, reason for recall, recalling firm or lot/code information; "quoted phrases" are kept together), product type, classification (Class I, II or III), status and report-date range. Returns recall number, class, status, firm, product, reason, distribution, dates and a link to the openFDA record. The data is FDA's weekly Enforcement Report (2012 onward), which can lag FDA's recall announcements.
vin
vin_recalls
Checks a 17-character vehicle identification number (VIN): validates its check digit, decodes make, model and model year with NHTSA's vPIC service (only the first 11 characters are sent, or 14 for low-volume manufacturers; never the serial number), then lists the NHTSA safety recall campaigns issued for that make, model and year, with the same fields as vehicle_recalls. It does not confirm whether this specific vehicle is included in a campaign or has been repaired; NHTSA's own VIN lookup at nhtsa.gov/recalls is the official source for that.

Endpoints

URLTransportStateLatencyChecked
https://recalls.trystarrynightops.com/mcp streamable-http answering 188 ms 10 min ago

Alternatives to RecallLens

same job, measured the same way
RecallScout
by yc-droid

US vehicle, car-seat, product and food recalls, VIN decoding and crash ratings (NHTSA, CPSC, FDA).

8 tools answering
Product safety & recalls
by fourzerotwo

UK product recalls, MHRA drug and device alerts, FSA food alerts, accident reports and US CPSC…

15 tools answering
FDA Recall Checker (openFDA)
by wyeming95-rgb

Check products against FDA food, drug and device recalls; drug labels, NDC, 510(k) via openFDA

answering
Vin Recall MCP
by pratikmehkarkar

Decodes US VINs and looks up open NHTSA safety recall campaigns for a vehicle.

2 tools answering
Recall Canary
by recallcanary

U.S. federal product recalls from FDA, FSIS, CPSC, and NHTSA, in one schema.

2 tools answering
US FDA Recalls (Food, Drug, Device) MCP
by donniertf-hub

FDA food, drug and medical-device recalls by keyword, class and state.

3 tools answering
R
Recall Risk
by dropwatchhq

Check a product's recall risk: score + active CPSC/FDA/NHTSA recalls for a product or brand.

1 tools answering
Canada Health Product Recalls MCP
by donniertf-hub

Health Canada recalls for drugs, natural health products and medical devices.

4 tools answering

RecallLens — questions

Answers built from our own checks of this server.

What can RecallLens do?
It exposes 5 tools, read directly from the server on our last check. Among them: consumer_product_recalls, food_drug_device_recalls, vehicle_recall_campaign, vehicle_recalls, vin_recalls. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is RecallLens working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 80 of 80 checks got a reply (100.0%), average response time 228 ms. The bar chart above shows every period we have measured.
How do I connect RecallLens?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does RecallLens need an API key?
No. RecallLens completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is RecallLens?
It answers our handshake in 228 ms on average, which is faster than 59% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.