Chia Health MCP Server

health.chiaPublished by chia.healthOfficial publisherv1.0.0Updated Nov 2, 2026

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

Overview

AI-generated overview

Remote MCP server for Chia Health, a US telehealth platform, letting an assistant browse treatments, run intake, sign consents, order, pay and manage care.

What you can do
  • Browse medications, categories, pricing and state shipping availability
  • Pre-screen eligibility and fetch, submit and track medical intake questionnaires
  • List, read out and record consent documents, and check consent status
  • Create orders, list and upload ID/selfie verification documents, track order status
  • Create, update, complete, poll and cancel checkout sessions, including Stripe ACP payment
  • Log weight and side effects, message the care team, view the care plan, request refills, open support tickets, and answer provider follow-up questions
When to use it
Use it when a patient wants to explore or start a Chia Health telehealth treatment in conversation: checking GLP-1 or peptide options and prices, seeing whether a medication ships to their state, completing intake and consents, placing and paying for an order, or managing an existing treatment after payment.
Requirements
A remote Streamable HTTP endpoint; no local install. The client must support streamable HTTP. Public discovery and eligibility tools need no auth; intake, consent, ordering and checkout need a guest bearer token obtained by emailing a 6-digit code via auth_start and auth_verify_otp; portal tools need a full-scope token after payment. Network access to the Chia endpoint is required.
Before you install
Handles sensitive health data: email, phone, name, age, state, BMI, conditions, weight, side effects, and base64 photo ID and selfie uploads. Actions create real orders, consents and payments; consent records cannot be deleted and PHI access is audit-logged. Payment can be taken in-conversation via a Stripe Shared Payment Token, which spends the patient's money. Consent text must be shown verbatim before recording agreement.

Installation

In SourceWeft

  1. Open Chia Health MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/health.chia%2Fchia-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

Chia Health MCP Server

[License] [MCP] [HIPAA] [Tools] [Stripe ACP]

The official MCP (Model Context Protocol) server for Chia (Chia Health, Inc.), a US telehealth prescription platform. It lets AI assistants (ChatGPT, Claude, Gemini, Copilot and custom agents) help patients browse treatments, check eligibility, complete a medical intake, sign consent documents, place an order, pay, and manage their treatment, all in conversation.

Treatments include GLP-1 medications (semaglutide, tirzepatide, including tablets), peptide therapies (sermorelin, NAD+, glutathione) and longevity programs. Every prescription is evaluated by a licensed US provider and delivered from US-licensed 503A compounding pharmacies that source their ingredients solely from FDA-regulated sources, to all 50 states plus DC. Chia Health is LegitScript-certified, and patient support is available 24/7.

Prices: current plans and prices are on chia.health, and the medications_list, medications_details and medications_pricing tools always return the live prices. This README does not list prices.

Getting Started

Chia 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

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

json
{  "mcpServers": {    "chia-health": {      "url": "https://mcp.chia.health/"    }  }}
Cursor

Add to .cursor/mcp.json in your project or ~/.cursor/mcp.json globally:

json
{  "mcpServers": {    "chia-health": {      "url": "https://mcp.chia.health/"    }  }}
Cline / VS Code

Add to your Cline MCP settings:

json
{  "mcpServers": {    "chia-health": {      "url": "https://mcp.chia.health/"    }  }}
Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

json
{  "mcpServers": {    "chia-health": {      "serverUrl": "https://mcp.chia.health/"    }  }}
Other MCP Clients

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 call these public tools right away (no auth required):

medications_categories     → treatment categoriesmedications_list           → all medications with current pricingmedications_availability   → check if a medication ships to your stateeligibility_check          → pre-screen age, state, BMI

What Can Your AI Assistant Do?

CategoryToolsAuth
Auth: email verification code, session, payment detection4No*
Discovery: browse medications, pricing, availability5No
Qualification: eligibility checks, intake questionnaires4Partial
Consent: present and sign consent documents4Guest
Ordering: place orders, upload ID verification4Guest
Checkout: Stripe ACP payments or authenticated payment links5Guest
Patient Portal: log weight, message the care team, refills6Full
Provider: answer follow-up questions from your provider2Guest

* Auth tools use a session_id (no token), except auth_check_payment, which uses a bearer token.

Important: Every prescription is evaluated and approved by a licensed US provider. This server handles the patient workflow; it does not make clinical decisions.

Authentication

Patients can browse freely without signing in: discovery, eligibility and the intake question preview are all public.

When the patient is ready to start their medical intake, they verify their email:

  1. auth_start(email, phone, first_name) → sends a 6-digit code to their email, returns a session_id
  2. auth_verify_otp(session_id, code) → returns a guest-scoped bearer token

The guest token covers 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

ToolAuthDescription
auth_startNoSend a verification code to the patient's email, get a session_id
auth_verify_otpNoVerify the code, get a guest-scoped bearer token
auth_resend_otpNoResend the code if it expired or did not arrive
auth_check_paymentGuestPoll for payment, upgrade the token to full scope

Discovery (public, no auth)

ToolDescription
medications_listList all medications with categories, forms and current pricing
medications_detailsDetailed info for one medication (plans, pricing, what's included)
medications_availabilityCheck if a medication ships to a given state
medications_pricingPrice breakdown for a medication, form and plan length
medications_categoriesList treatment categories (Weight Loss, Peptides, Longevity, etc.)

Qualification (public + guest)

ToolAuthDescription
eligibility_checkNoPre-screen age, state, BMI and medical conditions
intake_questionsNoGet the structured intake questionnaire for a medication
intake_submitGuestSubmit the completed intake for provider review
intake_statusGuestCheck intake review status (under review, approved, denied)

Consent (guest token required)

ToolDescription
consent_listList the consent documents needed for an intake
consent_textGet the full verbatim text of a consent document
consent_submitRecord the patient's consent with an audit trail
consent_statusCheck which consents are complete or pending

Ordering (guest token required)

ToolDescription
order_createCreate a medication order (requires all consents complete)
order_statusCheck order status and tracking
order_documentsList required ID documents for an order
order_uploadUpload a photo ID or selfie for identity verification

Checkout (guest token required)

ToolDescription
checkout_createCreate a checkout; returns an authenticated payment link
checkout_updateUpdate a pending checkout (promo code, shipping)
checkout_completeComplete payment with a Stripe Shared Payment Token (ACP path)
checkout_statusPoll payment status after sending a payment link (fallback path)
checkout_cancelCancel an in-progress checkout

Patient Portal (full token required, after payment)

ToolDescription
portal_log_weightLog weight for progress tracking
portal_log_side_effectsReport side effects (severe ones are flagged for the provider)
portal_messageSend a message to the care team
portal_care_planGet current medication, dosing and weight progress
portal_refillRequest a refill
portal_supportOpen a support ticket

Provider (guest token required)

ToolDescription
provider_questionsGet follow-up questions from the provider
provider_respondSubmit answers to the provider's questions

Example Agent Flows

1. Browse Medications (no auth)

User: "What weight loss medications do you offer?"
Agent calls: medications_list→ Categories with semaglutide, tirzepatide, etc., and current prices
Agent calls: medications_details(medication="semaglutide-injectable")→ Available plans with their current prices
Agent calls: medications_availability(medication="semaglutide-injectable", state="TX")→ { "available": true }
Agent calls: eligibility_check(age=35, state="TX", bmi=31.2)→ { "eligible": true, "available_medications": [...] }

2. Full Ordering Flow (verify → intake → consent → order → pay)

== VERIFY IDENTITY ==
1. auth_start(email="[email protected]", phone="5551234567", first_name="Jane")   → { "session_id": "abc123...", "otp_sent": true }
2. auth_verify_otp(session_id="abc123...", code="847293")   → { "guest_token": "mcp_...", "scope": "guest" }
== MEDICAL INTAKE ==
3. intake_questions(medication="semaglutide-injectable")   → Structured questionnaire (demographics, vitals, medical history, etc.)   → Agent asks one section at a time
4. intake_submit(patient_email, patient_name, answers, bearer_token)   → { "intake_id": "42", "next_step": "get_required_consents" }
5. consent_list(intake_id="42", bearer_token)   → Consent documents (telehealth, treatment, pharmacy, HIPAA, AI disclosure)
6. For each consent:   a. consent_text(consent_id, bearer_token)      → Full text the agent MUST present verbatim   b. Patient confirms: "I agree"   c. consent_submit(intake_id, consent_id, "I agree", bearer_token)
== ORDER & PAY ==
7. order_create(intake_id, medication, form, plan_months, shipping_address, bearer_token)   → { "order_id": "99", "total": "<current price>", "next_step": "create_checkout" }
8. checkout_create(order_id="99", bearer_token)   → { "checkout_id": "7", "payment_url": "https://chia.health/..." }   → Agent shares the link with the patient; it is also sent by email and SMS
9a. (ACP path) checkout_complete(checkout_id="7", shared_payment_token="spt_...", bearer_token)    → { "payment_status": "success", "confirmation_number": "CHIA-000099" }
9b. (Fallback) Patient opens payment_url in a browser and pays on the Chia checkout page
10. auth_check_payment(bearer_token)    → { "paid": true, "scope": "full" }  // token upgraded, portal unlocked

3. Patient Portal (full token, after payment)

1. portal_log_weight(patient_id, weight_lbs=195.5, date="2026-06-15", bearer_token)   → { "recorded": true }
2. portal_care_plan(patient_id, bearer_token)   → Current medication, phase, dosing schedule, recent weights
3. portal_log_side_effects(patient_id, effects=["nausea"], severity="mild", bearer_token)   → { "recorded": true, "flagged_for_review": false }
4. portal_message(patient_id, message="Nausea improving", bearer_token)   → { "sent": true }

Stripe ACP Integration

Chia supports Stripe's Agentic Commerce Protocol (ACP):

  1. Order creation: order_create calculates the total from current prices and creates a pre-payment order.
  2. Checkout: checkout_create creates a Stripe PaymentIntent (for ACP) and an authenticated payment link that signs the patient in and opens the Chia checkout page. The link is also sent by email and SMS.
  3. Payment, 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, the patient pays in their browser, and the agent polls auth_check_payment to detect completion.
  4. After payment: the subscription and treatment enrollment are created automatically, and 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, action, resource, IP address and timestamp. Logs are retained for 10 years.
  • Consent records: every consent confirmation stores the verbatim confirmation text, method (AI agent conversation), platform, session ID and IP address. Consent records cannot be deleted.
  • Input validation: all inputs are validated and sanitized; control characters are stripped, lengths enforced, and email, state, phone and ZIP formats checked.
  • Email verification first: email ownership is verified with a 6-digit code before any patient data is accessed. Tokens are SHA-256 hashed and scoped (guest / full).
  • Rate limiting: per-user and per-category limits (public: 100/min, sign-in: 5/min, authenticated: 30/min, consent: 10/min, checkout: 5/min).
  • Minimal data exposure: tools return only what the current step needs. Payment details and full SSNs are never returned.

Support

License

Apache License 2.0. See LICENSE for details.

Copyright 2026 Chia Health, Inc.

Source: README.md at commit 2918a83

Tools

34

auth_start

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.

Parametersemailrequiredphonerequiredlast_namefirst_namerequired

auth_verify_otp

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.

Parameterscoderequiredsession_idrequired

auth_resend_otp

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.

Parameterssession_idrequired

auth_check_payment

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.

Parametersbearer_token

medications_list

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.

Parametersclient_ip

medications_details

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.

Parameterscategoryclient_ipmedicationrequired

medications_availability

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.

Parametersstaterequiredclient_ipmedicationrequired

medications_pricing

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.

Parametersformrequiredclient_ipmedicationrequiredplan_monthsrequired

medications_categories

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.

Parametersclient_ip

eligibility_check

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.).

Parametersagerequiredbmisexstaterequiredclient_ipconditionspregnancy_status

intake_questions

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 ph

Parametersclient_ipmedicationrequiredadditional_medications

intake_submit

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.

Parametersbearer_tokenpatient_namerequiredpatient_emailrequiredintake_answersrequired

intake_status

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.

Parametersintake_idrequiredbearer_token

order_create

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.

Parametersformrequiredintake_idrequiredmedicationrequiredplan_monthsrequiredbearer_tokenshipping_addressrequired

order_status

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.

Parametersorder_idrequiredbearer_token

order_documents

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.

Parametersorder_idrequiredbearer_token

order_upload

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.

Parametersorder_idrequiredfile_namerequiredfile_base64requiredbearer_tokendocument_typerequired

checkout_create

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.

Parametersorder_idrequiredbearer_token

checkout_update

Update Checkout

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

Parametersupdatesrequiredcheckout_idrequiredbearer_token

checkout_complete

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.

Parameterscheckout_idrequiredbearer_tokenshared_payment_tokenrequired

checkout_status

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.

Parameterscheckout_idrequiredbearer_token

checkout_cancel

Cancel Checkout

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

Parameterscheckout_idrequiredbearer_token

portal_log_weight

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.

Parametersdaterequiredpatient_idrequiredweight_lbsrequiredbearer_token

portal_log_side_effects

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.

Parameterseffectsrequiredseverityrequiredpatient_idrequiredbearer_token

portal_message

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.

Parametersmessagerequiredpatient_idrequiredbearer_token

portal_care_plan

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.

Parameterspatient_idrequiredbearer_token

portal_refill

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.

Parameterspatient_idrequiredbearer_token

portal_support

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.

Parametersmessagerequiredsubjectrequiredpatient_idrequiredbearer_token

provider_questions

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.

Parametersorder_idrequiredbearer_token

provider_respond

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.

Parametersanswersrequiredorder_idrequiredbearer_token

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Chia integrations