OpenFDA Regulatory Metadata vs Taiwan Health MCP
A side-by-side look at the OpenFDA Regulatory Metadata and Taiwan Health MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose OpenFDA Regulatory Metadata for biology & bioinformatics work as a local process; choose Taiwan Health MCP for biology & bioinformatics. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose OpenFDA Regulatory Metadata when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OPENFDA_API_KEY. - You want tools like
search_drug_label, lookup_drugsfda_application, resolve_drug_to_application.
Choose Taiwan Health MCP when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- Its auth model fits you: No auth required.
- You have the keys it needs:
POSTGRES_PASSWORD. - You want tools like
health_check, calculate_chads2_vasc, calculate_wells_pe.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 56/100 · Good | 60/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | OPENFDA_API_KEY | POSTGRES_PASSWORD |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 167 |
| Directory activity | 6 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 7 | 59 |
| Full listing | View OpenFDA Regulatory Metadata | View Taiwan Health MCP |
Tools & capabilities
OpenFDA Regulatory Metadata tools 7
search_drug_labelSearch openFDA drug labels (SPL) for a term.lookup_drugsfda_applicationFetch Drugs@FDA application metadata for an NDA/BLA/ANDA number.resolve_drug_to_applicationResolve 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_signalsEXPERIMENTAL. 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_submissionLook 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_codeResolve a CDRH product code to its device class and medical specialty.validate_device_applicationValidate 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.
Taiwan Health MCP tools 59
health_checkReturn runtime readiness of the MCP server and every module-backed service. Call this first before any workflow to confirm the required services are online.calculate_chads2_vascCHA₂DS₂-VASc stroke-risk score for non-valvular atrial fibrillation (0–9). Accepts raw age/sex and computes brackets internally; also returns the 2024 ESC CHA₂DS₂-VA adjusted score (sex removed). Decision support only.calculate_wells_peWells criteria for pulmonary embolism (two-tier + three-tier risk). Binary findings are booleans; heart_rate_bpm is raw and the >100 criterion is computed.calculate_wells_dvtWells criteria for deep-vein thrombosis (two-tier + three-tier risk). All items are binary clinical findings.calculate_das28DAS28 rheumatoid arthritis disease activity. formula=esr needs esr (mm/h); formula=crp needs crp (mg/L). Joint counts are 28-joint (0–28); global_health is a 0–100 VAS (not the 0–10 scale CDAI uses). Returns score and activity band (remission/low/moderate/high).calculate_cdaiCDAI (lab-free) rheumatoid arthritis disease activity (0–76). Tender and swollen counts use the 28-joint assessment (0–28 each); patient and provider global assessments are 0–10.calculate_bmiBody mass index with Taiwan (Asian) cutoffs: <18.5 underweight, 18.5–23.9 normal, 24–26.9 overweight, ≥27 obese. Height in cm (not metres), weight in kg.calculate_egfrEstimated glomerular filtration rate using the CKD-EPI 2021 creatinine equation (race-free), adults ≥18 only. serum_creatinine_mgdl in mg/dL (convert µmol/L by dividing by 88.4). Returns eGFR in mL/min/1.73m² and KDIGO CKD stage.calculate_has_bledHAS-BLED bleeding risk on oral anticoagulation (0–9). Accepts raw age (the >65 criterion is computed) and raw systolic BP (the H criterion is computed as SBP >160 mmHg). Returns score and high/low bleeding-risk category (≥3 high).calculate_curb65CURB-65 community-acquired pneumonia severity (0–5). BUN in mg/dL (threshold >19), respiratory rate ≥30, hypotension SBP<90 or DBP≤60, confusion, age ≥65.calculate_qsofaqSOFA sepsis screening (0–3): respiratory rate ≥22, altered mentation (GCS <15), systolic BP ≤100. ≥2 suggests sepsis and further evaluation.calculate_gcsGlasgow Coma Scale (3–15). eye_response 1–4, verbal_response 1–5, motor_response 1–6. Returns total, E/V/M sub-scores, and mild/moderate/severe severity (≤8 severe).- +47 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
OpenFDA Regulatory Metadata
{
"mcpServers": {
"openfda-regulatory-metadata": {
"command": "uvx",
"args": [
"openfda-mcp"
],
"env": {
"OPENFDA_API_KEY": "YOUR_OPENFDA_API_KEY_HERE"
}
}
}
}
Taiwan Health MCP
No confirmed install command for Taiwan Health MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
OpenFDA Regulatory Metadata is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Taiwan Health MCP belongs to Biology & Bioinformatics and uses an install path we have not confirmed yet. Pick OpenFDA Regulatory Metadata for biology & bioinformatics work and Taiwan Health MCP for biology & bioinformatics.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Taiwan Health MCP has no confirmed install command yet — follow its own setup instructions.
OpenFDA Regulatory Metadata has no declared pricing — check the project's own site. Taiwan Health MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add openfda-regulatory-metadata and taiwan-health-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, OpenFDA Regulatory Metadata has a quality signal of 56/100 (Good) with 6 views, 0 installs and 0 GitHub stars. Taiwan Health MCP has 60/100 (Good) with 1 views, 0 installs and 167 GitHub stars.