Home / MCP registry index / io.usefulapi/halaxy

Halaxy MCP by usefulapi

io.usefulapi/halaxy in the official MCP registry. Endpoint https://halaxy.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Read Halaxy patients, appointments, slots and invoices; create patients, appointments and notes.

We read its 35 tools on 2026-11-01. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

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

Cursor: ~/.cursor/mcp.json

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

VS Code

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

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

halaxy_list_patients halaxy_list_practitioners halaxy_list_practitioner_roles halaxy_list_organizations halaxy_list_appointments halaxy_list_schedules halaxy_list_slots halaxy_list_healthcare_services halaxy_list_fees halaxy_list_coverage halaxy_list_invoices halaxy_list_invoice_lines halaxy_list_payment_transactions halaxy_list_referrals halaxy_list_referral_definitions halaxy_get_patient halaxy_get_practitioner halaxy_get_practitioner_role halaxy_get_organization halaxy_get_appointment halaxy_get_schedule halaxy_get_slot halaxy_get_healthcare_service halaxy_get_fee halaxy_get_coverage halaxy_get_invoice halaxy_get_invoice_line halaxy_get_payment_transaction halaxy_get_referral halaxy_get_referral_definition halaxy_find_available_appointments halaxy_create_patient halaxy_create_appointment halaxy_update_appointment_status halaxy_create_clinical_note

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-01): 4b6a322af7b5298e. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-halaxy/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-halaxy)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.