Listing rules
To be listed on MCPHub.travel a travel MCP server must answer when we call it, publish a valid tool schema, document its access model clearly — public, your own account with the provider, or a partner agreement — and belong to one of the eight travel categories we track. That is the whole bar. Listing is free, placement is not for sale, and a community-built server is listed on the same terms as one a vendor runs; we publish which is which and let the reader decide. We test the endpoint by hand before listing it, read the schema to populate your entry, and re-check afterwards. A server that stops answering is marked rather than removed silently, because what stopped working is information the people relying on it need. Submit one at mcphub.travel/submit.
These rules exist so that a reader can trust the catalog without testing every entry themselves. Everything below is something we can check by calling your server.
To be listed, your server must
- Answer live. We call your endpoint before listing it, and periodically after — if it stops responding, we mark it accordingly rather than removing it silently. Give us a stable URL rather than a demo instance you plan to move; a server that changes address quietly is indistinguishable from one that broke.
- Publish a valid tool schema. We read it to populate your catalogue entry and to keep your listed tool count accurate. Tool names and descriptions should say what the tool actually does, in words a stranger would understand — they are what an assistant reads when it decides whether to call you, so a vague description costs you calls before anyone sees your listing.
- Document its access model clearly: public, requires the user’s own account with your service, or a partner agreement. We show this on your listing so people know what to expect before they connect. If a server is public for reads and gated for anything else, say so — we will list the honest version rather than the flattering one.
- Belong to travel. We list servers serving one of our categories — flights, stays, activities and tours, cars and ground transport, eSIM and data, visas and entry, delay compensation, or a clear “everything else” travel use. A general-purpose tool with a travel example in its README is not a travel server; a currency converter a traveller genuinely reaches for is.
What “answers live” means in practice
It means we call your real endpoint and publish what came back — not what the documentation promises, not what a registry entry says. The status on your listing is a measurement with a date on it. That is the same standard every entry in the catalog is held to, including the ones we run ourselves.
If your server needs credentials to answer at all, tell us at submission. We would rather list it accurately as gated than have it show up as unreachable because we called it the wrong way.
What we publish, and what we do not
We publish your name, what the server does, its category, access model and provenance, the tools your schema declares, and the result of the last check. We do not publish rankings we were paid for, because there are none. We do not quietly drop a listing that broke, and we do not describe a server as live when it did not answer.
Provenance is stated plainly: official where the vendor runs the server, community where an independent author does. Neither is a judgement. Both are listed the same way, and both are checked the same way.
We’ll remove or flag a listing that
- Stops answering for an extended period without explanation.
- Materially misrepresents its tool schema or access model.
- Charges through the connection in a way its listing does not disclose.
- Violates these rules or our Terms of Service.
Revenue share
Where a listing generates booking revenue through MCPHub.travel, the share is set out in a separate agreement with the vendor — not a fixed public rate at this stage. No server on this site takes a booking itself: they return live options and booking links, and the transaction happens on the provider’s own site under the provider’s terms.
Before you submit
Have the endpoint URL, the access model, the category you think you belong in, and a contact address we can use when something stops answering. If your server covers a category that is currently empty — stays, eSIM and data, or delay compensation — say so, because those are the submissions we look at first.
Submit a server when you are ready. Questions: partnerships@mcphub.travel.
By what a trip is made of
100+ travel MCP servers across 8 categories. One page each, including the ones with nothing in them — that is information too.
- Flights4 live
- Stays3 live
- Activities & tours5 live
- Cars & ground5 live
- eSIM & datanone live
- Visas & entry3 live
- Delay compensationnone live
- Everything else7 live
Questions people ask
- What happens if my server goes down?
- We mark it. Removing a listing silently would hide the outage from the people relying on it, and hide from you that we noticed. When it answers again, the status goes back on its own.
- Is there a fee to be listed?
- No. Listing is free and placement is not for sale — the order in the catalog comes from access model and status, never from payment. Where a listing generates booking revenue through MCPHub.travel, the share is set out in a separate agreement with the vendor, not a fixed public rate at this stage.
- How long does it take?
- We test the endpoint by hand before listing it, so it depends on how quickly it answers and how clear the schema is. A server that responds to an anonymous call with a readable schema is the fast case; one that needs credentials arranged takes longer.
- Does my server have to be public?
- No. We list servers that need your own account with the provider, and servers behind a partner agreement, alongside public ones. What matters is that the access model is stated up front so nobody connects expecting something else.
- Do you list community servers, or only official ones?
- Both, on the same terms. We publish provenance — official where the vendor runs it, community where an independent author does — because it tells a reader who owns the roadmap, not who is better.
- What do you publish about my server?
- Your name, what the server does, its category, its access model, its provenance, the tools your schema declares, and whether it answered at our last check. The description and tool count come from your own schema, so keeping that accurate keeps your listing accurate.
- How do I update or remove my listing?
- Email partnerships@mcphub.travel. Schema changes are picked up when we re-read your endpoint, so a renamed or added tool usually needs nothing from you at all.