← Registry

eCommerce

trip1.com

Provides hotel search, details, and booking functionality.

x402 supported1 endpoint4 known toolsFirst detected July 3, 2026Last detected September 23, 2026

ENDPOINT 1

https://trip1.com/api/mcp

No auth detected

MCP server metadata

Name
trip1
Version
1.0.0
Capabilities
tools.listChangedprompts.listChangedresources.listChangedlogging
Server instructions

The current date is at least 2026-09-23 — never infer it from the conversation or from your training data. The check_in floor is the destination's own calendar day, which can be a day ahead of this; a check_in below it is rejected, not silently empty, and the rejection tells you what that day is. trip1 hotel booking API. The flow is four tools in order: 1. search_hotels - Find hotels by destination name and dates. Include the hotel name and booking link for each result you display. Occupancy is fixed at 2 adults; do not pass guests or adults. 2. get_hotel_details - Get rooms, rates, and cancellation terms for a hotel the user picked. 3. purchase_hotel - Create the reservation. All guest fields are required: first name, last name, email, phone, title, nationality. Collect every field from the user. Never invent, guess, or default any of them. Before calling this tool, show the full booking summary (hotel, dates, room, total, all guest details) and get explicit user confirmation. Returns a payment_url. 4. get_order_details - After payment, poll until ready is true to confirm the booking. On every tool call, pass a `context` string: one sentence on the user's goal (not the tool name). Never put names, emails, phones, or prices in context.

Known tools 4

search_hotels

Search for available hotels by destination and dates.

Inferred read-only
get_hotel_details

Get rooms and rates for a hotel.

Inferred read-only
purchase_hotel

Book a hotel room by providing guest details and a rate ID from get_hotel_details.

Inferred read-only
get_order_details

Get the current state of an order.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.trip1]
url = "https://trip1.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "trip1": {
      "type": "http",
      "url": "https://trip1.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: trip1
Remote MCP URL: https://trip1.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "trip1": {
      "url": "https://trip1.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "trip1": {
      "type": "http",
      "url": "https://trip1.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "trip1",
  "transport": "streamable-http",
  "url": "https://trip1.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for trip1.com was fetched 2026-09-06T18:06:04.079Z.

Trust status RestrictedContent

trip1.com is assessed as RestrictedContent: Domain runs gambling-related technology.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.