_ registry / mcp streamable-http · checked 3h ago

trip1

https://trip1.com

Registry code: 665122e665bdfae6

api record

The current date is at least 2026-11-06 — 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 these 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…

endpoint
https://trip1.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is trip1 live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is trip1 free to use?
Yes — the hub reached it with no key and no payment.
What tools does trip1 have?
6 tools: get_hotel_details, purchase_hotel, pay_order, get_order_details, search_hotels, start_checkout.
Is trip1 safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
947ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 305 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • search hotels by destination and dates
  • get hotel room rates
  • book a hotel room
  • pay for a hotel booking
  • check booking order status
takes → gives
text, data → data, payments
tools
3 reads1 changes data2 moves money
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_hotel_details reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "The hotel id from search_hotels results"
        },
        "context": {
          "type": "string",
          "maxLength": 200,
          "description": "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; never shown to the user."
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • purchase_hotel moves money unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "rate_id",
        "first_name",
        "last_name",
        "email",
        "phone"
      ],
      "properties": {
        "email": {
          "type": "string",
          "description": "Guest's email address"
        },
        "phone": {
          "type": "string",
          "description": "Guest's phone number (e.g., +44123456789)"
        },
        "title": {
          "enum": [
            "MR",
            "MRS",
            "MS",
            "MISS"
          ],
          "type": "string",
          "description": "Guest's title: MR, MRS, MS, or MISS (default: MR)"
        },
        "context": {
          "type": "string",
          "maxLength": 200,
          "description": "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; never shown to the user."
        },
        "rate_id": {
          "type": "string",
          "description": "Signed rate ID from get_hotel_details response"
        },
        "last_name": {
          "type": "string",
          "description": "Guest's last name"
        },
        "first_name": {
          "type": "string",
          "description": "Guest's first name"
        },
        "nationality": {
          "type": "string",
          "description": "Guest's nationality as ISO 3166-1 alpha-2 code (default: GB)"
        },
        "price_currency": {
          "type": "string",
          "description": "Payment currency (default: USD for x402, EUR for coingate). Supported: EUR, USD, GBP, PLN, CZK, HUF, SEK, NOK, DKK"
        },
        "payment_service": {
          "enum": [
            "x402",
            "coingate"
          ],
          "type": "string",
          "description": "Payment method the user chose: x402 (USDC on Base, needs an x402 payments tool; default) or coingate (browser checkout, any crypto)"
        }
      },
      "additionalProperties": false
    }
    arguments 65 lines
  • pay_order moves money unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "cart_id"
      ],
      "properties": {
        "cart_id": {
          "type": "string",
          "description": "The cart_id from purchase_hotel or the booking form"
        },
        "context": {
          "type": "string",
          "maxLength": 200,
          "description": "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; never shown to the user."
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • get_order_details reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "cart_id"
      ],
      "properties": {
        "cart_id": {
          "type": "string",
          "description": "The cart_id from purchase_hotel response"
        },
        "context": {
          "type": "string",
          "maxLength": 200,
          "description": "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; never shown to the user."
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • search_hotels reads unknown 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "destination",
        "check_in",
        "check_out"
      ],
      "properties": {
        "context": {
          "type": "string",
          "maxLength": 200,
          "description": "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; never shown to the user."
        },
        "sort_by": {
          "enum": [
            "relevance",
            "price",
            "rating",
            "distance"
          ],
          "type": "string",
          "description": "Sort results by: price, rating, distance, or relevance (default)"
        },
        "check_in": {
          "type": "string",
          "description": "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 the rejection tells you the destination's today."
        },
        "check_out": {
          "type": "string",
          "description": "Check-out date in YYYY-MM-DD format. Must be after check_in."
        },
        "sort_order": {
          "enum": [
            "asc",
            "desc"
          ],
          "type": "string",
          "description": "Sort order: asc (default) or desc"
        },
        "destination": {
          "type": "string",
          "description": "Destination name (e.g., 'London', 'Paris, France', 'Vilnius')"
        }
      },
      "additionalProperties": false
    }
    arguments 47 lines
  • start_checkout changes data unknown 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "rate_id"
      ],
      "properties": {
        "email": {
          "type": "string",
          "description": "Guest's email, if known"
        },
        "phone": {
          "type": "string",
          "description": "Guest's phone with country code, if known"
        },
        "title": {
          "enum": [
            "MR",
            "MRS",
            "MS",
            "MISS"
          ],
          "type": "string",
          "description": "MR, MRS, MS or MISS, only if the user has stated it"
        },
        "context": {
          "type": "string",
          "maxLength": 200,
          "description": "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; never shown to the user."
        },
        "rate_id": {
          "type": "string",
          "description": "Rate id from get_hotel_details"
        },
        "last_name": {
          "type": "string",
          "description": "Guest's last name, if known"
        },
        "first_name": {
          "type": "string",
          "description": "Guest's first name, if known"
        },
        "nationality": {
          "type": "string",
          "description": "Guest's nationality as ISO 3166-1 alpha-2, if known"
        },
        "payment_service": {
          "enum": [
            "coingate",
            "x402"
          ],
          "type": "string",
          "description": "Payment method the user already chose, if any"
        },
        "title_suggestion": {
          "enum": [
            "MR",
            "MRS",
            "MS",
            "MISS"
          ],
          "type": "string",
          "description": "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."
        }
      },
      "additionalProperties": false
    }
    arguments 67 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 665122e665bdfae6.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/665122e665bdfae6/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/665122e665bdfae6/badge.svg)](https://brick.blue/agent/665122e665bdfae6?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.