trips MCP server
us.thistripbtw/tripsthistripbtw.usstreamable-httpv1.3.5Scanned
Hand someone a complete trip as a private, editable map link. No account, no API key, no card.
6 tools: 3 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- 4 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the trips MCP server can do
The trips MCP server is published by thistripbtw.us, a domain the MCP Registry verified. It has 6 tools. It can create or change data (3 tools: build_trip_link, amend_trip_link and add_to_kept_trip), but cannot delete data. 3 tools only read.
3 tools bring in text other people can write (find_place, read_kept_trip and add_to_kept_trip).
The fixed checks matched 4 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.3.5.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 3Claude Code: ask
add_to_kept_tripAdd a stop to a trip the person has KEPT (a link with #k=), on their behalf.Reads text others write1 finding
Why it is in this group
- The name "add_to_kept_trip" says "add": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...counts as a guess. Treat the link as a credential."
Description, as the server wrote it 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.
Annotations the server declares
- title: Add a stop to a kept trip
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
amend_trip_linkUpdate 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.1 finding
Why it is in this group
- The name "amend_trip_link" says "link": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "amend_trip_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "amend_trip_link" says "link": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Amend a trip link
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
build_trip_linkStart here for any trip, road trip or itinerary.1 finding
Why it is in this group
- The name "build_trip_link" says "link": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "build_trip_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "build_trip_link" says "link": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Build a trip link
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 3Show 3 read-only tools
find_placeTurn a place name into coordinates for build_trip_link — towns, cities, airports (IATA or name), parks, trailheads.Reads text others writeNo findings
Why it is in this group
- The name "find_place" says "find": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Find a place
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
read_kept_tripUse 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 wh…Reads text others write1 finding
Why it is in this group
- The name "read_kept_trip" says "read": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...ccount is involved. Treat the link as a credential — do not repeat it back in text a third..."
Description, as the server wrote it 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.
Annotations the server declares
- title: Read a kept trip
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
read_trip_linkUse 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 somet…No findings
Why it is in this group
- The name "read_trip_link" says "read": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Read a trip link
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:20 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://thistripbtw.us/mcp: tools/list returned 6 tools to an anonymous client, including build_trip_link (write), amend_trip_link (write), add_to_kept_trip (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnbuild_trip_link
The server marks "build_trip_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "build_trip_link" says "link": a word for a change.
- Warnamend_trip_link
The server marks "amend_trip_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "amend_trip_link" says "link": a word for a change.
- Inforead_kept_trip
The description mentions "credential".
What this check looks forMatched text
description: "...ccount is involved. Treat the link as a credential — do not repeat it back in text a third..."
- Infoadd_to_kept_trip
The description mentions "credential".
What this check looks forMatched text
description: "...counts as a guess. Treat the link as a credential."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.3.5. Values in angle brackets are yours to fill in.
claude mcp add --transport http trips https://thistripbtw.us/mcpclaude mcp add --transport http trips https://thistripbtw.us/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__trips__find_place",
"mcp__trips__read_trip_link",
"mcp__trips__read_kept_trip"
],
"ask": [
"mcp__trips__build_trip_link",
"mcp__trips__amend_trip_link",
"mcp__trips__add_to_kept_trip"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as trips. Review it before you use it.
Capability tags behind 3 rules
- mcp__trips__find_place untrusted-input
- mcp__trips__read_kept_trip untrusted-input
- mcp__trips__add_to_kept_trip untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/us.thistripbtw/trips/verify?hash=d30d1fda2b113c6e7ed7130c49721fd73dfaf6c1b6d4a1ce34d97dbe1f570780" | jq -e '.changed == false'Pinned hash d30d1fda2b11, from Nov 18, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/us.thistripbtw/trips/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/us.thistripbtw/trips)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:55 UTC.
trips MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the trips MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the trips MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the trips MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the trips MCP server have?
- 6 tools: 3 write, 3 read. build_trip_link, amend_trip_link, add_to_kept_trip, find_place, read_trip_link and read_kept_trip.
Does the trips MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the trips MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the trips MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.