Trips MCP Server
us.thistripbtw/trips
answering
Trips is answering right now. Last checked 12 min ago. 129 installs a week from npm. It exposes 1 tools. Last commit 3 Aug 2026.
Turn a trip planned in conversation into a private, editable map link you hand the person.
Installs per day
peak 129 · avg 4
a month agotoday
Uptime history
40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
365 ms
Response time
average over 24h
129
Installs / week
npm and PyPI
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.
run in your terminal
claude mcp add trips --transport http https://thistripbtw.us/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"trips": {
"url": "https://thistripbtw.us/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.trips]
url = "https://thistripbtw.us/mcp".cursor/mcp.json
{
"mcpServers": {
"trips": {
"url": "https://thistripbtw.us/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"trips": {
"url": "https://thistripbtw.us/mcp"
}
}
}Available tools 1
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
build
build_trip_link
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. 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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://thistripbtw.us/mcp | streamable-http | answering | 295 ms | 12 min ago |
Trips — questions
Answers built from our own checks of this server.
What can Trips do?
It exposes 1 tools, read directly from the server on our last check. Among them: build_trip_link. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Trips working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 365 ms. The bar chart above shows every period we have measured.
How do I connect Trips?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Trips need an API key?
No. Trips completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Trips?
It answers our handshake in 365 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Trips?
The npm package thistripbtw-mcp was installed 129 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Trips open source?
Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.