fda_faers_signal_summary
Pack: openfda · Endpoint: https://gateway.pipeworx.io/openfda/mcp
Calculate report-level FAERS disproportionality routing metrics for one drug/reaction pair using a 2×2 reporting table. The reaction argument matches one whole MedDRA preferred term, so a broad word like “neuropathy” counts only reports filed under that exact term and not the specific terms containing it. Natural multi-word phrasing is resolved to MedDRA word order and disclosed; a term matching nothing is reported as unresolved rather than as zero reports. ROR/PRR are screening statistics—not incidence, causality, comparative drug safety, or an FDA safety conclusion.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
drug | string | yes | Brand or generic drug name. |
reaction | string | yes | MedDRA preferred term, matched whole rather than as a substring. Natural English word order is accepted and corrected (“ischaemic optic neuropathy” resolves to “OPTIC ISCHAEMIC NEUROPATHY”). |
from_date | string | no | Optional YYYY-MM-DD. |
to_date | string | no | Optional YYYY-MM-DD. |
Example call
Arguments
{
"drug": "semaglutide",
"reaction": "ischaemic optic neuropathy"
}
curl
curl -X POST https://gateway.pipeworx.io/openfda/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"fda_faers_signal_summary","arguments":{"drug":"semaglutide","reaction":"ischaemic optic neuropathy"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('fda_faers_signal_summary', {
"drug": "semaglutide",
"reaction": "ischaemic optic neuropathy"
});
More examples
{
"drug": "Ozempic",
"reaction": "Nausea",
"from_date": "2025-01-01",
"to_date": "2025-12-31"
}
Connect
Add this to your MCP client config, or use one-click install buttons:
{
"mcpServers": {
"openfda": {
"url": "https://gateway.pipeworx.io/openfda/mcp"
}
}
}
See Getting Started for client-specific install steps.