Medplum MCP
Securely access and manage FHIR healthcare data stored in Medplum.
US product recalls from FDA (food, drugs, devices), NHTSA (vehicles) and CPSC (consumer products).
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
Download the maker’s .mcpb file
The .mcpb file comes straight from the maker; we do not change it
Use US Product Recalls (FDA, NHTSA, CPSC) and tell me what you can do for me, then show me one thing✓ If Claude says it is using US Product Recalls (FDA, NHTSA, CPSC) or shows a US Product Recalls (FDA, NHTSA, CPSC) tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect US Product Recalls (FDA, NHTSA, CPSC) yet
US Product Recalls (FDA, NHTSA, CPSC) runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect US Product Recalls (FDA, NHTSA, CPSC)
B · Others in Clinics & health that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Claude Code cannot connect US Product Recalls (FDA, NHTSA, CPSC) yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect US Product Recalls (FDA, NHTSA, CPSC)
Cursor cannot connect US Product Recalls (FDA, NHTSA, CPSC) yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect US Product Recalls (FDA, NHTSA, CPSC)
VS Code cannot connect US Product Recalls (FDA, NHTSA, CPSC) yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect US Product Recalls (FDA, NHTSA, CPSC)
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account santex85, which owns the repo
Code last changed yesterday
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/santex85-us-recalls-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed yesterday, and the latest version (0.1.0) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Medplum MCP, Mirobody, Codescene MCP Server, WHOOP — MissingMCP, Marrow
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Securely access and manage FHIR healthcare data stored in Medplum.
An MCP server that provides CodeScene Code Health analysis tools.
WHOOP recovery, strain, sleep and workouts in Claude via official WHOOP OAuth. Free, open source.
Marrow Health: your Apple Health data over MCP, from the free iOS app. Reads, and writes on demand.
| This one US Product Recalls (FDA, NHTSA, CPSC) | Medplum MCP | Mirobody | Codescene MCP Server | WHOOP — MissingMCP | Marrow | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Installs on your computer | Installs on your computer | Runs in the cloud, nothing to install | Installs on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 3/3 | 2/3 | 2/4 | 3/3 |
| License | MIT | Apache-2.0 | Apache-2.0 | NOASSERTION | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
An MCP server that gives AI agents live access to official US product recalls:
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.
| Tool | What it does |
|---|---|
search_recalls | Keyword or brand search across all five datasets in a date window (default: last 365 days) |
recent_recalls | Latest recalls of the last N days (1-90), with the sources interleaved |
vehicle_recalls | Complete NHTSA recall history for one make, model and year. If the model name is wrong, lists the valid model names |
recall_details | Full, untrimmed record for one recall ID (FDA F-0276-2017, NHTSA 24V001000, CPSC 27082) |
// search_recalls
{"query": "listeria, salmonella", "sources": ["fda_food"], "date_from": "-90", "limit": 20} {"query": "Ford, Tesla", "sources": ["nhtsa"], "date_from": "2026-01-01"} {"query": "stroller", "sources": ["cpsc"]}
// recent_recalls {"days": 7, "limit": 30} {"sources": ["fda_drug", "fda_device"], "days": 30}
// vehicle_recalls {"make": "Toyota", "model": "RAV4", "year": 2022}
// recall_details {"recall_id": "24V001000"}
Source names: fda_food, fda_drug, fda_device, nhtsa_vehicle, 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).
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. Fields that a source does not provide are null. The date field is the FDA enforcement report date, the NHTSA report-received date or the CPSC recall date.
| Source | search / recent | details |
|---|---|---|
| FDA | api.fda.gov/{food,drug,device}/enforcement.json, server-side search on product description, recalling firm and reason | recall_number:"…" |
| NHTSA | official daily flat file FLAT_RCL_POST_2010.zip (about 15 MB, cached in memory for 6 h), filtered locally by date and keyword | api.nhtsa.gov/recalls/campaignNumber |
| NHTSA by vehicle | api.nhtsa.gov/recalls/recallsByVehicle; model names come from /products/vehicle/models | |
| CPSC | saferproducts.gov/RestWebServices/Recall; keyword search is a server-side RecallTitle match (titles name the firm, product and hazard) | RecallNumber |
python3 -m venv .venv && .venv/bin/pip install -r requirements.txt
.venv/bin/python src/server.py # streamable-http on 0.0.0.0:8080, endpoint /mcp PORT=8092 .venv/bin/python src/server.py MCP_TRANSPORT=stdio .venv/bin/python src/server.py .venv/bin/python tests/live_test.py # live smoke test of every tool
Environment: HOST, PORT, MCP_TRANSPORT, and optionally OPENFDA_API_KEY (a free key from open.fda.gov that raises the daily openFDA quota).
search_recalls and recent_recalls return at most 100 records per call. Long text fields are trimmed to 400 characters in list output; recall_details gives up to 2,000-4,000 characters per field.OPENFDA_API_KEY for heavy use.recent_recalls with days < 7 may show no FDA records.url points to the Enforcement Report search page and apiUrl links to the exact record.static.nhtsa.gov. These are US federal government works and public (17 U.S.C. §105).This project is not affiliated with or endorsed by the FDA, NHTSA, CPSC or any US agency. The data is provided "as is" and can contain errors or delays. Before any safety or medical decision, check the official notice linked in url.
The server returns product- and firm-level recall data only. It never copies contact persons, and it masks phone numbers and e-mail addresses that appear in CPSC remedy, injury or distribution text. The server keeps no logs of queries or results.
Local (stdio). Clone the repo, create the venv as above, then add this to claude_desktop_config.json (or your client's MCP config), with the paths changed to where you cloned it:
{
"mcpServers": { "us-recalls": { "command": "/path/to/us-recalls-mcp/.venv/bin/python", "args": ["/path/to/us-recalls-mcp/src/server.py"], "env": {"MCP_TRANSPORT": "stdio"} } } }
If you have a free openFDA key, add "OPENFDA_API_KEY": " " to env.
Remote (streamable HTTP). Run .venv/bin/python src/server.py on a server and point any client that supports remote MCP servers at http:// :8080/mcp. GET /health returns {"status": "healthy"}.
MIT, see LICENSE. The data returned by the tools stays under the terms of its sources (see above).