Travel · Remote MCP server
TravelMindsAI Concierge
Grounded, multilingual travel data + a cited travel concierge. 12+ languages, deep India coverage.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.travelminds/concierge- Version
- 1.0.0
- Status
- Active
- Category
- travel
- Transport
- Streamable HTTP
- Published
- 2026-05-30
- Updated
- 2026-05-30
- Publisher
- ai.travelminds
- Namespace
- Namespace verified by the MCP Registry via the domain travelminds.ai · how
- Website
- travelminds.ai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.travelminds.ai/mcp | Authorization (secret) |
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 530)
- Handshake
- HTTP 530
- Checked on
- 2026-10-05
How to connect TravelMindsAI Concierge
TravelMindsAI Concierge is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.travelminds.ai/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.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
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, travelminds.ai, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | No real file found |
/.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 |
|---|---|
| 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 |
| TravelOwlPlan trips directly into TravelOwl from a conversation with Claude. | Remote · HTTPLive check: sign-in required |
| TravelpayoutsTravelpayouts MCP - wraps the Aviasales Flights Data API (travelpayouts.com) | Remote · HTTPLive check: ✓ handshake |
| Travelpayouts MCPMCP server for Travelpayouts API -- flight search, popular routes, price calendar. | Local · stdio |
| TravolpTravel planner: create, edit, and explore trip itineraries from your Travolp AI assistant. | Remote · HTTPLive check: sign-in required |