MCP.Market

Trips MCP server

online · 96% uptime
by thistripbtw.us·us.thistripbtw/trips·v1.3.5
No reviews yet

Hand someone a complete trip as a private, editable map link. No account, no API key, no card.

A86/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A86/100

full report

Adoption
Growing

0 stars611 downloads/wk

Reviews

Write one

Nobody has reviewed Trips yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Trips tools (6, 1 write)

write = sends, deletes, buys or posts
  • add_to_kept_tripFree

    Add a stop to a trip the person has KEPT (a link with #k=), on their behalf. Use when they say 'add X to the trip', 'we're stopping at Y on the way', 'put the hotel on it'. Needs their EDIT phrase — a view phrase can read but not write, and the tool says so. Writes exactly one stop and returns the trip's current stop count. Like read_kept_trip this touches the network: the #k= phrase is the password and it goes to thistripbtw.us over TLS, nothing is stored about you, and a wrong phrase counts as a guess. Treat the link as a credential.

  • amend_trip_linkwrite actionFree

    Update a trip link you already built — add legs, change one leg's fields, replace them all, rename, or drop one — and get the new link back. Use this instead of building a fresh link every time the plan changes, so the person holds one link that grows. To change ONE leg (its lodging, date, note, who is on it) use `update` rather than resending every leg through `legs`. Takes a draft link (#d=) plus the changes; no network, no password, the trip is inside the link. For a KEPT trip (#k=) use add_to_kept_trip.

  • build_trip_linkFree

    Start here for any trip, road trip or itinerary. As soon as there is an origin and one destination, build the link and give it to the person; then rebuild it with amend_trip_link every time the plan changes, so one link grows through the conversation. It opens as a private, editable, shareable 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. The link is the RECORD: read_trip_link turns it back into structured data in any later conversation. Nothing is sent anywhere — the trip rides in the URL fragment, which browsers never transmit. Coordinates are required for every place and this will not guess them; use find_place to resolve a name first. Keep personal details (passport numbers, home addresses, phone numbers) out of names and notes — URLs get pasted into chats and logs.

  • find_placeFree

    Turn a place name into coordinates for build_trip_link — towns, cities, airports (IATA or name), parks, trailheads. Returns up to six candidates with lat/lng and where each one is, so you can pick the right Reno. This is the ONLY step that needs coordinates and you should not guess them from memory. It asks thistripbtw.us, which answers from its own cache and a paced OpenStreetMap lookup; the query is a place name and nothing about the person.

  • read_kept_tripFree

    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.

  • read_trip_linkFree

    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.

Public scan report

scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it

1 high
  • Code scan3 source files scanned25/25
  • Live reliabilityremote reachable in 513ms20/20
  • Tool poisoning6 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
  • Maintenancelast push 4 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10

Findings (1)

  • highWrite-action tools reachable without authenticationauth.open-write
Overall 86/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Trips compares

Against every graded Maps and travel MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
86/100
higher than 79% of 681 Maps and travel servers
Tools
6
the typical Maps and travel server has 6
Tools that change things
17%
typical: 0%. Fewer write tools means less an agent can break
Uptime
96%
of our recent checks; the typical remote Maps and travel server answers 100%
Response time
209 ms
faster than 68% of 452 Maps and travel servers
Downloads a week
611
more than 93% of 150 Maps and travel servers with a package

What its tools let an agent do: 4 read · 1 create · 1 change

Release history: 4 versions in the registry since 2026-09-13, latest 2026-09-30, typically one every 2 days.

Install Trips in Claude Code, Cursor or VS Code

claude mcp add --transport http trips https://thistripbtw.us/mcp
Add to Cursor

What the publisher says

From the Trips repository's README, as published. We do not edit it. Read it on GitHub

thistripbtw-mcp

Persistent, shareable travel workspaces for AI agents.

Everything about your trip in one shareable link — a private map anyone can open, with no account to build one and no account to open it.

An MCP server that hands someone that link, grows it as the plan changes, and reads it back. Six tools, and the first one is the point: build the link as soon as there is an origin and one destination, then amend it every time the plan moves. One resolves a place name to coordinates, one turns legs into a URL, one changes a URL you already built, one decodes a URL into the legs, one reads a trip the person has bought, and one adds a stop to it. The person opens it and their trip is already drawn on a real map — free, editable, theirs.

→ thistripbtw.us — the human side, and the thing that pays for this. The server is free and asks for nothing; the site's one-time paid tiers fund it rather than an ad business or your data.

Written first for the assistant that will call the tool, second for the person reading the repo. If you are that person: the site's source is thistripbtw (AGPL-3.0). This server is MIT and standalone on purpose — embed it wherever you like.

Why it exists

An AI assistant generally cannot create an account or enter card details. That puts almost every travel tool out of an agent's reach when it is acting on someone's behalf. This one asks for nothing, so it stays reachable.

Connect

A URL, if your client takes one. Nothing to install, nothing to keep updated:

https://thistripbtw.us/mcp

Streamable HTTP, no key, no sign-up to start. That is the whole configuration.

A note on gateways. Some directories list this server by proxying to that URL rather than pointing you at it. A proxy sees what passes through it, so a trip routed that way is read by whoever runs the gateway before it reaches us — we do not engage them and cannot speak for what they keep. Use the URL directly, or run the file yourself, if that matters to you.

Or run it locally from npm. Node 18+, no dependencies, nothing to keep updated:

claude mcp add thistripbtw -- npx -y thistripbtw-mcp

Or fetch the one file and run that, if you would rather read the code than trust either a host or a package registry. This is the whole install:

curl -O https://thistripbtw.us/mcp/thistripbtw-mcp.mjs
claude mcp add thistripbtw -- node ./thistripbtw-mcp.mjs

Claude Desktop config

{
  "mcpServers": {
    "thistripbtw": {
      "command": "npx",
      "args": ["-y", "thistripbtw-mcp"]
    }
  }
}

Swap to "command": "node" with "args": ["/absolute/path/to/thistripbtw-mcp.mjs"] if you fetched the file instead.

Check it before you trust it — the self-test touches no network and needs no config:

npx -y thistripbtw-mcp --selftest

Both paths carry the same six tools and produce byte-identical links. The hosted one is tested against this file on every build — same tool list, same output — so the two cannot drift apart.

Step-by-step, with a worked example in JavaScript and Python: thistripbtw.us/tutorials

The tools

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Trips: common questions

Is Trips MCP server safe?
Yes, by our scan: it is graded A (86/100). Read the Trips safety report
How do I install Trips?
It runs remotely at thistripbtw.us. 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 Trips need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Trips maintained?
The last commit was 35 days ago (2026-09-30). The latest release is v1.3.5.
Is Trips up?
96% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Trips?
Servers from other publishers that do the same job: HasData Google Flights Deals MCP server, TourClaim by Copernican MCP server and Repo Graph MCP server.
How does Trips compare with other Maps and travel MCP servers?
safety score 86/100 (higher than 79% of 681 Maps and travel servers); tools 6 (the typical Maps and travel server has 6); tools that change things 17% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Trips

Same job from other publishers: the closest match first, then the best rated.

  • HasData Google Flights Deals
    A plain-language trip description becomes dated flight deals with prices and booking links.
    A
  • TourClaim by Copernican
    Prepare trip cancellation claims on credit-card travel insurance with traveler consent. Review mode.
    A
  • Repo Graph
    Structural graph map of any codebase so LLMs navigate by structure, not guesswork.
    A
  • Agentmap
    The TS/JS-accurate repo map for coding agents: ts-morph import/symbol/call graph + MCP query tools
    A
  • Bharatlas
    Query India's open geo data, and author collect maps: register a link, moderate, publish.
    A