MCP (Model Context Protocol) server for the telehealth prescription platform. Enables AI assistants (ChatGPT, Claude, Gemini, OpenClaw, Copilot, and custom agents) to help patients browse medications, complete medical intake, sign consent documents, place orders, pay, and manage their treatment — all through natural conversation.
Available treatments include GLP-1 medications (semaglutide, tirzepatide including tablets), peptide therapies (sermorelin, NAD+, glutathione), and longevity programs. All prescriptions are evaluated by licensed US healthcare providers and delivered from FDA-regulated 503A compounding pharmacies across all 50 US states + DC.
Getting Started
doctormcp is a remote MCP server — connect over the network, no local installation required.
Server URL:https://mcp.chia.health/Transport: Streamable HTTP
Metadata:https://mcp.chia.health/server.json
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
Any MCP client that supports streamable HTTP transport can connect:
Server URL:https://mcp.chia.health/
Transport: Streamable HTTP
Server metadata:https://mcp.chia.health/server.json
Verify Connection
Once connected, your AI assistant can immediately call these public tools (no auth required):
medications.categories → medication categories
medications.list → all medications with pricing
medications.availability → check if a medication ships to your state
eligibility.check → pre-screen age, state, BMI
Provider — answer follow-up questions from your provider
2
Guest
* Auth tools use session_id (no token) except auth.check_payment which uses a bearer token.
Important: All prescriptions are evaluated and approved by licensed US healthcare providers. doctormcp facilitates the patient workflow — it does not make clinical decisions.
Authentication
Patients can browse freely without authentication — discovery, eligibility, and intake question preview are all public.
When the patient is ready to proceed with their medical intake, they verify their email:
auth.start(email, phone, name) → sends OTP to email, returns session_id
The guest token enables intake, consent, ordering, and checkout. After payment, auth.check_payment upgrades the token to full scope for portal access (care plan, messaging, refills).
Tool Catalog
Auth
Tool
Auth
Description
auth.start
No
Send OTP to patient's email, get session_id
auth.verify_otp
No
Verify code, get guest-scoped bearer token
auth.resend_otp
No
Resend OTP if expired or not received
auth.check_payment
Guest
Poll for payment, upgrade token to full scope
Discovery (public, no auth)
Tool
Description
medications.list
List all medications with categories, forms, and pricing
medications.details
Detailed info for a specific medication (plans, pricing, what's included)
medications.availability
Check if a medication ships to a given state
medications.pricing
Price breakdown for a specific medication/form/plan combo
medications.categories
List medication categories (Weight Loss, Peptides, Anti-Aging, etc.)
Qualification (public + guest)
Tool
Auth
Description
eligibility.check
No
Pre-screen age, state, BMI, and medical conditions
intake.questions
No
Get the structured intake questionnaire for a medication
intake.submit
Guest
Submit completed intake for provider review
intake.status
Guest
Check intake review status (under review, approved, denied)
Consent (guest token required)
Tool
Description
consent.list
List all 5 consent documents needed for an intake
consent.text
Get full verbatim text of a consent document
consent.submit
Record patient's consent confirmation with audit trail
consent.status
Check which consents are complete/pending
Ordering (guest token required)
Tool
Description
order.create
Create a medication order (requires all consents complete)
order.status
Check order status and tracking info
order.documents
List required ID documents for an order
order.upload
Upload photo ID or selfie for identity verification
Checkout (guest token required)
Tool
Description
checkout.create
Create checkout; returns authenticated payment link (magic-link URL)
checkout.update
Update a pending checkout (promo codes, shipping)
checkout.complete
Complete payment with a Stripe Shared Payment Token (ACP path)
checkout.status
Poll payment status after sending a payment link (fallback path)
checkout.cancel
Cancel an in-progress checkout
Patient Portal (full token required — after payment)
Tool
Description
portal.log_weight
Log weight for progress tracking
portal.log_side_effects
Report side effects (severe = auto-flagged for provider)
portal.message
Send a message to the healthcare provider
portal.care_plan
Get current medication, dosing, and weight progress
Order Creation — order.create calculates the total and creates a pre-payment order record.
Checkout Initiation — checkout.create creates a Stripe PaymentIntent (for ACP) and generates an authenticated payment link. The link auto-authenticates patients in the browser and lands on the Chia Health checkout page. Also sent via email and SMS.
Payment Completion — Two paths:
ACP: checkout.complete accepts a Shared Payment Token (SPT) from the AI platform and confirms the PaymentIntent. Instant, in-conversation payment.
Fallback: The agent shares the payment_url (authenticated magic-link) with the patient. The patient opens it in their browser, auto-authenticates, and pays on the Chia Health checkout page. The agent polls auth.check_payment to detect completion.
Post-Payment — On success (either path), a Subscription and Enrollment are created automatically. auth.check_payment upgrades the agent's token to full scope for portal access.
HIPAA Compliance
Audit Logging — Every access to protected health information (PHI) is logged with actor identity, action type, resource, IP address, and timestamp. Logs are retained for 10 years.
Consent Records — All patient consent confirmations include verbatim confirmation text, method (AI agent conversational), platform, session ID, and IP address. Consent records are immutable.
Input Sanitization — All inputs are validated and sanitized. Control characters are stripped, lengths enforced, and domain-specific formats (email, state, phone, ZIP) are validated.
OTP-First Auth — Email ownership verified via 6-digit OTP before any patient data access. SHA-256 hashed tokens with scoped access (guest/full). No token issued without email verification.
Rate Limiting — Redis-backed token-bucket rate limiting per user and endpoint category (public: 100/min, auth: 5/min, authenticated: 30/min, consent: 10/min, checkout: 5/min).
Minimal Data Exposure — Tools return only the data needed for the current step. Sensitive fields (payment details, full SSN) are never returned.
Henüz araç listesi yok. Uzak sunucular ilk sağlık kontrolünden sonra bir liste alır.
SSS
Sorular
Chia Health MCP Server nasıl kurulur?
Bu sayfadan Cursor, Claude Desktop, Claude Code veya VS Code için http yapılandırmasını kopyalayın. PlugMCP proxy'sini değil, yayıncının kurulumunu kullanır.
Chia Health MCP Server için API anahtarı gerekiyor mu?
Bu kayıtta gerekli bir ortam değişkeni listelenmiyor.
Chia Health MCP Server hangi aktarımı kullanıyor?
Chia Health MCP Server sunucusuna HTTP üzerinden ulaşılır.
Chia Health MCP Server en son ne zaman kontrol edildi?
Son kontrol: 2026-11-08. Licensed US telehealth — GLP-1 medications, intake, consents, Stripe ACP. HIPAA-compliant, 30 tools.