com.trip1/mcp
REMOTE · TRIP1.COM
Book hotels over MCP. Pay over x402. 3M+ properties in 200+ countries, USDC on Base.
Available components
Last scanned (23 hours ago)
Scores higher than 77% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (purchase_hotel). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2235 tokens (~223/item across 10 items; 6 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pay_order" implies "pay" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 20 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 19 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 18 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 17 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 16 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 15 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 14 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://trip1.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trip1.com | CN=WE1,O=Google Trust Services,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | db7e2584a5991b400ef33a0e0c72f388 |
| SANs: trip1.com, og.trip1.com, *.og.trip1.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of trip1.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| trip1.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trip1.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://trip1.com/api/mcp | HTTPS enforced | 301 | https://trip1.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_hotel_details Get Hotel Details ~199
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 than presenting these rates as the same quote. When the user picks a rate, call start_checkout with its id next -- it opens the booking form, so do not ask for guest details in chat.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | 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… |
| id | string | yes | The hotel id from search_hotels results |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string|null | yes | – |
| check_in | string | yes | Earliest check-in time, HH:MM |
| check_out | string | yes | Latest check-out time, HH:MM |
| image_urls | array | yes | Up to 5 hotel photos, primary first; for the rooms view, not sent to the model |
| name | string | yes | – |
| next_step | string | yes | What to call once the user picks a rate |
| prices_changed | boolean|null | yes | true when these rates come from a different provider than the search_hotels quote; null when the search recorded no winner |
| rooms | array | yes | – |
| star_rating | integer | yes | – |
| stay | object | yes | The dates and party these rates are for |
No examples provided.
get_order_details Get Order Details ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cart_id | string | yes | The cart_id from purchase_hotel response |
| context | string | – | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| booking | object|null | yes | – |
| cart_url | string | yes | – |
| payment | object|null | yes | – |
| ready | boolean | yes | true once payment settled and the booking is purchased — stop polling |
No examples provided.
pay_order Pay Order ~169
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 pays.
| Name | Type | Req | Description |
|---|---|---|---|
| cart_id | string | yes | The cart_id from purchase_hotel or the booking form |
| context | string | – | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| booking | object|null | yes | – |
| cart_url | string | yes | – |
| payment | object|null | yes | – |
| ready | boolean | yes | true once payment settled and the booking is purchased — stop polling |
No examples provided.
purchase_hotel Purchase Hotel ~442
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 by an x402 payments tool you have) or 'coingate' (a checkout page the user pays in their browser, any crypto). If you have no x402 payments tool, use coingate. Returns a payment_url and the cart_url where the order can also be paid in a browser. The booking is confirmed once payment settles; poll get_order_details to check status.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | 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… |
| string | yes | Guest's email address | |
| first_name | string | yes | Guest's first name |
| last_name | string | yes | Guest's last name |
| nationality | string | – | Guest's nationality as ISO 3166-1 alpha-2 code (default: GB) |
| payment_service | string | – | Payment method the user chose: x402 (USDC on Base, needs an x402 payments tool; default) or coingate (browser checkout, any crypto) |
| phone | string | yes | Guest's phone number (e.g., +44123456789) |
| price_currency | string | – | Payment currency (default: USD for x402, EUR for coingate). Supported: EUR, USD, GBP, PLN, CZK, HUF, SEK, NOK, DKK |
| rate_id | string | yes | Signed rate ID from get_hotel_details response |
| title | string | – | Guest's title: MR, MRS, MS, or MISS (default: MR) |
| Name | Type | Req | Description |
|---|---|---|---|
| booking_reference | string|null | yes | – |
| cart_id | string | yes | Pass to get_order_details to poll the booking |
| cart_url | string | yes | The order on trip1, where it can also be paid in a browser |
| message | string | yes | How to complete payment for the chosen payment_service |
| payment_url | string|null | yes | – |
No examples provided.
search_hotels Search Hotels ~294
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 hotel in your response.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| context | string | – | 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… |
| destination | string | yes | Destination name (e.g., 'London', 'Paris, France', 'Vilnius') |
| sort_by | string | – | Sort results by: price, rating, distance, or relevance (default) |
| sort_order | string | – | Sort order: asc (default) or desc |
| Name | Type | Req | Description |
|---|---|---|---|
| hotels | array | yes | – |
| total_results | integer | yes | – |
No examples provided.
start_checkout Start Checkout ~414
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 reviews every field before booking. If the user has not stated a title, pass title_suggestion instead: your best guess from their first name, which the form labels as a suggestion. If the user submits the form, it books the room itself (purchase_hotel) and tells you the booking reference: do not call purchase_hotel again for it. Call this again with more details to refill the form.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | 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… |
| string | – | Guest's email, if known | |
| first_name | string | – | Guest's first name, if known |
| last_name | string | – | Guest's last name, if known |
| nationality | string | – | Guest's nationality as ISO 3166-1 alpha-2, if known |
| payment_service | string | – | Payment method the user already chose, if any |
| phone | string | – | Guest's phone with country code, if known |
| rate_id | string | yes | Rate id from get_hotel_details |
| title | string | – | MR, MRS, MS or MISS, only if the user has stated it |
| title_suggestion | string | – | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | yes | – |
| board_type | string | yes | – |
| cancellation_deadline | string|null | yes | – |
| check_in | string|null | yes | YYYY-MM-DD |
| check_out | string|null | yes | YYYY-MM-DD |
| currency | string | yes | – |
| guest | object | yes | The guest details passed in, to prefill the form |
| hotel_name | string|null | yes | – |
| image_urls | array | yes | Up to 5 room (else hotel) photos; for the checkout view, not sent to the model |
| next_step | string | yes | Whether the form books, or booking continues in chat |
| payment_quotes | object | yes | What each payment method charges for this stay, in the currency it charges in |
| payment_service | string|null | yes | – |
| price | number | yes | – |
| rate_id | string | yes | – |
| refundability | string | yes | – |
| room_name | string|null | yes | – |
| title_suggestion | string|null | yes | Preselected in the form as a suggestion when no title was passed |
No examples provided.
How do I install the com.trip1/mcp server?
com.trip1/mcp is a hosted endpoint at https://trip1.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · trip1.com
claude mcp add --transport http com-trip1-mcp 'https://trip1.com/api/mcp'
What is the com.trip1/mcp server?
com.trip1/mcp is listed in the public MCP registry as com.trip1/mcp. Book hotels over MCP. Pay over x402. 3M+ properties in 200+ countries, USDC on Base. This page covers its hosted endpoint (https://trip1.com/api/mcp).
Is the com.trip1/mcp server safe to use?
com.trip1/mcp scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.trip1/mcp server expose?
com.trip1/mcp exposes 6 tools: search_hotels, get_hotel_details, start_checkout, purchase_hotel, pay_order, get_order_details. Their descriptions and schemas cost roughly 1,628 tokens of context every time the server is loaded.
Does the com.trip1/mcp server require authentication?
No. We connected to com.trip1/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.trip1/mcp server still maintained?
com.trip1/mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the com.trip1/mcp server?
VerifyMCP ran 14 checks on com.trip1/mcp, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.