Skip to main content
Glama
Black-Swan-Causal-Labs

com.blackswancausallabs/openfda-mcp

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OPENFDA_API_KEYNoAPI key for openFDA. Optional; without it, requests are rate-limited to 40/min and 1,000/day.

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_drug_labelB

Search openFDA drug labels (SPL) for a term.

lookup_drugsfda_applicationB

Fetch Drugs@FDA application metadata for an NDA/BLA/ANDA number.

resolve_drug_to_applicationA

Resolve a brand or generic drug name to its NDA/BLA application number(s).

Bridges drug-name-only sources (registry inventories, product lists) to FDA regulatory metadata. Searches the brand and generic name fields directly rather than label prose, so another product merely mentioning this drug does not produce a false match.

screen_for_rwe_signalsA

EXPERIMENTAL. Sweep drug labels for registry / real-world-evidence signals.

Searches the label corpus for terms suggesting registry, natural-history or other real-world evidence, then aggregates hits by application number with snippets showing where each term matched.

This tool is unvalidated and has a known false-positive problem. It has no ground-truth oracle, and below the strongest hits the results are dominated by applications whose labels use "registry" in an unrelated sense. Its output is a candidate list for human review — not a finding, and not a count you should report.

lookup_device_submissionA

Look up a CDRH device submission by its number.

Handles all four device pathways: 510(k) K-numbers ("K203571"), De Novo grants ("DEN160026" — stored in the 510(k) endpoint, not a separate one), PMA P-numbers ("P230044"), and HDE H-numbers. Supplement suffixes ("P230044/S001") are stripped before lookup.

classify_device_product_codeB

Resolve a CDRH product code to its device class and medical specialty.

validate_device_applicationA

Validate a device number and derive class, specialty and category in one call.

Chains lookup_device_submission -> classify_device_product_code, which is the full three-hop resolution: number -> product_code -> classification.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Black-Swan-Causal-Labs/openfda-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server