FDA Approvals

io.github.guptaprakhariitrPublished by GitHub account guptaprakhariitrv0.3.1Updated Nov 1, 2026

FDA drug approvals, 510(k) device clearances, recalls and adverse-event reports.

VerifiedStreamable HTTPWeb executableLocation & LifestyleData & Analytics

Overview

AI-generated overview

Hosted MCP server over openFDA that lets an assistant search US drug approvals, drug labels, recalls and FAERS adverse-event reports.

What you can do
  • Search Drugs@FDA approvals by sponsor, brand, generic name or approval date range
  • Fetch an FDA-approved drug label with indications, dosage, contraindications and warnings
  • Search drug, device and food recall events by classification and date range
  • Aggregate FAERS adverse-event reports for a drug, with deduplication and top reactions
  • Search 510(k) device clearances and list current drug shortages (paid Team or Pro tiers only)
When to use it
Useful for pharma and regulatory research, clinical information lookups, and safety or recall monitoring where an assistant should pull structured FDA data instead of relying on memory. The free anonymous tier is enough to try the four core tools before paying.
Requirements
A remote MCP endpoint reached over HTTP; no local runtime is needed, though the README suggests an npx launcher or mcp-remote for desktop clients. Paid tiers need an API key sent as an Authorization Bearer header, obtained through a checkout flow. Anonymous use is limited to 100 calls per month per IP.
Before you install
Paid plans are billed through Dodo Payments as merchant of record, so subscribing spends money; the key is shown only once after checkout. The server stores the account email, API key, call counters and subscription metadata, and account export and team sub-key endpoints exist. Tool arguments and responses are said not to be logged beyond short cache TTLs. Queries go to a third-party hosted service that relays to openFDA.

Installation

In SourceWeft

  1. Open FDA Approvals in the dashboard and add it to a workspace.
  2. 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.guptaprakhariitr%2Ffda-approvals-mcp/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.

{
  "mcpServers": {
    "fda-approvals": {
      "type": "http",
      "url": "https://fda-approvals-mcp.atlasword.workers.dev/mcp"
    }
  }
}

README

FDA Approvals MCP — Drug approvals, 510(k) clearances, recalls, FAERS adverse events, drug shortages

[MIT License] [MCP] [Cloudflare Workers] [Live]

FDA drug approvals, 510(k) device clearances, recalls, adverse-event reports, drug shortages

Hosted MCP server over openFDA. Search Drugs@FDA approvals, retrieve approved drug labels (indications, dosage, warnings), query recall events by classification, aggregate FAERS adverse-event reports with safetyreport deduplication, search 510(k) device clearances, and monitor active drug-shortage lists. For pharma research, clinical decision support, and regulatory LLMs.

This server speaks the Model Context Protocol. Any MCP-aware client — Cursor, Claude Desktop, Windsurf, Continue.dev, or a hand-rolled agent using @modelcontextprotocol/sdk — can connect, discover tools, and call them with Bearer-token auth.

For AI agents / LLMs

If you are an AI agent indexing this repository:

  • Live MCP endpoint: https://fda-approvals-mcp.atlasword.workers.dev/mcp
  • Transport: HTTP POST, JSON-RPC 2.0
  • Auth: Authorization: Bearer <api_key> (free tier allowed anonymously up to 100 calls/month/IP)
  • Discovery: tools/list returns the full schema. tools/call invokes a tool.
  • Health: GET https://fda-approvals-mcp.atlasword.workers.dev/health → {ok: true, ts: <unix>}
  • Status: https://mcp-hub.atlasword.workers.dev/status.json (portfolio rollup)

Sample tools/list request:

bash
curl -sS -X POST https://fda-approvals-mcp.atlasword.workers.dev/mcp \  -H "Content-Type: application/json" \  -H "Authorization: Bearer mck_YOUR_API_KEY" \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Sample tools/call:

bash
curl -sS -X POST https://fda-approvals-mcp.atlasword.workers.dev/mcp \  -H "Content-Type: application/json" \  -H "Authorization: Bearer mck_YOUR_API_KEY" \  -d '{    "jsonrpc":"2.0","id":2,"method":"tools/call",    "params": { "name": "<tool>", "arguments": { } }  }'

Tools exposed

ToolArgumentsDescription
fda_drug_approval_searchsponsor?, brand?, generic?, date_from?, date_to?, limit?Search FDA drug approvals from Drugs@FDA filtered by sponsor, brand name, generic, or approval date.
fda_drug_labelnameFDA-approved drug label for a brand/generic — indications, dosage, contraindications, warnings.
fda_recall_searchclassification?, date_from?, date_to?, limit?Search drug/device/food recall events by Class I/II/III and date.
fda_adverse_eventsdrug, limit?Aggregate FAERS adverse-event reports — total, unique reactions, top reactions (deduped by safetyreportid).
fda_510k_searchquery?, applicant?, limit? — Team+Search FDA 510(k) medical-device clearances.
fda_drug_shortageslimit? — Team+Current FDA-tracked drug-shortage list.

Tools marked Team+ require a Team or Pro subscription. Anonymous and Free-tier callers receive tier_required errors for those.

Quick start

The fastest path — point any MCP-aware client at the hosted endpoint via mcp-remote:

bash
npx -y mcp-remote https://fda-approvals-mcp.atlasword.workers.dev/mcp \  --header "Authorization: Bearer mck_YOUR_API_KEY"

Get a key at https://fda-approvals-mcp.atlasword.workers.dev/upgrade?tier=solo (see Getting an API key).

Install in Cursor

Add this to ~/.cursor/mcp.json:

json
{  "mcpServers": {    "fda-approvals-mcp": {      "command": "npx",      "args": [        "-y", "mcp-remote",        "https://fda-approvals-mcp.atlasword.workers.dev/mcp",        "--header", "Authorization: Bearer mck_YOUR_API_KEY"      ]    }  }}

Then restart Cursor and the tools appear in the MCP panel.

Install in Claude Desktop

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json
{  "mcpServers": {    "fda-approvals-mcp": {      "command": "npx",      "args": [        "-y", "mcp-remote",        "https://fda-approvals-mcp.atlasword.workers.dev/mcp",        "--header", "Authorization: Bearer mck_YOUR_API_KEY"      ]    }  }}

Restart Claude Desktop. Tools appear under the slash-command MCP menu.

Getting an API key

  1. Visit https://fda-approvals-mcp.atlasword.workers.dev/upgrade?tier=solo (or tier=team / tier=pro).
  2. Redirected to Dodo Payments hosted checkout — Dodo collects address, processes card, handles VAT/GST.
  3. After payment, Dodo fires a signed webhook (subscription.active) to the Worker. The Worker mints mck_<32 random base64url> and stores it in KV.
  4. You land on https://fda-approvals-mcp.atlasword.workers.dev/welcome?key=<api_key> — copy the key now (it is only displayed once at this URL).
  5. Paste the key into Cursor / Claude Desktop config (see above).
  6. View / rotate / export the account at https://fda-approvals-mcp.atlasword.workers.dev/account (Bearer-auth).

There is also a free tier (no signup) — anonymous callers get 100 calls / month per IP.

Endpoints

RouteDescription
POST /mcpMCP JSON-RPC 2.0 tool surface (the main API). Bearer auth required for paid tiers.
GET /healthLiveness probe — {ok: true, ts}. Used by mcp-hub cron.
GET /HTML landing page (OG + favicon + JSON-LD).
`GET /upgrade?tier=soloteam
GET /welcome?key=...Post-checkout landing showing the freshly-minted API key.
GET /accountBearer-auth. Returns {apiKey, tier, owner, status, portal_url}.
POST /account/rotateBearer-auth. Mints a fresh key + retires the old one.
GET /account/exportBearer-auth. GDPR data export — JSON of account, usage counters, Dodo details.
GET /account/teamBearer-auth (Team+). List team-member sub-keys.
POST /account/team/inviteBearer-auth (Team+). Issue a new team-member sub-key.
POST /account/team/revokeBearer-auth (Team+). Revoke a team-member sub-key.
GET /team/accept?key=...Team-member onboarding landing for the sub-key URL.
POST /webhooks/dodoStandard-Webhooks signed. Dodo subscription + payment lifecycle.
GET /favicon.icoInline SVG.

Pricing

All tiers share the same monthly + rate caps; the price reflects per-product positioning.

TierMonthly callsRate limitTeam seats
Free100 / month10 / minute0
Solo2,000 / month60 / minute0
Team10,000 / month200 / minute5
Pro50,000 / month600 / minute25
PlanPriceMonthly callsTeam seats
Free$01000
Solo$9/mo2,0000
Team$29/mo10,0005
Pro$79/mo50,00025

Billed via Dodo Payments (merchant-of-record — VAT/GST handled by Dodo). Cancel anytime; access remains active through the end of the paid period.

Data sources

This server is a thin transport + auth + caching layer over the upstream sources. Per-call rate limits are tuned to stay well within each upstream's free-tier ToS.

Privacy + GDPR

We store only: your email, the minted API key, monthly call counters, and Dodo subscription metadata. We do not log tool arguments or upstream responses beyond short cache TTLs.

Architecture

  • Runtime: Cloudflare Workers (V8 isolates, global edge).
  • Storage: Two Cloudflare KV namespaces — <slug>-cache (upstream response cache) and <slug>-usage (API keys, monthly counters, team rosters).
  • Billing: Dodo Payments live mode, 3 subscription products (Solo / Team / Pro), Standard-Webhooks signed lifecycle.
  • Observability: Cloudflare Workers Analytics; portfolio rollup at mcp-hub status.
  • Source: TypeScript, Vitest-tested, wrangler deploy-able. See src/ in this repo.

License

MIT — see LICENSE.

Author

Prakhar Gupta

Status

Install via npm (one-liner)

A thin launcher is published as @insnapsprakhar/fda-approvals-mcp on npm. No manual URL to copy/paste:

bash
npx -y @insnapsprakhar/fda-approvals-mcp

Or wire it into your MCP client:

jsonc
{  "mcpServers": {    "fda-approvals": {      "command": "npx",      "args": ["-y", "@insnapsprakhar/fda-approvals-mcp"]    }  }}

The npm package is just a launcher — it shells out to mcp-remote and points it at the hosted endpoint (https://fda-approvals-mcp.atlasword.workers.dev/mcp).

Source: README.md at commit 73940ca

Tools

4

fda_drug_label

Fetch the FDA-approved drug label for a brand or generic name. Includes indications, dosage, contraindications, warnings, adverse reactions.

Parametersdrug_namerequired

fda_adverse_events

Aggregate FDA adverse-event reports (FAERS) for a drug. Deduplicates by safetyreportid (bug fixed in 0.2.1). Returns total reports, unique reaction count, and top 20 reactions by frequency in the requested window.

Parametersdrugrequiredlimitdate_todate_from

Version history

1
  1. v0.3.1LatestSep 16, 2026

Score

90% 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.