healthie

Status

Newest check: answered with tools, from the daily check, 2026-10-06, 1,374 ms.

From one check a day over the last 3 days. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-072026-10-06

answered with toolssign-in or payment askednot answeringnot checked

Past outages lasted 2 days before it answered again.

Compare: the most reliable servers in Data, search and analytics, ranked by days answering.

Tools

16 tools: 14 read-only, 0 change data, 2 high risk (delete, pay, send or run code).

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 2,820 tokens of tool definitions and a 1,374 ms handshake.

• high riskhealthie_create_taskCreates a task in Healthie (additive). Requires content (the task text); optionally attach it to a client (user_id), set a due_date, priority, or created_by_id. GraphQL: mutation createTask(input: createTaskInput).
• high riskhealthie_create_noteCreates a note/chat entry in Healthie (additive). Requires content (the note text); optionally attach it to a client (user_id) or mark it as an org chat. GraphQL: mutation createNote(input: createNoteInput).
• read-onlyhealthie_current_userFetch the authenticated Healthie account (the provider/user that owns the API key). Good first call to verify auth. Read-only. GraphQL: query currentUser.
• read-onlyhealthie_get_organizationFetch the current organization / practice (name, NPI, contact, user counts). Read-only. GraphQL: query organization.
• read-onlyhealthie_list_patientsList patients/clients, optionally filtered by keyword search or active status. Read-only. GraphQL: query users(keywords, offset, page_size, should_paginate, active_status).
• read-onlyhealthie_get_userFetch a single user (patient or provider) by id. Read-only. GraphQL: query user(id).
• read-onlyhealthie_list_appointmentsList appointments, optionally filtered by patient, provider, date range, time-filter or status. Read-only. GraphQL: query appointments(user_id, provider_id, filter, startDate, endDate, filter_by_appointment_status).
• read-onlyhealthie_get_appointmentFetch a single appointment by id. Read-only. GraphQL: query appointment(id).
• read-onlyhealthie_list_appointment_typesList the practice's appointment types (services), optionally keyword-filtered. Read-only. GraphQL: query appointmentTypes(keywords, offset, page_size, should_paginate).
• read-onlyhealthie_list_formsList custom module form templates (charting notes, intake forms), optionally by keyword or category. Read-only. GraphQL: query customModuleForms(keywords, category, offset, page_size, should_paginate).
• read-onlyhealthie_list_form_answer_groupsList completed form submissions (charting notes / filled intake forms), optionally scoped to a patient or a form template. Read-only. GraphQL: query formAnswerGroups(user_id, custom_module_form_id, should_paginate, offset).
• read-onlyhealthie_list_documentsList documents, optionally scoped to a patient (viewable_user_id) or by keyword. Read-only. GraphQL: query documents(viewable_user_id, keywords, offset, page_size, should_paginate).
• read-onlyhealthie_list_tasksList tasks, optionally scoped to a client or filtered by completion status. Read-only. GraphQL: query tasks(client_id, completed_status, offset, per_page).
• read-onlyhealthie_list_goalsList goals, optionally scoped to a patient. Read-only. GraphQL: query goals(user_id, offset, per_page).
• read-onlyhealthie_list_metric_entriesList tracked metric entries (weight, blood pressure, etc.), optionally scoped to a client or a category. Read-only. GraphQL: query entries(client_id, category, offset, page_size).
• read-onlyhealthie_list_conversationsList messaging conversations, optionally between the current user and a given user. Read-only. GraphQL: query conversations(user_id).

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/healthie.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/healthie.usefulapi.io/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=healthie.usefulapi.io%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/healthie.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/healthie.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=healthie.usefulapi.io%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.