Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Trip1 is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Book hotels over MCP. Pay over x402. 3M+ properties in 200+ countries, USDC on Base.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http trip1-mcp https://trip1.com/api/mcp
# 2 — ask your agent for something these tools do
# search_hotels, get_hotel_details, start_checkout and 3 more
Trip1 costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http trip1-mcp https://trip1.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search for available hotels by destination and dates. Returns a list of matching hotels with pricing, images, and booking links. Occupancy is fixed at 2 adults in one room and cannot be set. If the user asked for a different party size, tell them these prices are for 2 adults rather than presenting them as a quote for their group. Always include the hotel name, booking link, and image for each hot
| Parameter | Type | Required | Notes |
|---|---|---|---|
| destination | string | yes | Destination name (e.g., 'London', 'Paris, France', 'Vilnius') |
| check_in | string | yes | Check-in date in YYYY-MM-DD format. Must be today or later in the destination's own timezone. Do not assume the current year — the server instructions state today's date; a past date is rejected, and |
| check_out | string | yes | Check-out date in YYYY-MM-DD format. Must be after check_in. |
| sort_by | string | no | Sort results by: price, rating, distance, or relevance (default) |
| sort_order | string | no | Sort order: asc (default) or desc |
| context | string | no | Why are you calling this tool? Describe the user's underlying goal in one short sentence — not the tool name. Never include names, emails, phones, or prices. Always pass this. Used for analytics only; |
Get rooms and rates for a hotel. Pass the hotel id from search_hotels results. Returns rate IDs needed for purchase_hotel. Each rate states its refundability and, when refundable, the cancellation deadline — quote these rather than inferring refund terms. When prices_changed is true, the price search_hotels quoted for this hotel is no longer the one on offer — tell the user prices changed rather t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The hotel id from search_hotels results |
| context | string | no | Why are you calling this tool? Describe the user's underlying goal in one short sentence — not the tool name. Never include names, emails, phones, or prices. Always pass this. Used for analytics only; |
Open the booking form for a rate the user picked from get_hotel_details. Shows the stay and the price, and lets the user enter the guest details and choose how to pay. On the first call, pass the user's own details you already know -- from this conversation or your memory of them -- so the form opens prefilled, and only those: never invent or guess any; the form asks for the rest and the user revi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rate_id | string | yes | Rate id from get_hotel_details |
| first_name | string | no | Guest's first name, if known |
| last_name | string | no | Guest's last name, if known |
| string | no | Guest's email, if known | |
| phone | string | no | Guest's phone with country code, if known |
| title | string | no | MR, MRS, MS or MISS, only if the user has stated it |
| title_suggestion | string | no | When the user has not stated a title: your best guess from their first name. The form preselects it, labelled as a suggestion from their name, and the user can change it. |
| nationality | string | no | Guest's nationality as ISO 3166-1 alpha-2, if known |
| payment_service | string | no | Payment method the user already chose, if any |
| context | string | no | Why are you calling this tool? Describe the user's underlying goal in one short sentence — not the tool name. Never include names, emails, phones, or prices. Always pass this. Used for analytics only; |
Book a hotel room in chat, by providing guest details and a rate ID from get_hotel_details. Use start_checkout instead, which opens a booking form; call this only when the user says they cannot see or use that form. Creates a guest profile, adds the room to a cart, and initiates checkout. Ask the user how they want to pay before calling, and pass it as payment_service: 'x402' (USDC on Base, paid b
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rate_id | string | yes | Signed rate ID from get_hotel_details response |
| first_name | string | yes | Guest's first name |
| last_name | string | yes | Guest's last name |
| string | yes | Guest's email address | |
| phone | string | yes | Guest's phone number (e.g., +44123456789) |
| nationality | string | no | Guest's nationality as ISO 3166-1 alpha-2 code (default: GB) |
| title | string | no | Guest's title: MR, MRS, MS, or MISS (default: MR) |
| price_currency | string | no | Payment currency (default: USD for x402, EUR for coingate). Supported: EUR, USD, GBP, PLN, CZK, HUF, SEK, NOK, DKK |
| payment_service | string | no | Payment method the user chose: x402 (USDC on Base, needs an x402 payments tool; default) or coingate (browser checkout, any crypto) |
| context | string | no | Why are you calling this tool? Describe the user's underlying goal in one short sentence — not the tool name. Never include names, emails, phones, or prices. Always pass this. Used for analytics only; |
Open CoinGate's checkout page for an unpaid CoinGate booking, so the user can pay in their browser. Pass the cart_id from purchase_hotel or the booking form. Where the client supports it, this asks the client to open the page for the user (URL elicitation); otherwise, and once the page has been offered, it returns the order with its payment link. Not for x402 bookings, which your payments tool pay
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cart_id | string | yes | The cart_id from purchase_hotel or the booking form |
| context | string | no | Why are you calling this tool? Describe the user's underlying goal in one short sentence — not the tool name. Never include names, emails, phones, or prices. Always pass this. Used for analytics only; |
Get the current state of an order. Returns payment status, booking state, and item details. Poll until ready is true to confirm the booking is complete.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cart_id | string | yes | The cart_id from purchase_hotel response |
| context | string | no | Why are you calling this tool? Describe the user's underlying goal in one short sentence — not the tool name. Never include names, emails, phones, or prices. Always pass this. Used for analytics only; |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Trip1 or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_hotels | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_hotel_details | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| start_checkout | no tags | |
| purchase_hotel | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| pay_order | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_order_details | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.2.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Trip1 can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.