My Next Adventure MCP server
online · 100% uptimecloud.mynextadventure/trip-planner·v1.0.1Create trips, compare variants side by side, and add accommodation, transport and event options.
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed My Next Adventure yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
My Next Adventure tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How My Next Adventure compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 97/100
- higher than 98% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 384 ms
- faster than 38% of 30,031 servers
Release history: 2 versions in the registry since 2026-07-31, latest 2026-10-05, typically one every 66 days.
Install My Next Adventure in Claude Code, Cursor or VS Code
claude mcp add --transport http trip-planner https://mcp.mynextadventure.cloud/mcp
What the publisher says
From the My Next Adventure repository's README, as published. We do not edit it. Read it on GitHub
MyNextAdventure MCP server
A remote Model Context Protocol server that lets an AI assistant plan trips in MyNextAdventure — create a trip, lay out the itinerary, propose flights and hotels, add things to do, and share the result.
It runs as a stateless Cloudflare Worker and is a thin, authenticated proxy in front of the MyNextAdventure public API: it holds no trip data of its own, and forwards every call to the API under the caller's own API key.
- Production: https://mcp.mynextadventure.cloud/mcp (Streamable HTTP)
- Upstream API: https://api.mynextadventure.cloud (v1 public API)
Authentication
Every request needs a MyNextAdventure API key. Create one in the app under Settings → API keys, then send it as either:
- Authorization: Bearer — what most MCP clients send, and what mcp-remote does, or
- X-API-Key: — for clients that only let you set custom headers.
The worker forwards it to the API as X-API-Key. Requests without a key get a 401. Whatever the key can do, the assistant can do: keys are per-user, so the assistant only ever sees that user's trips.
Where your key lives. The server is stateless: your key is read from the headers of each request, used to make that one call to the MyNextAdventure API, and never stored — there is no session storage and no Durable Object holding it between requests. It is never logged and is not shared between requests or users. Revoke a key any time in the app under Settings → API keys.
Tools
24 tools, covering the operations conversational planning actually needs. Each one is a curated view over a MyNextAdventure API operation — see Regenerating the tools.
The server also ships MCP instructions describing the data model (trip → variants → destinations → options, with events on the variant) and the usual order of operations, so a client does not have to guess the workflow.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
My Next Adventure: common questions
- Is My Next Adventure MCP server safe?
- Yes, by our scan: it is graded A (97/100). Read the My Next Adventure safety report
- How do I install My Next Adventure?
- It runs remotely at mcp.mynextadventure.cloud. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does My Next Adventure need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is My Next Adventure maintained?
- The last commit was 48 days ago (2026-09-17). The latest release is v1.0.1.
- Is My Next Adventure up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does My Next Adventure compare with other MCP servers?
- safety score 97/100 (higher than 98% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 384 ms (faster than 38% of 30,031 servers). Full comparison.