MCP server · registry snapshot 2026-10-27 · last tested 2026-10-27

io.usefulapi/halaxy

Halaxy MCP by usefulapi — the publisher's title

by usefulapi.io · domain (the registry's namespace rule)repository owner on GitHub: m190 (personal account)Source ↗Website ↗

Read Halaxy patients, appointments, slots and invoices; create patients, appointments and notes. — the publisher's description

4 of 4 record checks metRead-only · tools listed 2026-10-27version 1.1.0JavaScriptstreamable HTTP35 tools

Summary

io.usefulapi/halaxy is a remote MCP server listed in the official MCP registry at version 1.1.0, under the namespace of the domain usefulapi.io. Its linked repository is github.com/m190/usefulapi-mcp; GitHub reports its owner as m190, a personal account. On 2026-10-27 ProtocolProbe connected to it in read-only mode and read its inventory: 35 tools, 0 resources and 1 prompt.

Record checks

4 of 4 record checks met · 4 do not apply · 1 not checked

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not checked: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Your own values: none declared (not a guarantee)
Sign-in: none needed to open a session
Repository: public
Tools: 35
Last tested: 2026-10-27

Tool list size

22,430 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (35 tools). Counted with Anthropic's token counter on 2026-10-27, from the tool list we read on 2026-10-27. Median across 23,424 counted servers: 2,725 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-10-27 (halaxy.usefulapi.io), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.1.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 4 tools whose name or declaration suggests they change data (halaxy_create_patient, halaxy_create_appointment, halaxy_update_appointment_status, halaxy_create_clinical_note). That is our reading of the names; we did not call them. Source: our connection, 2026-10-27.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-27

Mode

read-only (no tool calls)

Latest version

1.1.0, published 2026-10-27 (registry, as of the 2026-10-27 snapshot)

First listed version

2026-10-26 (earliest version still in the registry; older removed versions would be earlier)

Version history

2 versions listed, 2026-10-26 to 2026-10-27; 2 in the 90 days before the 2026-10-27 snapshot.

Most recent 2 versions

1.1.0 · 2026-10-27
1.0.0 · 2026-10-26

(versions still listed in the registry only)

Registry data

snapshot 2026-10-27

Package and repository

checked 2026-10-27

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 1.0.0 (published 2026-10-26) → 1.1.0 (published 2026-10-27), between the registry lists of 2026-10-26 and 2026-10-27.

The publisher published no GitHub release note for this version: its repository publishes no GitHub releases.

Source: the official MCP Registry list on 2026-10-26 and on 2026-10-27; release notes from the GitHub Releases API, checked 2026-10-27.

What it is

What does this server offer?

Observed inventory

35tools

0resources

1prompts

None of its 35 tools are described as changing anything. For 35 the reading was uncertain, so no mark is shown.

halaxy_list_patients
“List or search patient records (demographics and contact details; HEALTH DATA).”
Publisher declares: read-only yes
15 inputs
- namestring“Search the family, given or preferred name (matches the start of the name).”
- familystring“Start of the family name.”
- givenstring“Start of the given name.”
- emailstring“An email address.”
- phonestring“A phone number, local or E.164 (+61412345678).”
- statusstring“Patient status, e.g.”
- birthdatestring“Date of birth (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).”
- createdstring“Created (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).”
- general_practitionerstring“A Practitioner/PractitionerRole the patient has records with.”
- 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).”
- sortstring“Sort order: _lastUpdated, name, created, -_lastUpdated, -name, -created ("-" = descending).”
- includearray“Also return related resources in "included": any of Patient:general-practitioner.”
- pageinteger“Page number, 1-based (default 1).”
- countinteger“Results per page, 1-100 (default 30).”
halaxy_list_practitioners
“List or search practitioners and administrators of the practice group (ids look like PR-12345).”
Publisher declares: read-only yes
11 inputs
- namestring“Family, given or preferred name.”
- familystring“Family name.”
- givenstring“Given name.”
- emailstring“An email address.”
- activeboolean“Only active (true) or inactive (false) practitioners.”
- profilestring“hx-practitioner = staff, hx-external-practitioner = professional contacts.”
- 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).”
- sortstring“Sort order: name, -name ("-" = descending).”
- pageinteger“Page number, 1-based (default 1).”
- countinteger“Results per page, 1-100 (default 30).”
halaxy_list_practitioner_roles
“List or search practitioner roles: a practitioner's association with one clinic location (the id used when booking and for clinical notes).”
Publisher declares: read-only yes
9 inputs
- practitionerstring“Practitioner id, e.g.”
- organizationstring“Organization (clinic) id.”
- provider_numberstring“Provider number.”
- profilestring“Staff roles or external professional-contact roles.”
- 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).”
- includearray“Also return related resources in "included": any of PractitionerRole:practitioner, PractitionerRole:organization.”
- pageinteger“Page number, 1-based (default 1).”
- countinteger“Results per page, 1-100 (default 30).”
halaxy_list_organizations
“List or search the practice group, its clinic locations, funders and external practices (practice group ids look like PG-12345).”
Publisher declares: read-only yes
6 inputs
- namestring“Organization name.”
- profilestring“Only one kind of organization.”
- 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).”
- countinteger“Results per page, 1-100 (default 30).”
halaxy_list_appointments
“List or search appointments (HEALTH DATA: names the patient).”
Publisher declares: read-only yes
14 inputs
- datestring“Appointment date/time (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).”
- createdstring“Created (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).”
- part_statusstring“The patient's participation status, e.g.”
- patientstring“Patient id.”
- practitionerstring“Practitioner id, e.g.”
- practitioner_rolestring“PractitionerRole id.”
- organizationstring“The clinic (Organization) id including its prefix.”
- 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).”
- sortstring“Sort order: date, -date ("-" = descending).”
- 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.”
- pageinteger“Page number, 1-based (default 1).”
- countinteger“Results per page, 1-100 (default 30).”
halaxy_list_schedules
“List or search schedules: containers of bookable time slots per practitioner.”
Publisher declares: read-only yes
7 inputs
- activeboolean“Only active (true) or inactive schedules.”
- actorstring“The practitioner/role the schedule belongs to.”
- 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).”
- includearray“Also return related resources in "included": any of Schedule:actor.”
- pageinteger“Page number, 1-based (default 1).”
- countinteger“Results per page, 1-100 (default 30).”
halaxy_list_slots
“List or search time slots of practitioner schedules (free or busy).”
Publisher declares: read-only yes
13 inputs
- durationstring“Slot duration in minutes.”
- statusstring“free or busy.”
- practitionerstring“Practitioner id.”
- organizationstring“Organization (clinic) id.”
- practitioner_rolestring“PractitionerRole id.”
- startstring“Slot start (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).”
- endstring“Slot end (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).”
- schedulestring“Schedule id.”
- 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).”
- includearray“Also return related resources in "included": any of Slot:practitioner, Slot:organization, Slot:practitioner-role.”
- pageinteger“Page number, 1-based (default 1).”
- countinteger“Results per page, 1-100 (default 30).”
halaxy_list_healthcare_services
“List or search appointment types used by the practice group, clinics and practitioners.”
Publisher declares: read-only yes
6 inputs
- activeboolean“Only active (true) or inactive appointment types.”
- namestring“Appointment type 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).”
- pageinteger“Page number, 1-based (default 1).”
- countinteger“Results per page, 1-100 (default 30).”
halaxy_list_fees
“List or search fees (ChargeItemDefinition): the services and products a practice charges for.”
Publisher declares: read-only yes
10 inputs
- context_typestring“Fee type: 0 = appointment, 1 = item, 2 = pro-rata.”
- property_group_statusstring“Fee pricing status: 1 = current, 2 = archived.”
- createdstring“Created (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).”
- titlestring“Fee name.”
- publisherstring“Funder name.”
- codestring“Fee item number.”
- 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).”
- countinteger“Results per page, 1-100 (default 30).”
halaxy_list_coverage
“List or search patients' health fund membership and claim details (HEALTH DATA).”
Publisher declares: read-only yes
12 inputs
- beneficiarystring“The primary beneficiary (a Patient id).”
- subscriberstring“The subscriber to the policy.”
- payorstring“The funder.”
- coverage_organizationstring“The coverage organization.”
- subscriber_idstring“Subscriber (membership) number.”
- 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).”
- sortstring“Sort order: _lastUpdated, created, -_lastUpdated, -created ("-" = descending).”
- includearray“Also return related resources in "included": any of Coverage:beneficiary, Coverage:subscriber, Coverage:payor.”
- pageinteger“Page number, 1-based (default 1).”
- countinteger“Results per page, 1-100 (default 30).”
halaxy_list_invoices
“List or search invoices of the practice group.”
Publisher declares: read-only yes
14 inputs
- createdstring“Created (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).”
- recipientstring“The invoice recipient (a Patient or Organization id).”
- practitionerstring“Practitioner id.”
- practitioner_rolestring“PractitionerRole id.”
- organizationstring“The clinic the invoice was created at.”
- statusstring“Invoice status.”
- total_paidstring“Total paid amount, optionally with a prefix such as gt0.”
- total_balancestring“Balance owing, optionally with a prefix such as gt0 (finds unpaid invoices).”
- 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).”
- 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.”
- pageinteger“Page number, 1-based (default 1).”
- countinteger“Results per page, 1-100 (default 30).”
halaxy_list_invoice_lines
“List or search invoice lines: single fees on invoices.”
Publisher declares: read-only yes
13 inputs
- createdstring“Created (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).”
- subjectstring“The patient the line is for.”
- performerstring“The performer of the service.”
- invoicestring“The invoice the line belongs to.”
- funderstring“The funder.”
- referralstring“The referral.”
- coveragestring“The coverage (claim details).”
- amountstring“The line amount, optionally with a prefix such as gt100.”
- 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).”
- includearray“Also return related resources in "included": any of InvoiceLine:subject, InvoiceLine:performer, InvoiceLine:invoice.”
- pageinteger“Page number, 1-based (default 1).”
- countinteger“Results per page, 1-100 (default 30).”

Show 23 more tools

halaxy_list_payment_transactions
“List or search payment transactions recorded on invoices.”
Publisher declares: read-only yes
5 inputs
- 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).”
- countinteger“Results per page, 1-100 (default 30).”
halaxy_list_referrals
“List or search referrals from one healthcare provider to another (HEALTH DATA).”
Publisher declares: read-only yes
9 inputs
- subjectstring“The patient the referral is for.”
- 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.”
- last_updatedstring“Only records last updated at this time (ISO date or date-time, optional prefix eq/ne/gt/lt/ge/le).”
- sortstring“Sort order: _lastUpdated, created, -_lastUpdated, -created ("-" = descending).”
- includearray“Also return related resources in "included": any of Referral:subject, Referral:coverage.”
- pageinteger“Page number, 1-based (default 1).”
- countinteger“Results per page, 1-100 (default 30).”
halaxy_list_referral_definitions
“List or search referral templates with preset properties.”
Publisher declares: read-only yes
5 inputs
- 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).”
- countinteger“Results per page, 1-100 (default 30).”
halaxy_get_patient
“Fetch a patient record (HEALTH DATA) by id.”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“The Patient id (from the matching list tool).”
halaxy_get_practitioner
“Fetch a practitioner or administrator by id.”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“The Practitioner id (from the matching list tool).”
halaxy_get_practitioner_role
“Fetch a practitioner role at a clinic location by id.”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“The PractitionerRole id (from the matching list tool).”
halaxy_get_organization
“Fetch a practice group, clinic, funder or external practice by id.”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“The Organization id (from the matching list tool).”
halaxy_get_appointment
“Fetch an appointment with its participants and statuses (HEALTH DATA) by id.”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“The Appointment id (from the matching list tool).”
halaxy_get_schedule
“Fetch a practitioner schedule by id.”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“The Schedule id (from the matching list tool).”
halaxy_get_slot
“Fetch a time slot by id.”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“The Slot id (from the matching list tool).”
halaxy_get_healthcare_service
“Fetch an appointment type by id.”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“The HealthcareService id (from the matching list tool).”
halaxy_get_fee
“Fetch a fee (ChargeItemDefinition) by id.”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“The ChargeItemDefinition id (from the matching list tool).”
halaxy_get_coverage
“Fetch a patient's coverage (claim details) record by id.”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“The Coverage id (from the matching list tool).”
halaxy_get_invoice
“Fetch an invoice by id.”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“The Invoice id (from the matching list tool).”
halaxy_get_invoice_line
“Fetch an invoice line by id.”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“The InvoiceLine id (from the matching list tool).”
halaxy_get_payment_transaction
“Fetch a payment transaction by id.”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“The PaymentTransaction id (from the matching list tool).”
halaxy_get_referral
“Fetch a referral (HEALTH DATA) by id.”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“The Referral id (from the matching list tool).”
halaxy_get_referral_definition
“Fetch a referral template by id.”
Publisher declares: read-only yes
1 input, 1 required
- idstringrequired“The ReferralDefinition id (from the matching list tool).”
halaxy_find_available_appointments
“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).”
Publisher declares: read-only yes
10 inputs, 3 required
- startstringrequired“Start of the search window, e.g.”
- endstringrequired“End of the search window, e.g.”
- durationintegerrequired“Appointment length in minutes.”
- practitionerstring“Practitioner id.”
- practitioner_rolestring“PractitionerRole id.”
- organizationstring“Organization (clinic) id.”
- showstring“first-available = only the first available time.”
- emergencyboolean“true ignores lead time, to show all times for emergency appointments.”
- apply_buffer_timeboolean“true applies buffer time to show all available times.”
- sortstring“start or -start.”
halaxy_create_patient
“Writes to the live Halaxy account.”
Publisher declares: read-only no · destructive no
9 inputs, 2 required
- familystringrequired“Legal family name (surname).”
- givenstringrequired“Legal given name.”
- preferred_namestring“Preferred (usual) given name.”
- emailstring“Email address.”
- mobilestring“Mobile number as +{country code}{number}, no spaces.”
- genderstring“Gender as registered in government records.”
- birth_datestring“Date of birth, YYYY-MM-DD.”
- addressobject“Mailing address.”
- managing_organizationstring“The practice group id, e.g.”
halaxy_create_appointment
“Writes to the live Halaxy account.”
Publisher declares: read-only no · destructive no
8 inputs, 4 required
- patient_idstringrequired“The patient id.”
- practitioner_role_idstringrequired“The PractitionerRole id (practitioner at a clinic), e.g.”
- startstringrequired“Start with the time zone offset, e.g.”
- endstringrequired“End with the time zone offset, e.g.”
- healthcare_service_idstring“The appointment type id (halaxy_list_healthcare_services).”
- charge_item_definition_idstring“The fee id (halaxy_list_fees) booked for the appointment.”
- statusstring“Initial status (default booked).”
- fail_on_double_bookingboolean“Refuse if the practitioner already has an appointment then (default true).”
halaxy_update_appointment_status
“Writes to the live Halaxy account.”
Publisher declares: destructive yes · idempotent yes
3 inputs, 2 required
- appointment_idstringrequired“The appointment id.”
- statusstringrequired“The new status.”
- patient_idstring“The patient whose status changes (needed only when the appointment has several patients).”
halaxy_create_clinical_note
“Writes to the live Halaxy account.”
Publisher declares: read-only no · destructive no
4 inputs, 4 required
- patient_idstringrequired“The patient the note is for.”
- practitioner_role_idstringrequired“The PractitionerRole id of the author, e.g.”
- titlestringrequired“The note title.”
- htmlstringrequired“The note body as HTML.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-27.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 100% of 198
Tools with a description: 100% of 35
Typical description length: 142 characters

The tool set

Counted from the listing

Tools: 35
Size of the list: about 11,719 tokens for an agent to load (characters ÷ 4)
Naming: 35 of 35 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 35 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-27 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://halaxy.usefulapi.io/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "halaxy": {
      "url": "https://halaxy.usefulapi.io/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "halaxy": {
      "type": "http",
      "url": "https://halaxy.usefulapi.io/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"halaxy","type":"http","url":"https://halaxy.usefulapi.io/mcp"}'

Claude Code

claude mcp add --transport http halaxy https://halaxy.usefulapi.io/mcp

Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)

{
  "mcpServers": {
    "halaxy": {
      "type": "streamableHttp",
      "url": "https://halaxy.usefulapi.io/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project

{
  "mcpServers": {
    "halaxy": {
      "httpUrl": "https://halaxy.usefulapi.io/mcp"
    }
  }
}

OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project

[mcp_servers.halaxy]
url = "https://halaxy.usefulapi.io/mcp"

Zed · Zed settings file (command: zed: open settings file)

{
  "context_servers": {
    "halaxy": {
      "url": "https://halaxy.usefulapi.io/mcp"
    }
  }
}

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://halaxy.usefulapi.io/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint halaxy.usefulapi.io/mcp	Session opened	matches	our test · 2026-10-27
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-27
Repository github.com/m190/usefulapi-mcp	Opens publicly	matches	api.github.com · 2026-10-27

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.usefulapi · 462 servers
GitHub owner: a personal account (m190)

Repository: github.com/m190/usefulapi-mcp
Stars: 0
Repository age: 91–180 days
Last push: 0–30 days ago
Archived: no

Source: the registry entry and api.github.com · 2026-10-27.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Tool list changes

Our reads compared · no tool called

Hosted endpoint halaxy.usefulapi.io/mcp

No change in the tool list across 2 reads (2026-10-26 to 2026-10-27; versions 1.0.0 to 1.1.0).

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-10-27 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

4 of 4 record checks met · 4 do not apply · 1 not checked

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-27. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.usefulapi/halaxy

Answered from the data above

Who publishes io.usefulapi/halaxy?

The registry ties the namespace io.usefulapi to the domain usefulapi.io; only its owner can publish under it. Its linked repository is github.com/m190/usefulapi-mcp; GitHub reports its owner as m190, a personal account. These are facts from the registry and GitHub, not a rating.

Is io.usefulapi/halaxy safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.usefulapi/halaxy need an API key or sign-in?

It opened a session without any credential on 2026-10-27. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.usefulapi/halaxy been security tested?

Partly. 3 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

Where is the source code of io.usefulapi/halaxy?

In github.com/m190/usefulapi-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-27

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not run · an error was returned
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

3 exercised13 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 13

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server returned an error when its prompts were read.not run · an error was returned
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 2

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-27, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
162 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 35 tools, 0 resources, 1 prompt.
2,330 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in the weekly update

listed 2026-10-27; not classified yet

Pricing modelAI-classified

pending: added in the weekly update

the website is not read yet

Programming language

JavaScript

api.github.com · 2026-10-27

Hosting type

remote (hosted by the publisher)

registry · 2026-10-27

MCP capability

prompts, tools

our test · 2026-10-27

Transport

streamable HTTP

registry · 2026-10-27

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-27

Lifecycle status

active

registry · 2026-10-27

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: a personal account · repository age: 91–180 days · stars: 0–9

api.github.com · 2026-10-27

Maintenance

active

api.github.com · 2026-10-27

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.usefulapi/halaxy: MCP server record.” Data checked 2026-10-27. https://protocolprobe.com/mcp/servers/io.usefulapi/halaxy

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.usefulapi/halaxy)](https://protocolprobe.com/mcp/servers/io.usefulapi/halaxy)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology