drug_patent_challenge_profile
Pack: fda-drug-competition · Endpoint: https://gateway.pipeworx.io/fda-drug-competition/mcp
How exposed is one brand drug’s patent protection, in a single call. Joins the three sources a generics or biotech analyst otherwise queries by hand: FDA Orange Book listed patents and their expiry dates, USPTO PTAB proceedings (IPR/PGR) filed against those exact patent numbers, and federal ANDA / Hatch-Waxman district-court dockets naming the brand. Returns the earliest expiry NOT under challenge, which patents are actively contested, and which generic firms are litigating. Use for loss-of-exclusivity diligence, generic-entry timing, or “who is attacking this drug and where”. Listed dates are FDA/USPTO/court records, not a legal conclusion about enforceability or actual launch.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
drug | string | yes | Brand or ingredient name, e.g. “Eliquis” or “apixaban”. |
application_no | string | no | Specific NDA/ANDA number instead of a name, e.g. “202155”. |
years | number | no | Docket lookback window in years (default 10). |
max_patents | number | no | Patents to check against PTAB (default 12, max 25). Each is one upstream call, so this bounds latency; any patents beyond the cap are still listed and counted. |
Example call
Arguments
{
"drug": "Eliquis"
}
curl
curl -X POST https://gateway.pipeworx.io/fda-drug-competition/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"drug_patent_challenge_profile","arguments":{"drug":"Eliquis"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('drug_patent_challenge_profile', {
"drug": "Eliquis"
});
More examples
{
"drug": "apixaban",
"years": 10,
"max_patents": 12
}
Connect
Add this to your MCP client config, or use one-click install buttons:
{
"mcpServers": {
"fda-drug-competition": {
"url": "https://gateway.pipeworx.io/fda-drug-competition/mcp"
}
}
}
See Getting Started for client-specific install steps.