nexhealth

Status

Newest check: answered with tools, from the daily check, 2026-10-03, 894 ms.

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

Last 30 days

2026-09-042026-10-03

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in Health, ranked by days answering.

Tools

16 tools: 13 read-only, 0 change data, 3 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 3,809 tokens of tool definitions and a 894 ms handshake.

• high risknexhealth_create_patientCREATE a new patient record in a location. MUTATES DATA - writes to the connected EHR/PMS. GET the patient back to confirm. POST /patients.
• high risknexhealth_book_appointmentBOOK a new appointment. MUTATES DATA - creates an appointment in the connected EHR/PMS (optionally notifying the patient). Provide either end_time or appointment_type_id. POST /appointments.
• high risknexhealth_update_appointmentUPDATE / reschedule / cancel / confirm an existing appointment by id. MUTATES DATA in the connected EHR/PMS. PATCH /appointments/{id}.
• read-onlynexhealth_list_locationsList the practice locations for an institution (id, name, address). Good first call to discover location_ids for other tools. GET /locations.
• read-onlynexhealth_list_providersList practitioners (providers) for an institution, optionally scoped to a location. GET /providers.
• read-onlynexhealth_search_patientsSearch patients within a location by name, email, phone, or date of birth. Patient search is always in a location context. GET /patients.
• read-onlynexhealth_get_patientFetch a single patient by id. GET /patients/{id}.
• read-onlynexhealth_list_appointmentsList appointments in a date/time window, optionally filtered by location, patient, or provider. GET /appointments.
• read-onlynexhealth_get_appointmentFetch a single appointment by id. GET /appointments/{id}.
• read-onlynexhealth_list_appointment_slotsFind bookable appointment start times across providers/locations for a date range. High-value for scheduling. GET /appointment_slots.
• read-onlynexhealth_list_appointment_typesList the appointment types configured for an institution/location. GET /appointment_types.
• read-onlynexhealth_list_operatoriesList operatories (chairs/rooms) for an institution, optionally scoped to a location. GET /operatories.
• read-onlynexhealth_list_insurance_plansList insurance plans known to the institution, optionally scoped to a location. GET /insurance_plans.
• read-onlynexhealth_list_insurance_coveragesList a patient's insurance coverages. GET /insurance_coverages.
• read-onlynexhealth_list_proceduresList clinical procedures, optionally scoped to a patient. GET /procedures.
• read-onlynexhealth_sync_statusReport the data-sync health for the practice's EHR/PMS integration (is the Synchronizer up to date?). GET /sync_status.

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/nexhealth.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/nexhealth.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=nexhealth.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/nexhealth.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/nexhealth.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=nexhealth.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.