Track FDA Enforcement Actions with MCP

FDA enforcement actions — recalls, seizures, injunctions — are the highest-signal events in regulatory monitoring. A single Class I recall can halt distribution, trigger investor concern, and cascade through supply chains. FDA Data MCP provides three complementary tools for tracking enforcement, each covering a different data source.

Three enforcement tools, three data sources

FDA publishes enforcement data in separate datasets. Each tool queries a different one:

• fda_search_enforcement — the primary openFDA enforcement dataset, covering both drug and device recalls across all classifications.
• fda_device_recalls — device-specific recall data from the CDRH recall database, often with additional device-level detail.
• fda_ires_enforcement — the iRES (Inspection, Recall, and Enforcement System) dataset, providing a third perspective on enforcement actions.

Search enforcement by company

fda_search_enforcement({ "company": "Pfizer" })

Sample response:

{
  "results": [
    {
      "recall_number": "D-0591-2025",
      "classification": "Class II",
      "status": "Ongoing",
      "report_date": "2025-01-15",
      "recalling_firm": "Pfizer Inc",
      "reason_for_recall": "Labeling: Label Mixup",
      "product_description": "Eliquis (apixaban) Tablets, 5 mg, ...",
      "product_type": "Drugs"
    },
    ...
  ],
  "pagination": { "offset": 0, "limit": 25, "total": 187 }
}

Understanding classification

The classification field in enforcement results indicates severity:

• Class I — most serious, reasonable probability of adverse health consequences or death
• Class II — may cause temporary or reversible adverse health consequences
• Class III — unlikely to cause adverse health consequences

For monitoring, filter on Class I and Class II. Class III recalls are typically labeling corrections or minor issues.

Device-specific recalls

fda_device_recalls({ "recalling_firm": "Pfizer" })

This tool queries a device-specific dataset and can return additional fields like product_code and root_cause_description that may not appear in the general enforcement dataset.

iRES enforcement

fda_ires_enforcement({ "company": "Pfizer" })

The iRES dataset provides yet another view. For thorough monitoring, query all three tools — they overlap but are not identical, and each may surface records the others miss.

Monitoring workflow

1. Run all three enforcement tools periodically for your target companies.
2. Deduplicate by recall_number where available.
3. Alert on Class I and Class II recalls immediately.
4. Use fda_recall_facility_trace to link recalls to specific facilities.
5. Cross-reference with fda_get_facility to assess facility-level impact.