Home / MCP registry index / com.xonark/dental-gateway
Xona Dental Gateway
com.xonark/dental-gateway in the official MCP registry.
Endpoint https://book.xonark.com/mcp.
The registry describes it as: Find Canadian dentists; send an appointment request or book with a connected practice.
We read its 20 tools on 2026-10-28. 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.
Tools it advertises
search_canadian_dentists get_canadian_dental_practice answer_dental_practice_question list_dental_practice_actions prepare_dental_practice_action get_dental_action_status list_public_booking_services list_public_booking_slots choose_public_booking_time start_dental_request confirm_dental_request list_xona_booking_services list_xona_booking_slots hold_xona_booking_slot confirm_xona_booking abandon_xona_booking start_xona_appointment_access list_xona_appointments list_xona_reschedule_times change_xona_appointment
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-xonark-dental-gateway)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.