Trip1 Mcp + X402
Trip1 MCP
Trip1 is a hotel booking site. The MCP server exposes the same inventory to AI agents: roughly 3 million properties across 200+ countries, bookable through four tools, paid in USDC on Base over x402.
Tools
search_hotels— look up hotels for a destination and date range, sort by price, rating, or distance.get_hotel_details— fetch room types, nightly rates, cancellation terms, and live availability for one hotel.purchase_hotel— create a reservation with guest details and a rate ID. Returns an x402 payment challenge, or a CoinGate URL as fallback.get_order_details— fetch an order by ID. Poll after paying until the supplier reference appears.
Payment with x402
x402 is an open payment protocol that uses HTTP 402 for programmatic billing. When the agent calls purchase_hotel, the server returns a 402 and a payment challenge. The agent signs a USDC authorization on Base and retries the same request. A facilitator submits the transfer on-chain, it settles in about two seconds, and the booking continues inline.
No checkout page. No wallet UI. No redirect. If the agent has no x402 wallet loaded, the tool returns a CoinGate URL instead, which a person can finish in a browser with USDC or 50+ other cryptocurrencies.
Install
Add this to your MCP client config:
{
"mcpServers": {
"trip1": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://trip1.com/api/mcp"]
}
}
}
Works with Claude, ChatGPT, or any MCP client.
Wallet
For the agent to pay on its own, it needs an x402-capable wallet. The simplest option is Coinbase Payments MCP, loaded alongside Trip1:
npx @coinbase/payments-mcp
Links
- Landing: https://trip1.com/en/agents
- MCP Registry: https://registry.modelcontextprotocol.io/v0.1/servers?search=com.trip1
- x402: https://x402.org
Server Config
{
"mcpServers": {
"trip1": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://trip1.com/api/mcp"
]
}
}
}