fda-inspections
No liveness check has reached it yet; it has been in the index since 9 Oct 2026. How this is checked
Fda Inspections is an HTTP JSON-RPC MCP server exposing tools for searching FDA inspection outcomes, Form 483 observations, compliance actions, and import refusals. It provides FDA-regulated establishment and enforcement data for developers and AI agents.
Inferred · not functionally tested
Overview
6 featuresPurpose: Finding and querying FDA inspection, Form 483, compliance action, and import refusal data programmatically.
Inferred · not functionally tested
Audience: developers and AI agent builders working with FDA regulatory data
Inferred · not functionally tested
Functions: data_extraction
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: unknown · Self-hosting: unknown
Recorded constraints: pricing: unknown · license: Proprietary · platforms: WEB · deployment: browser, api_only, cloud_managed
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: gateway.pipeworx.io. These links do not verify the individual claims.
In the API design, testing & docs space, fda-inspections takes a focused approach. Inferred · not functionally tested: It focuses on finding and querying FDA inspection, Form 483, compliance action, and import refusal data programmatically. Inferred · not functionally tested: fda-inspections is a B2B product aimed at developers and AI agent builders working with FDA regulatory data. Basis unknown · not verified: It ships for the web and API.
Pipeworx builds and maintains fda-inspections. Inferred · not functionally tested: Key capabilities include inspection search, form 483 citations, and compliance actions. Inferred · not functionally tested: Catalogued interfaces include an MCP server.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Inspection search
- Form 483 citations
- Compliance actions
- Import refusals
- Firm search
- Date filtering
Topics: Inferred · not functionally tested
Built with & integrations
- Cloudflare
- cf-ray header
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed9 Oct · 21:01 UTCFda Inspections seen via MCP Registry (official)Source: MCP Registry (official) · Open
Frequently asked questions about fda-inspections
- What is fda-inspections?
- Inferred · not functionally tested: Fda-inspections focuses on finding and querying FDA inspection, Form 483, compliance action, and import refusal data programmatically. It is catalogued under API design, testing & docs on PulseGate.
- Who should use fda-inspections?
- Inferred · not functionally tested: fda-inspections is a B2B product built for developers and AI agent builders working with FDA regulatory data.
- What platforms does fda-inspections run on?
- Basis unknown · not verified: fda-inspections runs on the web and API.
- Is fda-inspections still maintained?
- Unverified. fda-inspections has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
- What projects are similar to fda-inspections?
- Similar projects tracked by PulseGate include fda-devices, fda-regulations, and veterinary-fda.fda-devicesfda-regulationsveterinary-fda
- Who makes fda-inspections?
- fda-inspections is developed by Pipeworx.
- Does fda-inspections have an API or integrations?
- Inferred · not functionally tested: Yes — fda-inspections exposes an MCP server.
Similar projects
Closest matches by what these projects do