# Chia Health MCP Server (remote · mcp.chia.health)

Licensed US telehealth — GLP-1 medications, intake, consents, Stripe ACP. HIPAA-compliant, 30 tools.

- Trust score: 71/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- remote · `mcp.chia.health`: 71/100 (this document), [markdown](https://verifymcp.io/servers/health-chia-chia-mcp/mcp.md), [page](https://verifymcp.io/servers/health-chia-chia-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.chia.health/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (auth_start).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 5231 tokens (~153/item across 34 items; 34 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http health-chia-chia-mcp https://mcp.chia.health/
```

### Codex

```toml
[mcp_servers.health-chia-chia-mcp]
url = "https://mcp.chia.health/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "health-chia-chia-mcp": {
      "type": "remote",
      "url": "https://mcp.chia.health/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add health-chia-chia-mcp --url https://mcp.chia.health/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  health-chia-chia-mcp:
    url: "https://mcp.chia.health/"
```

### Other

```json
{
  "mcpServers": {
    "health-chia-chia-mcp": {
      "type": "http",
      "url": "https://mcp.chia.health/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-04 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-03 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 66)

First indexed and scored.

## MCP tools (34)

### `auth_start` (~173 tokens)

Start Session

Start a patient session by providing their contact information. Sends a 6-digit verification code to the patient's email.

Returns a session_id (NOT a token). The session_id is used with auth_verify_otp to prove email ownership and get a bearer token.

The code is in the email subject line: 'Chia Health: Your code is XXXXXX'. If you have access to the patient's email (e.g. Gmail MCP), search for this subject.

No authentication required. Call this when the patient is ready to proceed with their medical intake — after browsing medications and checking eligibility.

Input parameters:

- `email` (string, required): Patient's email address
- `first_name` (string, required): Patient's first name
- `last_name` (string): Patient's last name
- `phone` (string, required): Patient's phone number (US format)

Output parameters:

- `result` (string)

### `auth_verify_otp` (~100 tokens)

Verify OTP Code

Verify the 6-digit code sent to the patient's email. Returns a guest-scope bearer token for intake, consent, order, and checkout tools.

Requires the session_id from auth_start — no email needed.

After checkout and payment, call auth_check_payment to upgrade the token to full scope for portal access.

Input parameters:

- `code` (string, required): 6-digit verification code from the email
- `session_id` (string, required): Session ID from auth_start

Output parameters:

- `result` (string)

### `auth_resend_otp` (~63 tokens)

Resend OTP Code

Resend the verification code to the patient's email. Use this if the original code expired (5-minute window) or was not received.

Requires the session_id from auth_start — no email needed.

Input parameters:

- `session_id` (string, required): Session ID from auth_start

Output parameters:

- `result` (string)

### `auth_check_payment` (~103 tokens)

Check Payment Status

Check if the patient has completed payment and upgrade the token to full scope. Call this after sharing the checkout payment link with the patient.

Poll every 10-15 seconds. When payment is detected, the token is automatically upgraded to full scope, unlocking portal tools (care plan, refills, messaging, weight logs, etc.).

Requires the guest token from auth_verify_otp as bearer_token.

Input parameters:

- `bearer_token` (string): Guest token from auth_verify_otp

Output parameters:

- `result` (string)

### `medications_list` (~133 tokens)

List Medications

List all available prescription medications including GLP-1 weight loss drugs (compounded semaglutide, compounded tirzepatide), peptide therapies (sermorelin for growth hormone support, NAD+ for cellular energy and anti-aging, glutathione for antioxidant support), and other compounded wellness treatments. Returns medication names, categories, available forms (injectable, oral tablet, sublingual drops, nasal spray), and starting prices. All medications are compounded by US-licensed 503A pharmacies and require evaluation by a licensed US healthcare provider before prescribing.

Input parameters:

- `client_ip` (string): Client IP address for rate limiting

Output parameters:

- `result` (string)

### `medications_details` (~222 tokens)

Get Medication Details

Get detailed information about a specific medication including: all available dosage strengths and titration schedules, available forms (injectable vials, pre-filled syringes, oral dissolving tablets, sublingual drops), all active plan options with pricing for each, what's included (provider consultation, medication, shipping, ongoing support), contraindications, and common side effects. Supports queries by medication name (e.g. 'semaglutide', 'tirzepatide', 'sermorelin', 'NAD+', 'glutathione') or by category (e.g. 'weight loss', 'peptides', 'anti-aging'). Use this to look up exact plan durations and pricing.

Input parameters:

- `category`: Filter by category (e.g. 'weight loss', 'peptides', 'anti-aging')
- `client_ip` (string): Client IP address for rate limiting
- `medication` (string, required): Medication name (e.g. 'semaglutide', 'tirzepatide', 'sermorelin', 'NAD+', 'glutathione')

Output parameters:

- `result` (string)

### `medications_availability` (~92 tokens)

Check Medication Availability

Check if a specific medication is available for shipping to the patient's state. Some compounded medications have state-specific restrictions based on pharmacy licensing. Returns availability status and reason if unavailable.

Input parameters:

- `client_ip` (string): Client IP address for rate limiting
- `medication` (string, required): Medication name to check availability for
- `state` (string, required): US state abbreviation (e.g. 'CA', 'NY', 'TX')

Output parameters:

- `result` (string)

### `medications_pricing` (~153 tokens)

Get Pricing

Get detailed pricing for a specific medication, form, and plan duration. Returns price breakdown including medication cost, provider consultation fee, shipping, and any applicable discounts for longer plans. Plan durations vary by medication — use medications_details first to see available plan_months values. Supports semaglutide, tirzepatide, sermorelin, NAD+, glutathione and all other available medications.

Input parameters:

- `client_ip` (string): Client IP address for rate limiting
- `form` (string, required): Medication form: 'injectable', 'tablet', or 'drops'
- `medication` (string, required): Medication name
- `plan_months` (integer, required): Plan duration in months (1, 4, or 6)

Output parameters:

- `result` (string)

### `medications_categories` (~84 tokens)

List Categories

List all medication categories available through the telehealth platform: Weight Loss (GLP-1 medications), Peptide Therapy (sermorelin, growth hormone peptides), Anti-Aging & Longevity (NAD+, glutathione), and other treatment categories. Each category includes a description and count of available medications.

Input parameters:

- `client_ip` (string): Client IP address for rate limiting

Output parameters:

- `result` (string)

### `eligibility_check` (~474 tokens)

Check Eligibility

Pre-screen a patient's basic eligibility for telehealth prescription services. Required: age (18+) and state (where the patient resides). Optional: BMI (20+ required for GLP-1 / weight-loss products), biological sex, pregnancy status, and diagnosed conditions.

Only pass parameters that apply to this patient. `pregnancy_status` applies ONLY when biological sex is female — omit it entirely for males. Don't invent values to satisfy the schema; if you don't know, leave the parameter out and the server will return what is or isn't checkable.

If you already know the patient's age, sex, state, height/weight from prior conversation context, you may pre-fill — but read the values back to the patient and get explicit confirmation before calling this tool. Returns eligibility status, available medications, and any disqualifying reasons (MTC/MEN2 history, pregnancy, out-of-coverage state, etc.).

Input parameters:

- `age` (integer, required): Patient's age in years (must be 18+). Confirm with the patient before submitting.
- `bmi`: Patient's Body Mass Index. Required for GLP-1 / weight-loss eligibility (must be 20+). Omit for longevity products. Compute from confirmed height + weight; don't ask the patient to compute it themsel…
- `client_ip` (string): Client IP address for rate limiting
- `conditions`: List of diagnosed medical conditions the patient confirms they have. Disqualifiers include medullary thyroid carcinoma (MTC) and MEN2 syndrome. Omit if the patient has no diagnosed conditions or hasn…
- `pregnancy_status`: Pregnancy status. Use one of these exact values: 'not pregnant', 'currently pregnant', 'planning pregnancy', 'breastfeeding'. ONLY applies when sex == 'female'. OMIT this parameter entirely for biolo…
- `sex`: Patient's biological sex. Pass 'female' when you'll also pass `pregnancy_status` (so the server knows pregnancy screening was considered). Pass 'male' to make it explicit that pregnancy screening doe…
- `state` (string, required): US state abbreviation (e.g. 'CA', 'NY') where the patient resides. Confirm before submitting.

Output parameters:

- `result` (string)

### `intake_questions` (~537 tokens)

Get Intake Questions

Get the medical intake questionnaire for the chosen medication(s). The questionnaire is product-aware: GLP-1 / weight-loss medications return weight-loss goals, GLP-1 history, and MTC/MEN2 screening; NAD+ and other longevity peptides return energy/sleep/stress/cognitive/delivery-method questions instead. If the patient wants more than one medication, pass the additional slugs in `additional_medications` — the server returns the UNION of section sets deduped by section key, so you ask each shared question exactly once.

\## How to present this to the patient
1\. PROGRESSIVE DISCLOSURE: walk through ONE section at a time. Wait for the patient's reply before moving to the next section. Do not paste the whole questionnaire in a single message.
2\. HONOR CONDITIONALS: each section and each question may carry a `conditional_on` predicate (e.g. `{sex_assigned_at_birth: Female}` on the Pregnancy section). SKIP any section/question whose predicate isn't satisfied. Don't ask males about pregnancy or perimenopause.
3\. QUIZ FORMAT: present every `select` / `multi_select` question as a short pick-list using the `options` array verbatim. The patient should be able to reply with a single choice, not a sentence. Reserve free text for `*_details` follow-ups.
4\. EASY FIRST: order sections from low-friction (goals, lifestyle, preferences) to high-friction (clinical history, MTC/MEN2, prior therapies). The provider sees all answers regardless of order asked.
5\. USE-AND-VERIFY: if you know answers from prior conversation context, pre-fill them in your draft, but read them back to the patient and get explicit OK before calling `intake_submit`. Never silently submit assumed values.

Returns two phases: (1) pre_checkout — eligibility / screening questions, collected and submitted BEFORE payment; (2) post_checkout — detailed clinical history, collected and submitted AFTER payment. Do not submit post_checkout answers before the patient has paid. A licensed US healthcare provider reviews both p…

Input parameters:

- `additional_medications`: Optional list of additional medication slugs the patient also wants. Use this when the patient is ordering more than one product in the same visit (e.g. GLP-1 + NAD+) so the questionnaire is deduped.
- `client_ip` (string): Client IP address for rate limiting
- `medication` (string, required): Primary medication slug (e.g. 'semaglutide', 'nad-injection', 'nad-nasal-spray')

Output parameters:

- `result` (string)

### `intake_submit` (~110 tokens)

Submit Intake

Submit a completed medical intake questionnaire for provider review. All fields from intake_questions must be completed. Returns an intake ID and estimated provider review time. The intake is reviewed by a licensed US healthcare provider who makes all prescribing decisions. Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `intake_answers` (object, required): Completed intake questionnaire answers from intake_questions
- `patient_email` (string, required): Patient's email address
- `patient_name` (string, required): Patient's full legal name

Output parameters:

- `result` (string)

### `intake_status` (~82 tokens)

Get Intake Status

Check the current status of a previously submitted intake questionnaire. Returns whether the intake is under review, approved, or denied by a licensed healthcare provider. Use this to poll for provider review completion before proceeding to order placement. Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `intake_id` (string, required): Intake ID returned from intake_submit

Output parameters:

- `result` (string)

### `consent_list` (~117 tokens)

Get Required Consents

Get the list of all consent documents a patient must accept before ordering medication. Returns consent IDs, titles, summaries, and order of presentation. Required consents include: telehealth informed consent, compounded medication treatment consent, pharmacy authorization, HIPAA notice of privacy practices, and AI-assisted intake disclosure. Each consent must be fetched individually via consent_text and confirmed by the patient before proceeding. Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `intake_id` (string, required): Intake ID to get required consents for

Output parameters:

- `result` (string)

### `consent_text` (~155 tokens)

Get Consent Text

Fetch the full text of a specific consent document for patient review. Returns the complete consent document split into titled sections that the agent MUST present to the patient verbatim in the conversation — do not summarize or paraphrase. Includes: consent version number, effective date, section headings and body text, a confirmation prompt the patient should agree to, and withdrawal instructions. Available consent types: telehealth informed consent, compounded medication treatment consent, pharmacy authorization, HIPAA notice of privacy practices, and AI-assisted intake disclosure. The patient must explicitly confirm each consent before the agent can call consent_submit. Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `consent_id` (string, required): Consent document ID from consent_list

Output parameters:

- `result` (string)

### `consent_submit` (~268 tokens)

Submit Consent

Record a patient's consent confirmation for a specific consent document. The agent must have already presented the full consent text (from consent_text) to the patient and received explicit confirmation. Required parameters: intake_id, consent_id, the patient's exact confirmation text (e.g. 'I agree'), consent method ('ai_agent_conversational'), the AI platform name ('chatgpt', 'claude', 'gemini'), and a session/conversation ID for audit trail. Returns a consent record with timestamp, audit trail details, and the list of remaining consents still needed. All consent records are retained for 10 years per HIPAA requirements. Requires authentication.

Input parameters:

- `agent_platform` (string): AI platform name: 'chatgpt', 'claude', or 'gemini'
- `agent_session_id` (string): Unique session/conversation ID for audit trail
- `bearer_token` (string): Authentication token for the patient session
- `consent_id` (string, required): Consent document ID being confirmed
- `consent_method` (string): Method of consent collection
- `intake_id` (string, required): Intake ID this consent belongs to
- `patient_confirmation` (string, required): Patient's exact confirmation text (e.g. 'I agree')
- `timestamp` (string): ISO 8601 timestamp of consent confirmation

Output parameters:

- `result` (string)

### `consent_status` (~82 tokens)

Get Consent Status

Check whether all required consents are complete for a patient intake. Returns status of each consent and whether the patient can proceed to ordering. This is a gate — order_create will reject if consents are incomplete. Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `intake_id` (string, required): Intake ID to check consent completion for

Output parameters:

- `result` (string)

### `order_create` (~233 tokens)

Create Order

Create a new prescription medication order. The patient must have completed intake questionnaire and consent before ordering. Required: medication name, selected form (injectable, tablet, drops), plan duration (1, 4, or 6 months), shipping address. The order is reviewed by a licensed US healthcare provider who makes the final prescribing decision. If approved, medication is compounded at a US-licensed 503A pharmacy and shipped directly to the patient. Returns order ID, estimated provider review time, and expected delivery window. Payment is processed via Stripe Agentic Commerce Protocol (ACP). Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `form` (string, required): Medication form: 'injectable', 'tablet', or 'drops'
- `intake_id` (string, required): Approved intake ID from intake_submit
- `medication` (string, required): Medication name to order
- `plan_months` (integer, required): Plan duration in months (1, 4, or 6)
- `shipping_address` (object, required): Shipping address with keys: line1, city, state, zip, and optional line2

Output parameters:

- `result` (string)

### `order_status` (~78 tokens)

Get Order Status

Get the current status of a medication order. Returns status (pending_review, provider_reviewing, approved, needs_info, denied, compounding, shipped, delivered), tracking information, and delivery estimate. Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `order_id` (string, required): Order ID from order_create

Output parameters:

- `result` (string)

### `order_documents` (~73 tokens)

Get Required Documents

Get the list of documents a patient needs to upload for their order. Returns required documents (photo ID, selfie for verification) with upload status and accepted file formats. Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `order_id` (string, required): Order ID to check required documents for

Output parameters:

- `result` (string)

### `order_upload` (~142 tokens)

Upload Document

Upload a verification document for a medication order. Accepts photo ID and selfie as base64-encoded files. Supported formats: PDF, JPEG, PNG. Maximum size: 10MB. Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `document_type` (string, required): Document type: 'photo_id' or 'selfie'
- `file_base64` (string, required): Base64-encoded file content (PDF, JPEG, or PNG, max 10MB)
- `file_name` (string, required): Original filename with extension (e.g. 'license.jpg')
- `order_id` (string, required): Order ID to upload document for

Output parameters:

- `result` (string)

### `checkout_create` (~167 tokens)

Create Checkout

Initiate a checkout session for a medication order. Returns checkout details including line items, total, and payment options.

TWO PAYMENT PATHS are supported:
1\. **Stripe ACP (preferred)**: If your platform supports Stripe Agentic Commerce Protocol, provision a Shared Payment Token (SPT) and call checkout_complete to pay instantly.
2\. **Payment link (fallback)**: If ACP/SPT is not available, present the returned `payment_url` to the patient. This is a Stripe-hosted checkout page where the patient can enter their card and pay directly. After sending the link, call checkout_status to poll for payment completion.

Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `order_id` (string, required): Order ID to create checkout for

Output parameters:

- `result` (string)

### `checkout_update` (~82 tokens)

Update Checkout

Update an existing checkout session. Can modify shipping method, apply promo codes, or update customer details before payment is completed. Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `checkout_id` (string, required): Checkout session ID to update
- `updates` (object, required): Updates to apply: shipping method, promo code, or customer details

Output parameters:

- `result` (string)

### `checkout_complete` (~117 tokens)

Complete Checkout

Complete payment using Stripe ACP (Shared Payment Token). Only use this if your platform supports Stripe Agentic Commerce Protocol and can provision an SPT. If your platform does NOT support ACP, use the `payment_url` from checkout_create instead, then poll checkout_status. Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `checkout_id` (string, required): Checkout session ID to complete payment for
- `shared_payment_token` (string, required): Stripe ACP Shared Payment Token (SPT) provisioned by the client platform

Output parameters:

- `result` (string)

### `checkout_status` (~106 tokens)

Get Checkout Status

Check the payment status of a checkout session. Use this to poll for completion after sending the patient a payment link (the `payment_url` from checkout_create). When the patient pays via the link, this tool detects the payment, triggers order fulfillment, and returns the confirmation. Poll every 5-10 seconds while waiting. Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `checkout_id` (string, required): Checkout session ID to check payment status for

Output parameters:

- `result` (string)

### `checkout_cancel` (~62 tokens)

Cancel Checkout

Cancel an in-progress checkout session. Releases any held inventory and cancels the associated Stripe PaymentIntent if not yet captured. Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `checkout_id` (string, required): Checkout session ID to cancel

Output parameters:

- `result` (string)

### `portal_log_weight` (~97 tokens)

Log Weight

Log a patient's weight for tracking progress on their treatment plan. Requires patient_id, weight in pounds, and date (ISO 8601). Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `date` (string, required): Date of weight measurement in ISO 8601 format (YYYY-MM-DD)
- `patient_id` (string, required): Patient ID
- `weight_lbs` (number, required): Weight in pounds

Output parameters:

- `result` (string)

### `portal_log_side_effects` (~116 tokens)

Log Side Effects

Log side effects a patient is experiencing. If severity is 'severe', the case is auto-flagged for immediate provider review and returns urgent guidance. Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `effects` (array, required): List of side effects being experienced (e.g. ['nausea', 'headache'])
- `patient_id` (string, required): Patient ID
- `severity` (string, required): Severity level: 'mild', 'moderate', or 'severe'

Output parameters:

- `result` (string)

### `portal_message` (~94 tokens)

Message Provider

Send a message to the patient's healthcare provider. Returns sent confirmation and estimated response time. Urgent messages (containing keywords like 'emergency', 'chest pain', 'difficulty breathing') are flagged for priority response. Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `message` (string, required): Message text to send to the healthcare provider
- `patient_id` (string, required): Patient ID

Output parameters:

- `result` (string)

### `portal_care_plan` (~72 tokens)

Get Care Plan

Get the patient's current care plan including: current medication, current dosage, titration schedule, next dose adjustment date, upcoming refill date, provider notes, and weight progress summary. Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `patient_id` (string, required): Patient ID

Output parameters:

- `result` (string)

### `portal_refill` (~64 tokens)

Request Refill

Request a medication refill for the patient's current prescription. Creates a refill order that will be reviewed by a provider within 24-48 hours. Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `patient_id` (string, required): Patient ID

Output parameters:

- `result` (string)

### `portal_support` (~83 tokens)

Contact Support

Contact customer support with a question or issue. Creates a support ticket and returns the ticket ID and estimated response time. Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `message` (string, required): Detailed description of the question or issue
- `patient_id` (string, required): Patient ID
- `subject` (string, required): Support ticket subject line

Output parameters:

- `result` (string)

### `provider_questions` (~86 tokens)

Get Provider Questions

Get follow-up questions from the healthcare provider for a specific order. The provider may request additional information before making a prescribing decision. Returns the questions if the order status is 'needs_info', or a message that no questions are pending. Requires authentication.

Input parameters:

- `bearer_token` (string): Authentication token for the patient session
- `order_id` (string, required): Order ID to get provider questions for

Output parameters:

- `result` (string)

### `provider_respond` (~88 tokens)

Submit Provider Response

Submit answers to provider follow-up questions for a specific order. The responses are sent to the provider for review. Returns confirmation and updated order status. Requires authentication.

Input parameters:

- `answers` (object, required): Answers to the provider's follow-up questions keyed by question ID
- `bearer_token` (string): Authentication token for the patient session
- `order_id` (string, required): Order ID to submit responses for

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/health-chia-chia-mcp/mcp#diagnostics

## Score history

- 2026-08-04: 71
- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 69
- 2026-07-30: 68
- 2026-07-29: 68
- 2026-07-28: 67
- 2026-07-27: 66
- 2026-07-26: 66

## Links

- Remote endpoint: https://mcp.chia.health/
- Repository: https://github.com/chia-health/chia-mcp
- Website: https://chia.health/
- Changelog RSS feed: https://verifymcp.io/servers/health-chia-chia-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/health-chia-chia-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/health-chia-chia-mcp/mcp