Let AI agents
understand
Taiwan healthcare.
Open-source MCP server for FHIR Box, TW Core IG and Taiwan terminology. Free for dev, hosted for prod.
63 tools · TW Core / TW NHI PAS · TFDA drugs · ICD-10 / SNOMED / LOINC / RxNorm · MIT · Passed Taiwan Connectathon 2026
From MCP handshake to clinical answers in seconds.
Taiwan Health MCP follows the Model Context Protocol — the same standard used by Claude, ChatGPT, and dozens of agent frameworks. No custom SDK, no proprietary format.
Connect your LLM client
Add the MCP endpoint to Claude Desktop, ChatGPT, or any MCP-compatible agent. The handshake negotiates all 63 tools automatically.
Browse the tool catalog
Your AI assistant discovers every tool by name and schema — from ICD-10 code search to TFDA pill identification to FHIR R4 validation.
Query in natural language
Describe what you need: "Identify this pill based on its imprint" or "Find all LOINC codes for HbA1c." The LLM picks the right tool and returns structured results.
Scale freely
Deploy via Docker for on-premise use, or connect to the managed endpoint. MIT licensed — fork and customize freely.
One MCP endpoint. Every Taiwan healthcare dataset your LLM needs.
Taiwan Health MCP unifies TFDA drug records, FHIR R4 profiles, ICD-10 / LOINC / SNOMED CT terminologies, and curated Taiwan clinical content behind the official Model Context Protocol — ready to plug into Claude, ChatGPT, or any agent runtime.
12 tool groups · 63 tools
FHIR Box connection
Register a hospital FHIR Box or any FHIR R4 server once; agents can then list, read and — with an allow-list and confirm_write=true — write resources.
Docs ↗TW Core validation & grounding
Multi-IG profiles and ValueSets, skeleton-fill authoring, validation aligned with HL7 validator_cli 7.0.1, plus deterministic (non-LLM) checks that a resource stays faithful to the source note.
Docs ↗Taiwan drugs & nutrition
TFDA drug licences with package-insert OCR and pill identification by imprint, colour and shape, plus Taiwan FDA health foods and food composition data.
Docs ↗International terminology
ICD-10-CM / PCS (CMS 2026-04-01), SNOMED CT International, LOINC 2.80 and RxNorm: code search, cross-terminology mapping and lab interpretation against reference ranges.
Docs ↗Clinical calculators
CHA₂DS₂-VASc, Wells PE / DVT, HAS-BLED, CURB-65, qSOFA, GCS, eGFR, DAS28, CDAI and BMI with Taiwan (Asian) cut-offs — deterministic, no LLM arithmetic.
Docs ↗Semantic search
Hybrid search over pgvector embeddings (Ollama qwen3-embedding by default) for ICD-10, LOINC and SNOMED CT; falls back to keyword search when embeddings are missing.
Docs ↗Connect Taiwan Health MCP
Add Taiwan healthcare data to any MCP-compatible LLM client.
- 1Open Claude Desktop
- 2Add the MCP endpoint to your config
- 3Restart Claude — tools appear automatically
Seamless MCP Integration for Clinical AI
Compatible with Claude Desktop, ChatGPT, and any MCP-enabled AI assistant.
Taiwan-Localized & International
Covers TFDA drug database (外觀/仿單/OCR), health supplements, food nutrition and clinical calculators — alongside ICD-10-CM/PCS (CMS 2026-04-01), SNOMED CT, LOINC 2.80 and RxNorm.
Production-Grade Infrastructure
PostgreSQL 16 with pgvector for semantic / hybrid search via Ollama embeddings, with Redis for real-time admin events and MinIO for pill images and leaflets.
Dual Interface: MCP + OpenAPI
Every tool is available natively through MCP (port /mcp) and as a RESTful OpenAPI endpoint at /tools/<name> for non-MCP integrations.
Every LLM Deserves Quality Clinical Data
Taiwan Health MCP treats AI agents as first-class citizens. Every tool is documented and typed — so any MCP-compatible LLM can discover, reason over, and combine Taiwan healthcare datasets autonomously.
Browse the Tool CatalogFree. Open source. No lock-in.
No API keys. No paywalls. No rate limits. MIT licensed — self-host with Docker, or try the public endpoint first.
MIT Licensed
Full source on GitHub. Fork it, modify it, deploy it — no strings attached.
Self-Host Ready
Run the entire server on your own infrastructure with Docker. Your data stays local.
Community Driven
Open issues, discussions, and contributions welcome. No vendor lock-in, ever.
Three ways to run it. One set of tools.
Use our hosted endpoint, run it in your own cloud, or keep everything inside the hospital network.
Hosted (we run it)
We operate Taiwan Health MCP for you — data loading and updates, upgrades and an authenticated endpoint — so you only point your AI client at it.
Self-hosted (your cloud or data centre)
git clone, then docker compose up -d: one nginx gateway (:8080) serves both MCP and OpenAPI, with PostgreSQL 16 + pgvector, Redis and MinIO in the same compose file. MIT-licensed, no usage limits.
Offline, on-premises hospital
No cloud dependency: upload terminology source files and FHIR IG packages (package.tgz) through the admin console, run semantic search on a local Ollama model, and register the hospital's own FHIR Box.
Authentication that matches the environment.
No tier stores patient data: audit records keep only the tool name and a SHA-256 hash of its parameters, never the raw values.
Community public endpoint / self-host default
No authServes only public terminology and drug data, no PHI — suited to development, testing and trusted internal networks.
Self-hosted, publicly exposed
Bearer tokenSet PUBLIC_TOOLS_AUTH_MODE=bearer and /mcp, /openapi.json and /tools/* all require Authorization: Bearer <token>; CORS origins may not include *.
Hosted and Enterprise
OAuth / SSOIntegrates with your organisation's identity provider, with access control and audit logs, for production and hospital deployments.
Free for dev, hosted for prod.
The open-source Community edition stays free. Hosted and Enterprise are for teams that would rather not run it themselves.
Community
Free
Forever
- MIT licence
- All 63 tools
- Self-host with no usage limits
- Community support on GitHub Issues
Hosted
Coming soon
Monthly subscription
- Operated and updated by us
- Authenticated production endpoint
- Data versions kept current
- No servers to run
Enterprise
Contact us
Quoted per deployment
- OAuth / SSO integration
- Audit logs and access control
- On-premises hospital rollout
- Technical support
Open-source. Production-ready. Taiwan-first.
Taiwan Health MCP is built for healthcare developers, clinical informaticists, and AI application builders who need structured Taiwanese and international medical data via LLM-compatible tooling.
This service is provided for development and research purposes. Always validate AI-generated clinical outputs before deploying to production environments.