Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "trips": {
      "type": "http",
      "url": "https://thistripbtw.us/mcp"
    }
  }
}

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

[mcp_servers.trips]
url = "https://thistripbtw.us/mcp"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "trips": {
      "type": "remote",
      "url": "https://thistripbtw.us/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "trips": {
      "type": "http",
      "url": "https://thistripbtw.us/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=trips&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vdGhpc3RyaXBidHcudXMvbWNwIn0%3D"
}

{
  "servers": {
    "trips": {
      "type": "http",
      "url": "https://thistripbtw.us/mcp"
    }
  }
}

{
  "mcpServers": {
    "trips": {
      "httpUrl": "https://thistripbtw.us/mcp"
    }
  }
}

extensions:
  "trips":
    enabled: true
    name: "trips"
    type: streamable_http
    uri: "https://thistripbtw.us/mcp"
    timeout: 300

Quality 86 / 100good

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene100 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations6 of 6 tools declare readOnlyHint or destructiveHint
pass
tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
pass
tools.token_costabout 3,734 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability75 · weight 15

warn
stability.changes8 tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvabledeps.dev does not know [email protected]

6 tools, about 3,734 tokens to load them all · tool set 83b9839b5ef5 · tools last changed 2026-10-01 · checked 2026-10-19 23:50 UTC

Tool changes

2026-10-01amend_trip_linkchangeddescription, input schema, output schema
before
Update a trip link you already built — add legs, replace them, 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. 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.
after · 75% of words in common
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.
2026-09-28read_kept_tripchangedinput schema
2026-09-25add_to_kept_tripchangedoutput schema, annotations
2026-09-25read_kept_tripchangedoutput schema, annotations
2026-09-25read_trip_linkchangedoutput schema, annotations
2026-09-25amend_trip_linkchangedoutput schema, annotations
2026-09-25find_placechangedoutput schema, annotations
2026-09-25build_trip_linkchangedoutput schema, annotations

Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 95 / 100

provenance85

liveness98

freshness100

hygiene100

+repository +dns-namespace +website +reachable +uptime-95% +updated-20d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Dependencies

[email protected] npmthis version is not known to the dependency resolver

Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0. The graph is what a clean install of this version resolves today; nothing was installed or run. How it is checked.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://thistripbtw.us/mcp` streamable-http	none	yes	95%	221 ms	2025-11-25	2026-10-19

package	registry	version	runtime	secrets
`thistripbtw-mcp`	npm	1.3.5	–

Tools (6)

`add_to_kept_trip`	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_link`read-only	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_link`read-only	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_place`read-only	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_trip`read-only	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_link`read-only	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.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "us.thistripbtw/trips",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://thistripbtw.us/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.3.5",
  "packages": [
    {
      "version": "1.3.5",
      "transport": {
        "type": "stdio"
      },
      "identifier": "thistripbtw-mcp",
      "registryType": "npm"
    }
  ],
  "repository": {
    "url": "https://github.com/peterbartsch/thistripbtw-mcp",
    "source": "github"
  },
  "websiteUrl": "https://thistripbtw.us/for-agents",
  "description": "Hand someone a complete trip as a private, editable map link. No account, no API key, no card."
}