US Product Recalls (FDA, NHTSA, CPSC)

● Active

io.github.santex85/us-recalls-mcp

US product recalls from FDA (food, drugs, devices), NHTSA (vehicles) and CPSC (consumer products).

Category
Legal & Government
Version
0.1.0
Registry
active
Published
11/18/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 21, 2026

Looks healthy: US Product Recalls (FDA, NHTSA, CPSC) is maintained, open source.

Maintained
Active
Last commit 4 days ago (Nov 18, 2026), 0 open issues.
Official registry
Active
Published as io.github.santex85/us-recalls-mcp in the official MCP registry, version 0.1.0.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
On your machine
A local mcpb package started by your client; it can reach whatever your user account can.
Credentials
None declared
The registry entry declares no required environment variables.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.

On GitHub

read Nov 18, 2026
Stars
0
Forks
0
Last push
Nov 18, 2026
License
MIT

Pythoncpscfdamcpmcp-servermodel-context-protocolnhtsaopenfdaproduct-safetypythonrecalls

From the README

US Recalls MCP server (FDA, NHTSA, CPSC) An MCP server that gives AI agents live access to official US product recalls: • FDA: food, drugs and medical devices, from openFDA enforcement reports • NHTSA: vehicles and vehicle equipment, tires and child seats • CPSC: consumer products such as toys, furniture and appliances, from SaferProducts.gov Every recall is returned in the same flat schema, so one call can answer questions like "were there any listeria recalls this month?", "does my 2022 RAV4 have open recalls?" or "what is recall 24V001000 about?". No API keys are required. It is a port of the us-recalls-monitor Apify actor. The normalisation is the same; the Apify, billing and "only new" state code is removed. Tools Example calls Source names: fdafood, fdadrug, fdadevice, nhtsavehicle, cpsc_consumer. The aliases fda, nhtsa, cpsc, food, drug, device, vehicle and consumer also work. Dates are YYYY-MM-DD or relative days (-30 = 30 days ago). Record fields source, agency, recallId, date, initiatedDate, title, product, firm, firmLocation, reason, consequence, classification, status, distribution, quantity, remedy, codeInfo, url, apiUrl. recall_details adds raw (extra source fields) and, for NHTSA, affectedVehicleCount.…

Read the full README on GitHub →

The most-starred Legal & Government servers in the index, with their live-check result.

ServerStarsLast pushLive check
Korean Law MCP2,891Nov 2026Working
EdgarTools2,859Nov 2026Local / not checked
Global law2,167Nov 2026Working
MCP Fiscal Brasil433Nov 2026Local / not checked
Legal Data Hunter422Nov 2026Needs sign-in

US Product Recalls (FDA, NHTSA, CPSC): questions people ask

Is US Product Recalls (FDA, NHTSA, CPSC) a remote or a local MCP server?
According to its entry in the official MCP registry, US Product Recalls (FDA, NHTSA, CPSC) ships as a local package (mcpb) that your client starts on your machine.
Is US Product Recalls (FDA, NHTSA, CPSC) safe to use?
Looks healthy: US Product Recalls (FDA, NHTSA, CPSC) is maintained, open source. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: On your machine; credentials: None declared. Serverdex check of Nov 21, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is US Product Recalls (FDA, NHTSA, CPSC) still maintained?
Active: the repository's last commit 4 days ago. Last push Nov 18, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 18, 2026.
How do I add US Product Recalls (FDA, NHTSA, CPSC) to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. Website Contacts & Socials (role emails, WhatsApp, LINE, Telegram)Contact channels from a website: role emails, WhatsApp, LINE, Telegram, socials. No personal data.
  2. US & UK Import Tariffs and Duty RatesUS HTS and UK Trade Tariff: HS code search, duty rates by origin and rough landed-cost estimates.
  3. OSS Audit (package due diligence)Open-source package due diligence: licences, release health, Scorecard, dependents, OSV vulns.
  4. OpenStreetMap POI SearchFind OpenStreetMap businesses and places by category or tag, plus geocoding and reverse geocoding.
Browse all Legal & Government →

Add the badge to your site

Show visitors that US Product Recalls (FDA, NHTSA, CPSC) is listed here — it’s also the link we check for a free listing.

US Product Recalls (FDA, NHTSA, CPSC) — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-santex85-us-recalls-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="US Product Recalls (FDA, NHTSA, CPSC) — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![US Product Recalls (FDA, NHTSA, CPSC) — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-santex85-us-recalls-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).