Chia Health MCP Server
Licensed US telehealth — GLP-1 medications, intake, consents, Stripe ACP. HIPAA-compliant, 30 tools.
https://mcp.chia.healthCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- doctormcp
- Version
- 1.26.0
- Capability keys
- experimental, prompts, resources, tools
- Tool names
- auth_start, auth_verify_otp, auth_resend_otp, auth_check_payment, medications_list, medications_details, medications_availability, medications_pricing, medications_categories, eligibility_check, intake_questions, intake_submit, intake_status, consent_list, consent_text, consent_submit, consent_status, order_create, order_status, order_documents, order_upload, checkout_create, checkout_update, checkout_complete, checkout_status, checkout_cancel, portal_log_weight, portal_log_side_effects, portal_message, portal_care_plan, portal_refill, portal_support, provider_questions, provider_respond
Chia Health telehealth prescription platform. Patients can browse medications, check eligibility, complete intake questionnaires, sign consents, order medications, pay via Stripe ACP, and manage their treatment through the patient portal. All prescriptions require evaluation by a licensed US healthcare provider. ## How to talk to the patient - Progressive disclosure: ask ONE section at a time, not the whole questionnaire. Wait for the patient's reply before moving on. Never dump a long list of demographic, lifestyle, and medical-history questions at once — that's the fastest way to lose them. - Prefer quiz-style choice questions over open text. Every `select` / `multi_select` question in `intake_questions` ships with the exact options the provider expects — present those options verbatim as a short pick-list so the patient just picks one. Reserve free-text follow-ups for conditional `*_details` fields. - Start with the easiest, most engaging questions (goals, lifestyle, preference
Reported Aug 17, 2026, 05:03 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 301ms
- respondsMCP initialize · 8s limit · HTTP 200 · 360ms
- respondsMCP initialize · 8s limit · HTTP 200 · 179ms
- respondsMCP initialize · 8s limit · HTTP 200 · 361ms