Travel · Remote MCP server
Tripsy
Plan trips and manage itineraries, stays, transport, activities, expenses, and documents in Tripsy.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.tripsyapp/tripsy- Version
- 2.0.1
- Status
- Active
- Category
- travel
- Transport
- Streamable HTTP
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- tripsyapp (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/tripsyapp) · how
- Website
- tripsy.help/article/97-ai-tools
- Repository
- github.com/tripsyapp/cli
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.tripsy.app | 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 Tripsy
Tripsy is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.tripsy.app, 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, tripsy.help, 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 |
|---|---|
| Tripgain MCP ServerCorporate travel booking and expense management for TripGain, exposed as an MCP server. | Remote · HTTPLive check: sign-in required |
| TriphetuPlan group trips with your AI: itineraries, checklists, shopping, expenses and who owes whom. | Remote · HTTPLive check: sign-in required |
| TripHookFind group trips and day outs to join, events in a city, and where to go by weather and budget. | Remote · HTTPLive check: ✓ handshake |
| TripsHand someone a complete trip as a private, editable map link. No account, no API key, no card. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| TripWaysFind, price, and book tours, day trips, and activities worldwide, with live dates and prices. | Remote · HTTPLive check: ✓ handshake |
| Tripyana London ChauffeurFixed London chauffeur prices: airport & cruise transfers, hourly hire, day trips, booking links. | Remote · HTTPLive check: ✓ handshake |
| trvlDoor-to-door travel MCP + CLI: flights, hotels, trains, cars, ferries. No API keys, Go binary. | Local · stdio |
| TrvlrrYour travel history and upcoming trips: flights, stays, activities, places, photos and stats. | Remote · HTTPLive check: sign-in required |