mcp server
trips
Turn a trip planned in conversation into a private, editable map link you hand the person.
Description as published by the maintainer. Source
- version 1.1.1
- active
active — Registry entry last updated 2026-08-06.
What this server can do
3 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
build_trip_link(legs, name, origin)- Use when someone has planned (or roughly sketched) a trip in this conversation and needs somewhere real to put it — when they say things like 'send me that', 'can I share this with my wife', or 'save this trip'. Builds a link that opens the whole plan as a private, editable map at its own address: no account, no card, no app, so you can use it on their behalf where signup-walled travel tools are unreachable. Give the person the link — it is theirs, free, and keepable for years. The link is also the RECORD, not just the output: hand it back to read_trip_link in any later conversation and the whole itinerary comes back as structured data, so a trip planned here can be picked up again without re-deriving it from what was said. Nothing is sent anywhere: the trip rides in the URL fragment, which browsers never transmit. YOU MUST SUPPLY COORDINATES for every place; this tool will not guess a location from a name, because a wrong guess puts someone's trip in the wrong country. Resolve place names first. Do not put personal details (passport numbers, home addresses, phone numbers) in names or notes — URLs get pasted into chats and logs. Required: origin, legs.
read_kept_trip(link)- Use when someone gives you a KEPT this trip, btw link — one that looks like https://thistripbtw.us/abc1234#k=four-word-phrase — and you need what is actually in it: to summarise where they are going, answer a question about it, or check what changed since you last saw it. Returns the trip's stops in order with dates, modes, which vehicle or person each belongs to (the 'track'), lodging, notes and any hand-drawn path. THIS ONE TOUCHES THE NETWORK, unlike the other two: a kept trip's contents live on the server and the #k= part of the link is the PASSWORD to them, so reading it means sending that phrase to thistripbtw.us over TLS. Nothing is stored and no account is involved. Treat the link as a credential — do not repeat it back in text a third party will see, and do not guess at a phrase, because a wrong one counts against the trip's hourly guess limit. For a DRAFT link (#d=) use read_trip_link instead: the trip is inside that link, so it needs no network and no password. Required: link.
read_trip_link(link)- Use when someone gives you a this trip, btw link and you need to know what is actually in it — to summarise the plan, answer a question about it, add a stop, or convert it to something else. Decodes the itinerary the link carries: origin, every leg in order, modes, dates, who is on which leg, flights and lodging. Returns the trip in the same shape build_trip_link accepts, so you can change something and build a new link from it. Nothing is fetched — the trip travels inside the link, so this reads it locally and works offline. Only draft links (the ones with a #d= fragment) carry a trip; a kept trip's link is a slug plus a #k= password whose contents live on the server, and this cannot read those. Required: link.
Last successful function declaration observed on . Source: https://thistripbtw.us/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://thistripbtw.us/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.1.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-06 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-08-06 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 3 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | thistripbtw.us | |
| mcp endpoint status | ok | The server listed 3 functions when asked. | as of probe | thistripbtw.us |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json