Travel · Remote MCP server
Traveler.md
A traveler's portable travel profile and trip plans. It remembers, it does not search or book.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
md.traveler/mcp- Version
- 1.0.1
- Status
- Active
- Category
- travel
- Transport
- Streamable HTTP
- Published
- 2026-08-28
- Updated
- 2026-08-28
- Publisher
- md.traveler
- Namespace
- Namespace verified by the MCP Registry via the domain traveler.md · how
- Website
- traveler.md
- Repository
- github.com/TravelAiSolution/traveler-md-mcp-registry
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.traveler.md/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Traveler.md
Traveler.md is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.traveler.md/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, traveler.md, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More travel servers
| Server | Runs |
|---|---|
| Travel MCP ServerBooking.com, Airbnb, TripAdvisor unified - for AI travel concierges and trip planners. | Remote · HTTPLive check: sign-in required |
| Travel Per Diem & Allowance CalculatorCompliant per diems in one call: official US GSA, German BMF and UK HMRC rates, with a trip… | Remote · HTTPLive check: ✓ handshake |
| Travel Trends MCPEuropean tourism & travel-disruption MCP: trip risk, live events, Eurostat panels, RO county data. | Remote · HTTPLive check: ✓ handshake |
| travel.artArt-tourism data for AI agents: biennales, art fairs, museums, layover itineraries with 2026 facts. | Remote · HTTPLive check: ✓ handshake |
| TravelerLocal - China travel facts for foreign visitorsField-verified China travel facts for foreign visitors: booking walls, hotel registration, transit. | Remote · HTTPLive check: ✓ handshake |
| Travellers Group - Regional Australia HotelsVerified facts and direct-booking handoff for five Travellers Group hotels in regional Australia. | Remote · HTTPLive check: ✓ handshake |
| travelMCP DirectorySearch MCP servers, agent skills and APIs for travel: hotel ID mapping, rates, rooms. | Remote · HTTPLive check: ✓ handshake |
| TravelMind MCPTravelMind: 8 MCP tools for travel (12306 trains, flights, hotels, geocode, planning, policy). | Remote · HTTPLive check: sign-in required |