HealthPass runs a remote Model Context Protocol (MCP) server. With it, an assistant such as Claude or ChatGPT can find travel-health doctors and clinics that a person at HealthPass has checked, point to the official health requirements for a destination, and hand over a doctor it found elsewhere.
The assistant finds, HealthPass books. No tool books, sends or confirms an appointment. Every answer contains a link to HealthPass, where the traveller signs in, checks the doctor and sends the request.
https://travelhealthpass.app/mcp{
"mcpServers": {
"healthpass": { "type": "http", "url": "https://travelhealthpass.app/mcp" }
}
}
find_travel_health_provider (read-only)country (ISO code), city,
lat/lng (nearest first), service
and language. Each result carries its page and, where the
practice accepts requests, a HealthPass request link. Order never
depends on payment.
get_provider (read-only)get_destination_requirements (read-only)prepare_appointment
Service codes: travel-consultation, vaccination,
yellow-fever, malaria-prophylaxis,
fitness-to-fly, medication-letter,
chronic-condition-travel, post-travel,
foreign-patients, telemedicine.
Reason codes: pre-travel, vaccination,
chronic-condition, fitness-to-fly,
during-trip, post-travel.
The tools have no field for a name, diagnosis, condition or medication, and assistants are asked not to pass any. Whether a traveller shares their health record with a doctor, and which parts, is decided on HealthPass after sign-in. See the privacy policy, section 12.
support@travelhealthpass.app · Privacy policy · Terms · Imprint
HealthPass is operated by Centrafox Consulting LLC. A practice that does not want requests can reply to any request email, and we stop.