pharma_resolve_drug

Pack: pharma-intel · 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/pharma_resolve_drug for the schema, then POST the same URL with its arguments for the data.

Turn one drug name into every identifier the other pharma tools need: RxNorm RxCUI for the brand and the ingredient, FDA application numbers (NDA from the Orange Book, BLA from the Purple Book) with the sponsor on each, the DailyMed setid of the current prescribing label, the marketer’s SEC CIK and ticker when it is a listed filer, the count of registered ClinicalTrials.gov studies, and the ChEMBL molecule id. Call this first when a name has to travel between regulatory, clinical, chemical, and financial sources. Every system is asked in parallel and each answer is returned with the ones that had no record left null and listed, so a gap is visible as a gap.

Parameters

Example call

Arguments

{
  "name": "Humira"
}

curl

curl -X POST https://gateway.pipeworx.io/pharma-intel/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"pharma_resolve_drug","arguments":{"name":"Humira"}}}'

TypeScript (@pipeworx/sdk)

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

const result = await pipeworx.call('pharma_resolve_drug', {
  "name": "Humira"
});

More examples

{
  "name": "Keytruda"
}

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"
    }
  }
}

{
  "mcpServers": {
    "pharma-intel": {
      "url": "https://gateway.pipeworx.io/pharma-intel/mcp"
    }
  }
}

See Getting Started for client-specific install steps.