Health Api
Prototype lab-result interpretation, biomarker scoring, and health narratives inside an agent without building a clinical ML stack from scratch.
Overview
health-api is an MCP server for the Validate phase that connects agents to E-Labus clinical AI for lab analysis and biomarker scoring.
What is this MCP server?
- stdio MCP package @e-labus/mcp (v1.0.6) for clinical-style lab analysis workflows
- Biomarker scoring, health narratives, and risk-oriented insights via E-Labus backend
- Requires ELABUS_API_KEY (elab_sk_…); free key from developers.e-labus.com
- Agent-facing clinical AI layer—analysis and scoring, not a general CRUD health database
- npm registry transport with secret API key env var documented in server schema
- Server schema version 1.0.6
- npm package identifier @e-labus/mcp
- Required secret: ELABUS_API_KEY
What problem does it solve?
Health-app founders cannot quickly test credible lab narratives and biomarker logic inside their agent workflow without a specialized medical AI backend.
Who is it for?
Solo builders validating a health, wellness, or lab-report feature who want agent-callable clinical AI during prototyping.
Skip if: General B2B SaaS with no lab data, or teams that need full regulatory sign-off without any third-party clinical API.
What do I get? / Deliverables
After you add the MCP server and ELABUS_API_KEY, agents can generate lab analyses and health narratives on sample data so you can judge fit before building custom clinical pipelines.
- Agent-callable lab analysis and biomarker scoring via MCP
- Draft health narratives and risk-style insight outputs for UX review
- Documented dependency on E-Labus API for prototype scope decisions
Recommended MCP Servers
Journey fit
Health API fits Validate when you are proving whether AI-driven lab insights belong in a wellness or clinical-adjacent product before a full Build. Prototype is the shelf: you call E-Labus through MCP to demo narratives and risk-style outputs on sample labs, not to harden production compliance alone.
How it compares
Clinical analysis MCP integration, not a FHIR database connector or generic OpenAPI wrapper skill.
Common Questions / FAQ
Who is health-api for?
Builders prototyping health or lab-interpretation products who want MCP-accessible clinical AI from E-Labus.
When should I use health-api?
Use it while validating scope—demoing biomarker scoring and narratives on test labs before you invest in custom medical logic.
How do I add health-api to my agent?
Register the @e-labus/mcp stdio server in your MCP config and set the required secret ELABUS_API_KEY from developers.e-labus.com.