Fda Approvals Mcp

Name: Fda Approvals Mcp
Author: guptaprakhariitr

by guptaprakhariitrcommunityv0.3.1

Hosted MCP server over openFDA that lets clients search FDA drug approvals, retrieve drug labels, query recalls, aggregate FAERS adverse events, search 510(k) device clearances, and view drug shortages. It acts as a thin transport, auth, and caching layer over FDA data sources.

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

GitHub Repository Website

Install & configure

Prerequisites

required
Install Node.js and npm
Required to run the MCP launcher via npx.
https://nodejs.org/
optional
Get an API key (optional for free tier, required for paid tiers and higher limits)
Create or purchase an API key from the hosted service if you want authenticated access, higher limits, or Team+/Pro features. Anonymous access is available for the free tier with 100 calls/month/IP.
https://fda-approvals-mcp.atlasword.workers.dev/upgrade?tier=solo

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `fda-approvals-mcp` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Install Node.js and npm** — Required to run the MCP launcher via npx. (https://nodejs.org/)

Optional prerequisites:
- Get an API key (optional for free tier, required for paid tiers and higher limits) — Create or purchase an API key from the hosted service if you want authenticated access, higher limits, or Team+/Pro features. Anonymous access is available for the free tier with 100 calls/month/IP. (https://fda-approvals-mcp.atlasword.workers.dev/upgrade?tier=solo)

Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","@insnapsprakhar/fda-approvals-mcp"]

Note: The README offers two portable paths: a direct mcp-remote invocation with the hosted HTTP MCP endpoint and Authorization header, and a simpler npm launcher package. Per the README, the npm package is a thin launcher around mcp-remote and is the simplest install path, so it is preferred. Anonymous free-tier access is supported, so no environment variables are required for the default launcher path. If a client supports only explicit remote wrapping, the equivalent command is: npx -y mcp-remote https://fda-approvals-mcp.atlasword.workers.dev/mcp --header "Authorization: Bearer <your-api-key>".

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: The README offers two portable paths: a direct mcp-remote invocation with the hosted HTTP MCP endpoint and Authorization header, and a simpler npm launcher package. Per the README, the npm package is a thin launcher around mcp-remote and is the simplest install path, so it is preferred. Anonymous free-tier access is supported, so no environment variables are required for the default launcher path. If a client supports only explicit remote wrapping, the equivalent command is: npx -y mcp-remote https://fda-approvals-mcp.atlasword.workers.dev/mcp --header "Authorization: Bearer <your-api-key>".