`fda_device_company_profile`

Pack: fda-devices · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/fda_device_company_profile for the schema, then POST the same URL with its arguments for the data.

Build a bounded FDA regulatory snapshot for one device company across 510(k), PMA, recalls, and MAUDE. Dataset name matching is imperfect and MAUDE counts are signals, not safety rates.

Parameters

Name	Type	Required	Description
`company`	string	yes	Company/manufacturer name.
`limit_per_dataset`	number	no	Rows per dataset (1-20, default 5).

Example call

Arguments

{
  "company": "Dexcom",
  "limit_per_dataset": 5
}

curl

curl -X POST https://gateway.pipeworx.io/fda-devices/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"fda_device_company_profile","arguments":{"company":"Dexcom","limit_per_dataset":5}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('fda_device_company_profile', {
  "company": "Dexcom",
  "limit_per_dataset": 5
});

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

Connect to just the fda-devices pack

{
  "mcpServers": {
    "fda-devices": {
      "url": "https://gateway.pipeworx.io/fda-devices/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

fda_device_company_profile