MCP.Market

Fda Inspections MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/fda-inspections·v0.2.1

FDA inspection outcomes, Form 483 observations, compliance actions and import refusals for drug…

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Fda Inspections yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Fda Inspections tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Fda Inspections compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
107 ms
faster than 82% of 30,031 servers

Release history: 4 versions in the registry since 2026-09-16, latest 2026-11-01, typically one every 8 days.

Install Fda Inspections in Claude Code, Cursor or VS Code

claude mcp add --transport http fda-inspections https://gateway.pipeworx.io/fda-inspections/mcp
Add to Cursor

What the publisher says

From the Fda Inspections repository's README, as published. We do not edit it. Read it on GitHub

fda-inspections

FDA inspection outcomes, Form 483 citations, compliance actions and import refusals, from the FDA Data Dashboard (Office of Inspections and Investigations).

Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.

This is not openFDA. openFDA carries drug/device adverse events, labels, recalls and warning letters. It does not carry inspection classifications, 483 observations, or border refusals — those live only in OII's own Data Dashboard, on a different host with a different credential.

Tools

Auth

The credential is a pair, not a single key:

Authorization-User: <the e-mail it was issued to>
Authorization-Key:  <the FDA-generated key>

Pass it as apiKey in the combined form "email:key" (split on the first colon). Platform secret: PLATFORMFDADASHBOARDKEY, same combined form, set on both the gateway and registry-api workers.

Credentials are free: create an account in the OII Unified Logon application at and request Data Dashboard API access. FDA mails the key to the address you register, and that address becomes the Authorization-User value. The platform credential is set, so callers need no key of their own.

Note that datadashboard.fda.gov serves a 403 to a default curl User-Agent — send a browser UA when reading the docs by hand. The API host (api-datadashboard.fda.gov) has no such restriction.

Request contract

Verified against the live endpoint rather than assumed — a malformed body returns 400 and names the offending field, a well-formed but unauthenticated one returns 401, which makes the shape testable without a credential.

InspectionEndDateTo. There is no top-level date-range parameter, and the bare date fieldname is rejected as a filter key.

  • POST https://api-datadashboard.fda.gov/v1/
  • Body: { start, rows, sort, sortorder, columns[], filters{} }
  • sort and sortorder are required, not optional.
  • start is 1-based.
  • rows maxes at 5000.
  • columns is required — omitting it 400s and names the missing field.
  • Filter values must be arrays — {"State": ["California"]}. A bare string 400s.
  • Date ranges use suffixed keys: InspectionEndDateFrom /

substring searches. State is the exception — see below.

  • Most string filters match LIKE %term% case-insensitively, so firm names are

Gotcha: State is exact, and a wrong one looks like "never inspected"

LegalName, FirmName and CountryName are case-insensitive substring matches. State is exact and case-sensitive against the spelled-out name. "CA", "Ca" and "CALIFORNIA" each return a clean 200 with resultcount: 0 — which reads as this site was never inspected rather than you passed the wrong argument. Only "California" returns data.

The pack normalizes postal codes and casing (normalizeState), so callers may pass either form. Foreign establishments carry State: null; filter those by country instead.

Gotcha: firm search is a substring, so it over-matches

firm: "Intas" also matches Cintas Corporation. fdafirmriskprofile returns every FEI it matched in matchedestablishments precisely so this is visible — read that list before quoting the aggregate counts, which are computed over all matched rows.

Gotcha: the name column is not uniform

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Fda Inspections: common questions

Is Fda Inspections MCP server safe?
Mostly: it is graded B (77/100). Read the Fda Inspections safety report
How do I install Fda Inspections?
It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Fda Inspections need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Fda Inspections maintained?
The last commit was 40 days ago (2026-09-24). The latest release is v0.2.1.
Is Fda Inspections up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Fda Inspections?
Servers from other publishers that do the same job: Auth0 MCP Server.
How does Fda Inspections compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 107 ms (faster than 82% of 30,031 servers). Full comparison.

Alternatives to Fda Inspections

Same job from other publishers: the closest match first, then the best rated.

  • Auth0 MCP Server
    Auth0 MCP Server: Manage Auth0 applications, APIs, actions, logs, and forms using natural language
    A

More from pipeworx-io →