The medical-tourism
data layer, built
for AI agents.
880 accredited clinics across 13 countries, verified weekly, exposed as a Model Context Protocol server. Plug MedX into your Claude or ChatGPT agent in four lines of config — and answer patient questions with sourced, current, citable facts.
# user prompt > Knee replacement in Türkiye under £6,000? # agent calls medx via mcp call medx.clinic_search( country: "TR", procedure: "knee-replacement", max_price: 6000, currency: "GBP" ) # 200 OK · 12 results · 142ms [ { "slug": "acibadem-maslak", "name": "Acibadem Maslak", "city": "Istanbul, Türkiye", "accreditation": ["JCI"], "price_from": { "GBP": 5400 }, "last_verified": "2026-05-11", "source": "clinic-published" }, … ]
Works with every MCP-compatible agent
WHAT YOUR AGENT GETS
Three things the public web can’t reliably give you.
Verified facts, structured the same way every time, dated, with provenance. Designed so an agent can cite a clinic instead of paraphrasing one.
Verified accreditation status
JCI, ISO 9001, national regulator. Each record carries its source and verification date — never a marketing claim.
Clinic-published pricing
Treatment prices direct from each clinic, refreshed weekly, in patient currency. Ranges where the clinic publishes them, “estimate” where we infer.
Geographic + regulatory metadata
City, country, coordinates, regulatory body, climate, common procedures. Every record reads the same shape, so your agent can compare.
MCP IN 60 SECONDS
Four lines, then your agent can answer real patient questions.
Add the MedX MCP server to your Claude Desktop, Cursor, or any MCP-compatible client. Authentication is a single bearer token from the dashboard. No SDK to install, no schema to memorise — the agent discovers tools at runtime.
Add the server block to your client config.
Set MEDX_API_KEY from your dashboard.
Restart the agent — tools appear automatically.
Ask a question. The agent calls clinic_search, returns sourced JSON.
{ "mcpServers": { "medx": { "command": "npx", "args": ["-y", "@medxcare/mcp"], "env": { "MEDX_API_KEY": "mx_live_***" } } } } # tools available after restart: # clinic_search, clinic_detail, # procedure_detail, destination_search, # methodology_for_field
BUILT FOR
The four teams already using MedX.
AI agents · developers
Health-and-travel agents
Claude, ChatGPT, and Cursor builds that recommend clinics, plan medical-tourism trips, or answer patient questions. MCP-native; no scraping, no hallucinated accreditation claims.
Insurers
Underwriting & policy referral
Look up clinic-level accreditation, outcome data, and refresh dates inside your underwriting workflow. Refer policyholders to verified clinics with a structured handoff.
Employers
International benefits platforms
Embed verified clinic access in your global benefits portal. Bulk vouchers, per-country routing, and country-aware pricing in one API.
Researchers
Pricing benchmarks & market intel
Quarterly licence to the full dataset for healthcare-economics research, journalism, or competitive analysis. CSV / JSON dumps with full versioning.
HOW THE DATA IS MADE
Provenance over reach.
We index only clinics we can verify against a primary source. Every record carries its provenance and a date. If we can’t verify it, it’s not in the catalogue.
Re-verification cadence
Each clinic re-checked weekly against its primary source. Stale records are flagged before they hit your agent.
Accreditation sources
Direct from JCI, ISO 9001, and national regulators (TITCK, NEAK, MFDS, COFEPRIS, …). Never paraphrased from clinic marketing copy.
Pricing provenance
Four labelled levels: clinic-confirmed, clinic-published, estimate, and time-locked. Always returned with the price.
What we don’t store
No patient identity, no clinical history, no payments. MedX is a clinic catalogue, not a medical record.
Schema.org JSON-LD
Every public page emits MedicalOrganization, MedicalProcedure, Place, and Offer schema. Discoverable by any structured-data crawler.
Versioned + dated
Every API response includes verified_at and dataset_version. Cite a clinic the way you’d cite a paper.
PRICING
Transparent tiers. Real numbers.
Build for free. Pay when you ship. Enterprise terms when you need a data licence or a private SLA.
Developer
Building or evaluating
- 1,000 requests / month
- MCP server access
- Catalogue & search
- Community Slack
- Watermarked attribution
Starter
Indie agents & small tools
- 50,000 requests / month
- MCP + REST + GraphQL
- Same-day support
- Remove attribution
- Webhooks on re-verification
Pro
Production agents & platforms
- 500,000 requests / month
- Priority MCP routing
- 99.9% SLA
- Audit log export
- Dedicated engineer Slack
- Bring-your-own-clinic upserts
Enterprise
Insurers, employers, data licences
- Custom volume & SLA
- Full data-licence options
- Private MCP deployment
- BAA, DPA, custom contracts
- Procurement support
- On-site integration time
All paid tiers include MCP and REST access, the same dataset, and the same verification cadence. Volume is the only difference — never the data quality.
COMPLIANCE
Built for regulated workflows.
We don’t store clinical data. We do offer the paperwork your procurement team will ask for.
GDPR
ICO ZA…
SOC 2
Type II
DPA
Available
Status
99.97% uptime
Ship an agent that doesn’t make things up about medicine.
Get an API key in 60 seconds. Free up to 1,000 requests a month. No card.