FDA Recall Checker (openFDA)

io.github.wyeming95-rgbPublished by GitHub account wyeming95-rgbv1.0.0Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableLocation & LifestyleData & Analytics

Overview

AI-generated overview

Remote Apify-hosted MCP server that lets an assistant query openFDA data on food, drug and device recalls, drug labels, NDC codes and 510(k) clearances.

What you can do
Check products against FDA food, drug and device recall records via openFDA data, including recall details and statuses. Look up drug labeling information and NDC product codes. Retrieve 510(k) premarket clearance records for medical devices. All queries run through an Apify-hosted remote endpoint rather than a local package.
When to use it
Useful when you need to verify whether a product, drug or medical device has been recalled, or to pull FDA label, NDC or 510(k) reference data while researching products, compliance or safety questions.
Requirements
A remote MCP endpoint at mcp.apify.com over streamable HTTP. An Apify account and API token are required, sent as a Bearer token in the Authorization header; OAuth authentication is declared as required. Network access to the endpoint is needed.
Before you install
The server requires an Apify API token in the Authorization header, which is a credential granting access to your Apify account; keep it private. Queries are sent to Apify's hosted service and onward to openFDA data, so search terms leave your machine. Recall and label data are informational and should not be treated as medical or regulatory advice.

Installation

In SourceWeft

  1. Open FDA Recall Checker (openFDA) in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.wyeming95-rgb%2Fopenfda-recalls/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "fda-recall-checker-openfda": {
      "type": "http",
      "url": "https://mcp.apify.com/?actors=smartmoney-data/openfda"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.