Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Halaxy MCP by usefulapi

REMOTE · HALAXY.USEFULAPI.IO

Read Halaxy patients, appointments, slots and invoices; create patients, appointments and notes.

−45 this week 18 Trust /100

Last scanned (10 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Nov 26 −49
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Stability: 0.20 → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 31 Oct 26 +4
    • Authorization: partial → pass ▲ security
    • MCP protocol: fail → pass ▲ functional
    • New prompt “browse_schedules_and_time_slots” functional
    • New prompt “find_open_appointment_times” functional
    • New prompt “list_your_appointment_types_and_fees” functional
    • New prompt “see_your_practitioners_and_clinics” functional
    • MCP protocol version: 2025-06-18 → 2025-11-25 functional
    • Server version: 1.7.0 → 1.9.0 functional
    • Server version: 1.6.0 → 1.7.0 functional
    • Server version: 1.5.2 → 1.6.0 functional
  • 30 Oct 26 0
    • Server version: 1.5.1 → 1.5.2 functional
    • Server version: 1.5.0 → 1.5.1 functional
  • 29 Oct 26 0
    • Server version: 1.4.0 → 1.5.0 functional
    • Server version: 1.3.0 → 1.4.0 functional
  • 28 Oct 26 +1
    • Server version: 1.1.0 → 1.3.0 functional
  • 27 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.0.0 → 1.1.0 functional
  • 26 Oct 26 62

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://halaxy.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of halaxy.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://halaxy.usefulapi.io/mcp Redirected 302 https://usefulapi.io/halaxy/
http (plaintext) http://halaxy.usefulapi.io/mcp Inconclusive 302 http://halaxy.usefulapi.io/mcp
MCP tools · 35 exposed · ~5,410 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
halaxy_create_appointment ~269

Writes to the live Halaxy account. Books an appointment for a patient with a practitioner at a clinic (the practitioner role). Halaxy also creates the invoice, clinical note and reminder. Use halaxy_find_available_appointments for free times. By default a double booking is refused (HTTP 409, nothing created). POST /main/Appointment/$book.

NameTypeReqDescription
charge_item_definition_idstring–The fee id (halaxy_list_fees) booked for the appointment.
endstringyesEnd with the time zone offset, e.g. 2027-06-15T16:00:00+10:00.
fail_on_double_bookingboolean–Refuse if the practitioner already has an appointment then (default true).
healthcare_service_idstring–The appointment type id (halaxy_list_healthcare_services).
patient_idstringyesThe patient id.
practitioner_role_idstringyesThe PractitionerRole id (practitioner at a clinic), e.g. PR-1234567.
startstringyesStart with the time zone offset, e.g. 2027-06-15T15:00:00+10:00.
statusstring–Initial status (default booked).

No output schema declared.

No examples provided.

halaxy_create_clinical_note ~135

Writes to the live Halaxy account. Adds a clinical note to a patient's record as a DRAFT (preliminary); the practitioner reviews and publishes it in Halaxy. The author is a PractitionerRole (practitioner at a clinic). Only HTML text is supported. POST /main/DocumentReference.

NameTypeReqDescription
htmlstringyesThe note body as HTML.
patient_idstringyesThe patient the note is for.
practitioner_role_idstringyesThe PractitionerRole id of the author, e.g. PR-1234567.
titlestringyesThe note title.

No output schema declared.

No examples provided.

halaxy_create_patient ~202

Writes to the live Halaxy account. Creates a new patient record (always a new one: search with halaxy_list_patients first to avoid a duplicate). Pass managing_organization (the practice group id, e.g. PG-12345, from halaxy_list_organizations) if Halaxy asks for it. POST /main/Patient.

NameTypeReqDescription
addressobject–Mailing address.
birth_datestring–Date of birth, YYYY-MM-DD.
emailstring–Email address.
familystringyesLegal family name (surname).
genderstring–Gender as registered in government records.
givenstringyesLegal given name.
managing_organizationstring–The practice group id, e.g. PG-12345.
mobilestring–Mobile number as +{country code}{number}, no spaces.
preferred_namestring–Preferred (usual) given name.

No output schema declared.

No examples provided.

halaxy_find_available_appointments ~226

Find free appointment times between start and end for a given duration, respecting each practitioner's online booking preferences (buffer time, lead time, advance booking limit). Narrow it with practitioner, practitioner_role or organization. GET /main/Appointment/$find.

NameTypeReqDescription
apply_buffer_timeboolean–true applies buffer time to show all available times.
durationintegeryesAppointment length in minutes.
emergencyboolean–true ignores lead time, to show all times for emergency appointments.
endstringyesEnd of the search window, e.g. 2027-01-12T23:59:59.
organizationstring–Organization (clinic) id.
practitionerstring–Practitioner id.
practitioner_rolestring–PractitionerRole id.
showstring–first-available = only the first available time.
sortstring–start or -start.
startstringyesStart of the search window, e.g. 2027-01-12T00:00:00.

No output schema declared.

No examples provided.

halaxy_get_appointment ~51

Fetch an appointment with its participants and statuses (HEALTH DATA) by id. GET /main/Appointment/{id}.

NameTypeReqDescription
idstringyesThe Appointment id (from the matching list tool).

No output schema declared.

No examples provided.

halaxy_get_coverage ~48

Fetch a patient's coverage (claim details) record by id. GET /main/Coverage/{id}.

NameTypeReqDescription
idstringyesThe Coverage id (from the matching list tool).

No output schema declared.

No examples provided.

halaxy_get_fee ~49

Fetch a fee (ChargeItemDefinition) by id. GET /main/ChargeItemDefinition/{id}.

NameTypeReqDescription
idstringyesThe ChargeItemDefinition id (from the matching list tool).

No output schema declared.

No examples provided.

halaxy_get_healthcare_service ~45

Fetch an appointment type by id. GET /main/HealthcareService/{id}.

NameTypeReqDescription
idstringyesThe HealthcareService id (from the matching list tool).

No output schema declared.

No examples provided.

halaxy_get_invoice ~40

Fetch an invoice by id. GET /main/Invoice/{id}.

NameTypeReqDescription
idstringyesThe Invoice id (from the matching list tool).

No output schema declared.

No examples provided.

halaxy_get_invoice_line ~44

Fetch an invoice line by id. GET /main/InvoiceLine/{id}.

NameTypeReqDescription
idstringyesThe InvoiceLine id (from the matching list tool).

No output schema declared.

No examples provided.

halaxy_get_organization ~50

Fetch a practice group, clinic, funder or external practice by id. GET /main/Organization/{id}.

NameTypeReqDescription
idstringyesThe Organization id (from the matching list tool).

No output schema declared.

No examples provided.

halaxy_get_patient ~46

Fetch a patient record (HEALTH DATA) by id. GET /main/Patient/{id}.

NameTypeReqDescription
idstringyesThe Patient id (from the matching list tool).

No output schema declared.

No examples provided.

halaxy_get_payment_transaction ~44

Fetch a payment transaction by id. GET /main/PaymentTransaction/{id}.

NameTypeReqDescription
idstringyesThe PaymentTransaction id (from the matching list tool).

No output schema declared.

No examples provided.

halaxy_get_practitioner ~45

Fetch a practitioner or administrator by id. GET /main/Practitioner/{id}.

NameTypeReqDescription
idstringyesThe Practitioner id (from the matching list tool).

No output schema declared.

No examples provided.

halaxy_get_practitioner_role ~51

Fetch a practitioner role at a clinic location by id. GET /main/PractitionerRole/{id}.

NameTypeReqDescription
idstringyesThe PractitionerRole id (from the matching list tool).

No output schema declared.

No examples provided.

halaxy_get_referral ~46

Fetch a referral (HEALTH DATA) by id. GET /main/Referral/{id}.

NameTypeReqDescription
idstringyesThe Referral id (from the matching list tool).

No output schema declared.

No examples provided.

halaxy_get_referral_definition ~45

Fetch a referral template by id. GET /main/ReferralDefinition/{id}.

NameTypeReqDescription
idstringyesThe ReferralDefinition id (from the matching list tool).

No output schema declared.

No examples provided.

halaxy_get_schedule ~41

Fetch a practitioner schedule by id. GET /main/Schedule/{id}.

NameTypeReqDescription
idstringyesThe Schedule id (from the matching list tool).

No output schema declared.

No examples provided.

halaxy_get_slot ~41

Fetch a time slot by id. GET /main/Slot/{id}.

NameTypeReqDescription
idstringyesThe Slot id (from the matching list tool).

No output schema declared.

No examples provided.

halaxy_list_appointments ~349

List or search appointments (HEALTH DATA: names the patient). Filters combine with AND. Paged: pass next_page as page. GET /main/Appointment.

NameTypeReqDescription
countinteger–Results per page, 1-100 (default 30).
createdstring–Created (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
datestring–Appointment date/time (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
idstring–One id or several separated by commas, for example 1,2,3.
includearray–Also return related resources in "included": any of Appointment:patient, Appointment:practitioner-role.
include_iteratearray–Also return resources related to an included one (needs the matching include): any of PractitionerRole:practitioner, PractitionerRole:organization.
last_updatedstring–Only records last updated at this time (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
organizationstring–The clinic (Organization) id including its prefix.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
part_statusstring–The patient's participation status, e.g. booked, arrived, cancelled.
patientstring–Patient id.
practitionerstring–Practitioner id, e.g. PR-123.
practitioner_rolestring–PractitionerRole id.
sortstring–Sort order: date, -date ("-" = descending).

No output schema declared.

No examples provided.

halaxy_list_coverage ~291

List or search patients' health fund membership and claim details (HEALTH DATA). Filters combine with AND. Paged: pass next_page as page. GET /main/Coverage.

NameTypeReqDescription
beneficiarystring–The primary beneficiary (a Patient id).
countinteger–Results per page, 1-100 (default 30).
coverage_organizationstring–The coverage organization.
createdstring–Created (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
idstring–One id or several separated by commas, for example 1,2,3.
includearray–Also return related resources in "included": any of Coverage:beneficiary, Coverage:subscriber, Coverage:payor.
last_updatedstring–Only records last updated at this time (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
payorstring–The funder.
sortstring–Sort order: _lastUpdated, created, -_lastUpdated, -created ("-" = descending).
subscriberstring–The subscriber to the policy.
subscriber_idstring–Subscriber (membership) number.

No output schema declared.

No examples provided.

halaxy_list_fees ~252

List or search fees (ChargeItemDefinition): the services and products a practice charges for. Filters combine with AND. Paged: pass next_page as page. GET /main/ChargeItemDefinition.

NameTypeReqDescription
codestring–Fee item number.
context_typestring–Fee type: 0 = appointment, 1 = item, 2 = pro-rata.
countinteger–Results per page, 1-100 (default 30).
createdstring–Created (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
idstring–One id or several separated by commas, for example 1,2,3.
last_updatedstring–Only records last updated at this time (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
property_group_statusstring–Fee pricing status: 1 = current, 2 = archived.
publisherstring–Funder name.
titlestring–Fee name.

No output schema declared.

No examples provided.

halaxy_list_healthcare_services ~173

List or search appointment types used by the practice group, clinics and practitioners. Filters combine with AND. Paged: pass next_page as page. GET /main/HealthcareService.

NameTypeReqDescription
activeboolean–Only active (true) or inactive appointment types.
countinteger–Results per page, 1-100 (default 30).
idstring–One id or several separated by commas, for example 1,2,3.
last_updatedstring–Only records last updated at this time (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
namestring–Appointment type name.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.

No output schema declared.

No examples provided.

halaxy_list_invoice_lines ~288

List or search invoice lines: single fees on invoices. Filters combine with AND. Paged: pass next_page as page. GET /main/InvoiceLine.

NameTypeReqDescription
amountstring–The line amount, optionally with a prefix such as gt100.
countinteger–Results per page, 1-100 (default 30).
coveragestring–The coverage (claim details).
createdstring–Created (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
funderstring–The funder.
idstring–One id or several separated by commas, for example 1,2,3.
includearray–Also return related resources in "included": any of InvoiceLine:subject, InvoiceLine:performer, InvoiceLine:invoice.
invoicestring–The invoice the line belongs to.
last_updatedstring–Only records last updated at this time (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
performerstring–The performer of the service.
referralstring–The referral.
subjectstring–The patient the line is for.

No output schema declared.

No examples provided.

halaxy_list_invoices ~329

List or search invoices of the practice group. Filters combine with AND. Paged: pass next_page as page. GET /main/Invoice.

NameTypeReqDescription
countinteger–Results per page, 1-100 (default 30).
createdstring–Created (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
idstring–One id or several separated by commas, for example 1,2,3.
includearray–Also return related resources in "included": any of Invoice:recipient, Invoice:practitioner.
include_iteratearray–Also return resources related to an included one (needs the matching include): any of PractitionerRole:practitioner, PractitionerRole:organization.
last_updatedstring–Only records last updated at this time (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
organizationstring–The clinic the invoice was created at.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
practitionerstring–Practitioner id.
practitioner_rolestring–PractitionerRole id.
recipientstring–The invoice recipient (a Patient or Organization id).
statusstring–Invoice status.
total_balancestring–Balance owing, optionally with a prefix such as gt0 (finds unpaid invoices).
total_paidstring–Total paid amount, optionally with a prefix such as gt0.

No output schema declared.

No examples provided.

halaxy_list_organizations ~178

List or search the practice group, its clinic locations, funders and external practices (practice group ids look like PG-12345). Filters combine with AND. Paged: pass next_page as page. GET /main/Organization.

NameTypeReqDescription
countinteger–Results per page, 1-100 (default 30).
idstring–One id or several separated by commas, for example 1,2,3.
last_updatedstring–Only records last updated at this time (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
namestring–Organization name.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
profilestring–Only one kind of organization.

No output schema declared.

No examples provided.

halaxy_list_patients ~365

List or search patient records (demographics and contact details; HEALTH DATA). Filters combine with AND. Paged: pass next_page as page. GET /main/Patient.

NameTypeReqDescription
birthdatestring–Date of birth (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
countinteger–Results per page, 1-100 (default 30).
createdstring–Created (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
emailstring–An email address.
familystring–Start of the family name.
general_practitionerstring–A Practitioner/PractitionerRole the patient has records with.
givenstring–Start of the given name.
idstring–One id or several separated by commas, for example 1,2,3.
includearray–Also return related resources in "included": any of Patient:general-practitioner.
last_updatedstring–Only records last updated at this time (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
namestring–Search the family, given or preferred name (matches the start of the name).
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
phonestring–A phone number, local or E.164 (+61412345678).
sortstring–Sort order: _lastUpdated, name, created, -_lastUpdated, -name, -created ("-" = descending).
statusstring–Patient status, e.g. active.

No output schema declared.

No examples provided.

halaxy_list_payment_transactions ~165

List or search payment transactions recorded on invoices. Filters combine with AND. Paged: pass next_page as page. GET /main/PaymentTransaction.

NameTypeReqDescription
countinteger–Results per page, 1-100 (default 30).
createdstring–Created (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
idstring–One id or several separated by commas, for example 1,2,3.
last_updatedstring–Only records last updated at this time (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.

No output schema declared.

No examples provided.

halaxy_list_practitioner_roles ~239

List or search practitioner roles: a practitioner's association with one clinic location (the id used when booking and for clinical notes). Filters combine with AND. Paged: pass next_page as page. GET /main/PractitionerRole.

NameTypeReqDescription
countinteger–Results per page, 1-100 (default 30).
idstring–One id or several separated by commas, for example 1,2,3.
includearray–Also return related resources in "included": any of PractitionerRole:practitioner, PractitionerRole:organization.
last_updatedstring–Only records last updated at this time (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
organizationstring–Organization (clinic) id.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
practitionerstring–Practitioner id, e.g. PR-123.
profilestring–Staff roles or external professional-contact roles.
provider_numberstring–Provider number.

No output schema declared.

No examples provided.

halaxy_list_practitioners ~252

List or search practitioners and administrators of the practice group (ids look like PR-12345). Filters combine with AND. Paged: pass next_page as page. GET /main/Practitioner.

NameTypeReqDescription
activeboolean–Only active (true) or inactive (false) practitioners.
countinteger–Results per page, 1-100 (default 30).
emailstring–An email address.
familystring–Family name.
givenstring–Given name.
idstring–One id or several separated by commas, for example 1,2,3.
last_updatedstring–Only records last updated at this time (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
namestring–Family, given or preferred name.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
profilestring–hx-practitioner = staff, hx-external-practitioner = professional contacts.
sortstring–Sort order: name, -name ("-" = descending).

No output schema declared.

No examples provided.

halaxy_list_referral_definitions ~154

List or search referral templates with preset properties. Filters combine with AND. Paged: pass next_page as page. GET /main/ReferralDefinition.

NameTypeReqDescription
countinteger–Results per page, 1-100 (default 30).
funding_organizationstring–The funder.
idstring–One id or several separated by commas, for example 1,2,3.
last_updatedstring–Only records last updated at this time (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.

No output schema declared.

No examples provided.

halaxy_list_referrals ~250

List or search referrals from one healthcare provider to another (HEALTH DATA). Filters combine with AND. Paged: pass next_page as page. GET /main/Referral.

NameTypeReqDescription
countinteger–Results per page, 1-100 (default 30).
coveragestring–The coverage (claim details) of the referral.
createdstring–Created (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
idstring–One id or several separated by commas, for example 1,2,3.
includearray–Also return related resources in "included": any of Referral:subject, Referral:coverage.
last_updatedstring–Only records last updated at this time (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
sortstring–Sort order: _lastUpdated, created, -_lastUpdated, -created ("-" = descending).
subjectstring–The patient the referral is for.

No output schema declared.

No examples provided.

halaxy_list_schedules ~194

List or search schedules: containers of bookable time slots per practitioner. Filters combine with AND. Paged: pass next_page as page. GET /main/Schedule.

NameTypeReqDescription
activeboolean–Only active (true) or inactive schedules.
actorstring–The practitioner/role the schedule belongs to.
countinteger–Results per page, 1-100 (default 30).
idstring–One id or several separated by commas, for example 1,2,3.
includearray–Also return related resources in "included": any of Schedule:actor.
last_updatedstring–Only records last updated at this time (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.

No output schema declared.

No examples provided.

halaxy_list_slots ~289

List or search time slots of practitioner schedules (free or busy). Filters combine with AND. Paged: pass next_page as page. GET /main/Slot.

NameTypeReqDescription
countinteger–Results per page, 1-100 (default 30).
durationstring–Slot duration in minutes.
endstring–Slot end (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
idstring–One id or several separated by commas, for example 1,2,3.
includearray–Also return related resources in "included": any of Slot:practitioner, Slot:organization, Slot:practitioner-role.
last_updatedstring–Only records last updated at this time (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
organizationstring–Organization (clinic) id.
pageinteger–Page number, 1-based (default 1). Use next_page from the previous reply.
practitionerstring–Practitioner id.
practitioner_rolestring–PractitionerRole id.
schedulestring–Schedule id.
startstring–Slot start (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).
statusstring–free or busy.

No output schema declared.

No examples provided.

halaxy_update_appointment_status ~124

Writes to the live Halaxy account. Sets the patient's status on an appointment (shown in the Halaxy calendar), for example arrived, attended, confirmed or cancelled. "cancelled (no charge)" also sets the invoice to $0. For a group appointment pass patient_id to say whose status changes. PATCH /main/Appointment/{id}.

NameTypeReqDescription
appointment_idstringyesThe appointment id.
patient_idstring–The patient whose status changes (needed only when the appointment has several patients).
statusstringyesThe new status.

No output schema declared.

No examples provided.

Install

How do I install the Halaxy MCP by usefulapi server?

Halaxy MCP by usefulapi is a hosted endpoint at https://halaxy.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · halaxy.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-halaxy 'https://halaxy.usefulapi.io/mcp'
Common questions

What is the Halaxy MCP by usefulapi server?

Halaxy MCP by usefulapi is listed in the public MCP registry as io.usefulapi/halaxy. Read Halaxy patients, appointments, slots and invoices; create patients, appointments and notes. This page covers its hosted endpoint (https://halaxy.usefulapi.io/mcp).

Is the Halaxy MCP by usefulapi server safe to use?

Halaxy MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Halaxy MCP by usefulapi server expose?

Halaxy MCP by usefulapi exposes 35 tools: halaxy_list_patients, halaxy_list_practitioners, halaxy_list_practitioner_roles, halaxy_list_organizations, halaxy_list_appointments, and 30 more. Their descriptions and schemas cost roughly 5,410 tokens of context every time the server is loaded.

Does the Halaxy MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Halaxy MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Halaxy MCP by usefulapi server still maintained?

Halaxy MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.