OpenFDA API에서 약물 정보를 조회하기 위한 Model Context Protocol (MCP) 서버입니다.
브랜드명으로 약물 라벨 정보 검색
일반명(유효 성분)으로 약물 정보 검색
특정 일반 의약품의 모든 브랜드 버전 조회
약물에 대한 이상 반응(부작용) 보고서 조회 (브랜드명 또는 일반명 기준)
특정 제약사가 제조한 모든 약물 검색
포괄적인 약물 안전 정보 조회 (경고, 금기 사항, 상호 작용, 주의 사항 등)
NDC(National Drug Code) 형식 정규화 및 유효성 검사
쿼리 실패 시 유용한 오류 메시지 및 제안 제공
OpenFDA API 키 설정
이 MCP 서버는 OpenFDA API에 액세스하기 위해 OpenFDA API 키가 필요합니다.
프로젝트 루트에 .env 파일을 생성하고 다음 줄을 추가하세요:
OPENFDA_API_KEY=your_openfda_api_key_here참고: 실제 API 키를 버전 관리 시스템에 커밋하지 마십시오.
OpenFDA API 키 등록에서 API 키를 얻을 수 있습니다.
MCP 서버 구성 예시
이 서버를 더 큰 MCP 시스템과 통합하는 경우 구성은 다음과 같을 수 있습니다:
{
"mcpServers": {
"openfda": {
"command": "npx",
"args": [
"@ythalorossy/openfda"
],
"env": {
"OPENFDA_API_KEY": "*****************************************"
},
"timeout": 60000,
"autoApprove": [
"get-drug-by-name",
"get-drug-by-generic-name",
"get-drug-adverse-events",
"get-drugs-by-manufacturer",
"get-drug-safety-info",
"get-drug-by-ndc",
"get-drug-by-product-ndc"
]
}
}
}별표를 실제 API 키로 바꾸거나 .env 파일에서 로드되도록 하십시오.
Related MCP server: drugbank-mcp-server
git clone https://github.com/ythalorossy/openfda.git
cd openfda
npm install
npm run build그런 다음 서버를 시작합니다:
node bin/index.js또는 npx를 사용하여 직접 사용하세요:
npx @ythalorossy/openfda필요한 환경 변수를 위해 .env 파일을 생성하세요.
MIT
Get adverse event reports for a drug. This provides safety information about reported side effects and reactions. Use brand name or generic name.
Inputs: drugName (required), limit, seriousness.
Get drug information by generic (active ingredient) name. Useful when you know the generic name but not the brand name. Returns all brand versions of the generic drug.
Inputs: genericName (required), limit.
Get drug by name. Use this tool to get the drug information by name. The drug name should be the brand name. It returns the brand name, generic name, manufacturer name, product NDC, product type, route, substance name, indications and usage, warnings, do not use, ask doctor, ask doctor or pharmacist, stop use, pregnancy or breast feeding.
Inputs: drugName (required).
Get drug information by National Drug Code (NDC). Accepts both product NDC (XXXXX-XXXX) and package NDC (XXXXX-XXXX-XX) formats. Also accepts NDC codes without dashes.
Inputs: ndcCode (required).
Get drug information by product NDC only (XXXXX-XXXX format). This ignores package variations and finds all packages for a product.
Inputs: productNDC (required).
Get comprehensive safety information for a drug including warnings, contraindications, drug interactions, and precautions. Use brand name.
Inputs: drugName (required).
Get all drugs manufactured by a specific company. Useful for finding alternatives or checking manufacturer portfolios.
Inputs: manufacturerName (required), limit.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 7 tools
The tools have overlapping purposes that could cause confusion, particularly between get-drug-by-name, get-drug-by-generic-name, and get-drug-by-ndc, which all retrieve drug information but with different input parameters. Descriptions help clarify the distinctions, but an agent might misselect when the query is ambiguous about whether to use brand name, generic name, or NDC. The safety-focused tools (get-drug-adverse-events and get-drug-safety-info) are more distinct, but overall there is moderate overlap in the information retrieval tools.
All tool names follow a consistent verb_noun pattern with hyphens, specifically 'get-drug-by-X' or 'get-drug-X', where X is a specific attribute like name, ndc, or safety-info. This predictability makes it easy for an agent to understand the naming convention and infer tool purposes. There are no deviations in style, such as mixing camelCase or snake_case, ensuring high readability and consistency throughout the set.
With 7 tools, the server is well-scoped for its domain of drug information retrieval from OpenFDA. Each tool serves a distinct purpose, such as looking up drugs by different identifiers or accessing safety data, and none appear redundant or unnecessary. This count is typical for a focused API server, providing enough functionality without being overwhelming or too sparse, making it appropriate for the server's purpose.
The tool set covers the core domain of drug information retrieval comprehensively, including lookups by brand name, generic name, NDC, manufacturer, and safety data. Minor gaps exist, such as the lack of update or delete operations, but this is reasonable since OpenFDA is a read-only public database. Agents can work around these gaps, and the surface supports common queries without dead ends, though advanced features like filtering or pagination might be missing but are not essential for basic coverage.
DrugBank MCP — wraps the DrugBank Clinical API (api.drugbank.com)
RxNorm MCP — wraps the NLM RxNav REST API (free, no auth)
MCP server exposing supplements database used by iNutriPlan.com
MCP server for US nursing facility search and ownership lookup (NursingHomeDatabase).
