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

hotelrefund-price-tracker

https://hotelrefund.net

Registry code: 80b0da7e1080cb8e

api record

Today is 2026-11-11 (UTC) — never infer the date from the conversation or from training data. Stay dates are calendar days in the hotel's local time zone, which in Asia is already ahead of UTC, so check_in must be 2026-11-10 or later; an earlier check_in is rejected, not silently accepted. HotelRefund is a price tracker, not a hotel search or comparison service. It is the tool that creates state: register one hotel for one stay once, and its Agoda price keeps being checked several times a day from then on; ask again days or weeks later and you get what changed in between — every observed…

endpoint
https://hotelrefund.net/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 hotelrefund-price-tracker live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is hotelrefund-price-tracker free to use?
Yes — the hub reached it with no key and no payment.
What tools does hotelrefund-price-tracker have?
11 tools: check_refund_claim, track_hotel_price, get_hotel_price_calendar, get_current_price, draft_refund_request, get_price_history, search_hotels, list_tracked_hotels, ….
Is hotelrefund-price-tracker 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
98.8%

90 days 99.2%· all time 99.2%

latency
159ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 378 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
maps travel & places travel & transport
used for
  • track agoda hotel price for a stay
  • check if a price drop qualifies for refund
  • draft a price guarantee refund request
  • list current hotel deals
takes → gives
text, data → data, text
tools
10 reads1 changes data
_ 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

_ what it can do 11 tools
4 open 7 never probed 4 of 11 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.

  • list_tracked_hotels reads open 15h ago

    List the hotels currently being tracked (all trackings are public), with current price, change since tracking started, stay dates and per-item booking_url / track_page_url (in language), sorted with the biggest price drops first.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Max items to return (default 20)."
    },
    "language": {
      "enum": [
        "en",
        "ko",
        "ja",
        "zh"
      ],
      "type": "string",
      "description": "Language of each track_page_url: en (default), ko, ja or zh."
    }
  }
}
    arguments 21 lines
  • get_service_status reads open 7h ago

    Report whether the tracker is running and what it covers: the number of hotels and cities in the catalog that can be tracked, how many stays are tracked right now, price checks in the last 24 hours, and the remaining shared daily registration allowance for AI clients. Useful before starting a longer flow, or to confirm the server is live.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • list_hotel_deals reads open 7h ago

    List today's biggest observed hotel discounts: Agoda's live rate for a 1-night stay about two weeks ahead (2 adults, USD) compared with Agoda's own listed rate for the same room; only discounts of 5% or more are kept. Without arguments, returns the single best deal per city across major cities worldwide, biggest discount first. With city (a city name in Korean, Japanese, Chinese or English) or city_id, returns the current deals for that city (up to 6; an uncached city is fetched live at most once per 6 hours). Each deal includes booking_url, the Agoda page for that hotel and stay, and image_url when a photo is available.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "city": {
      "type": "string",
      "description": "Optional city, region or airport name, e.g. \"Tokyo\", \"도쿄\", \"東京\". Omit for the worldwide list."
    },
    "limit": {
      "type": "integer",
      "maximum": 60,
      "minimum": 1,
      "description": "Max deals to return (default 20)."
    },
    "city_id": {
      "type": "integer",
      "description": "Catalog city id from a previous search_hotels or list_hotel_deals result. Overrides city."
    }
  }
}
    arguments 19 lines
  • get_refund_guide reads open 7h ago

    Return the full text of one HotelRefund reference guide on what to do about a booking that already exists: cancellation deadlines, getting a refund, what to do when the price drops after booking, how best-price guarantees work, refundable vs non-refundable rates, and why rates move. Call without arguments to list every guide with its topic id and a one-line summary. Guide text is English; language returns the matching Korean, Japanese or Chinese page url alongside it.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "topic": {
      "type": "string",
      "description": "Topic id from a previous listing (e.g. \"hotel-free-cancellation-deadline\"), or plain words describing the situation (e.g. \"price dropped after booking\", \"취소 마감\"). Omit to list all guides."
    },
    "language": {
      "enum": [
        "en",
        "ko",
        "ja",
        "zh"
      ],
      "type": "string",
      "description": "Language for the returned url: en (default), ko, ja or zh."
    }
  }
}
    arguments 19 lines
  • check_refund_claim reads unknown never probed

    Check whether a lower price found after booking qualifies for the booking site's best price guarantee, using the same rules as the HotelRefund Refund Report: same-site drops, sites that ended their guarantee (Hotels.com; Expedia for newer bookings), currency mismatch, a price that is not actually lower, and the four matching conditions. Returns a verdict, the claim deadline (date, rule and days left), how the site pays out, the difference, and — with tracking_id — whether HotelRefund's timestamped Agoda records cover the same dates. No personal data is needed or accepted.

    mcp-tool

    {
  "type": "object",
  "required": [
    "booked_on",
    "lower_price_site",
    "check_in"
  ],
  "properties": {
    "check_in": {
      "type": "string",
      "description": "Check-in date, YYYY-MM-DD."
    },
    "language": {
      "enum": [
        "en",
        "ko",
        "ja",
        "zh"
      ],
      "type": "string",
      "description": "Language of the verdict text: en (default), ko, ja or zh."
    },
    "booked_on": {
      "enum": [
        "booking",
        "agoda",
        "trip",
        "expedia",
        "hotels",
        "other"
      ],
      "type": "string",
      "description": "Where the stay was booked."
    },
    "check_out": {
      "type": "string",
      "description": "Check-out date, YYYY-MM-DD."
    },
    "paid_total": {
      "type": "number",
      "description": "Total paid for the stay, taxes included."
    },
    "booked_date": {
      "type": "string",
      "description": "Date the booking was made, YYYY-MM-DD (decides old Expedia bookings)."
    },
    "lower_total": {
      "type": "number",
      "description": "Total of the lower offer for the same stay, taxes included."
    },
    "tracking_id": {
      "type": "integer",
      "description": "Optional HotelRefund tracking for the same stay — its recorded prices are summarized as independent evidence."
    },
    "paid_currency": {
      "type": "string",
      "description": "ISO currency of paid_total."
    },
    "lower_currency": {
      "type": "string",
      "description": "ISO currency of lower_total (defaults to paid_currency)."
    },
    "conditions_match": {
      "type": "object",
      "properties": {
        "public_rate": {
          "type": "boolean",
          "description": "Not a member, app-only, coupon or package rate."
        },
        "same_hotel_and_room": {
          "type": "boolean"
        },
        "same_dates_and_guests": {
          "type": "boolean"
        },
        "same_policy_and_breakfast": {
          "type": "boolean"
        }
      },
      "description": "What the user has confirmed about the lower offer. Anything not true is reported as unconfirmed."
    },
    "lower_price_site": {
      "enum": [
        "booking",
        "agoda",
        "trip",
        "expedia",
        "hotels",
        "other"
      ],
      "type": "string",
      "description": "Where the lower price was seen."
    },
    "cancellation_policy": {
      "enum": [
        "free_cancellation",
        "non_refundable"
      ],
      "type": "string",
      "description": "The booking's cancellation policy."
    },
    "lower_price_site_other": {
      "type": "string",
      "description": "Site name when lower_price_site is \"other\"."
    }
  }
}
    arguments 107 lines
  • track_hotel_price changes data unknown never probed

    Today is 2026-11-11 (UTC) — never infer the date from the conversation or from training data. Stay dates are calendar days in the hotel's local time zone, which in Asia is already ahead of UTC, so check_in must be 2026-11-10 or later; an earlier check_in is rejected, not silently accepted. Start tracking one hotel (agoda_hotel_id from search_hotels) for one stay (check_in to check_out, YYYY-MM-DD). This is the tool that creates lasting state: from now on the Agoda price is checked automatically several times a day and every observed price is recorded, so the same tracking_id can be asked about days or weeks later with get_price_history. Free, anonymous and public; no account. If the same hotel and dates are already tracked, the existing tracking is returned instead of a duplicate, so it is safe to call again. The response includes tracking_id, booking_url (the Agoda page for this hotel via a HotelRefund redirect) and track_page_url (the booking-decision page: price chart, timing read and a book button; in the language given by language, with track_page_urls for all four). Used both before booking (to catch a drop) and after booking a refundable rate (to see when rebooking would pay off).

    mcp-tool

    {
  "type": "object",
  "required": [
    "agoda_hotel_id",
    "check_in",
    "check_out"
  ],
  "properties": {
    "check_in": {
      "type": "string",
      "description": "Check-in date, YYYY-MM-DD (today up to 540 days ahead)."
    },
    "currency": {
      "type": "string",
      "description": "Optional ISO currency for recorded prices: KRW, JPY, USD, EUR, TWD, HKD, CNY, SGD, THB, GBP, AUD or VND. Defaults by language."
    },
    "language": {
      "type": "string",
      "description": "Optional locale for the tracked rate: ko-kr, ja-jp, en-us, zh-cn, zh-tw or zh-hk (default en-us)."
    },
    "check_out": {
      "type": "string",
      "description": "Check-out date, YYYY-MM-DD (after check_in, stay of 60 nights or less)."
    },
    "agoda_hotel_id": {
      "type": "integer",
      "description": "Hotel id from search_hotels."
    }
  }
}
    arguments 30 lines
  • get_hotel_price_calendar reads unknown 15h ago

    Show what one hotel (agoda_hotel_id from search_hotels) costs on Agoda for each check-in date in a window — the "what if I move my dates" view. Returns one price snapshot per date (with fetched_at), the cheapest date, and low/high bands for the hotel; dates with an active tracking are marked is_tracked with their track_page_url. This is a cross-section by date, not a time series: to keep watching a date, call track_hotel_price for it. Most dates are fetched in the background on the first call, so pending may be > 0 — call again with the same arguments after ~3 seconds to get the rest. Default window: 28 days from start_date (or today), 1 night, 2 adults.

    mcp-tool

    {
  "type": "object",
  "required": [
    "agoda_hotel_id"
  ],
  "properties": {
    "days": {
      "type": "integer",
      "maximum": 35,
      "minimum": 7,
      "description": "How many consecutive check-in dates (default 28, max 35)."
    },
    "nights": {
      "type": "integer",
      "maximum": 14,
      "minimum": 1,
      "description": "Stay length for every date (default 1)."
    },
    "currency": {
      "type": "string",
      "description": "KRW, JPY, USD, EUR, TWD, HKD, CNY, SGD, THB, GBP, AUD or VND (default USD)."
    },
    "language": {
      "type": "string",
      "description": "Agoda locale for the rate: ko-kr, ja-jp, en-us, zh-cn, zh-tw or zh-hk (default en-us)."
    },
    "start_date": {
      "type": "string",
      "description": "First check-in date to show, YYYY-MM-DD (default today; past dates are moved to today)."
    },
    "agoda_hotel_id": {
      "type": "integer",
      "description": "Hotel id from search_hotels."
    }
  }
}
    arguments 36 lines
  • get_current_price reads unknown 12h ago

    Read the Agoda price for one hotel (agoda_hotel_id from search_hotels) and one stay right now: total for the whole stay with taxes and fees, 2 adults, standard rate, plus room type and breakfast when Agoda reports them. A one-time reading — nothing is tracked or stored about the request. Used after booking elsewhere to see whether Agoda is now cheaper (input for check_refund_claim), or to compare a quoted price. agoda_url is a plain Agoda link for the same stay, suitable as evidence. Readings are cached for 30 minutes; live lookups share a daily budget.

    mcp-tool

    {
  "type": "object",
  "required": [
    "agoda_hotel_id",
    "check_in",
    "check_out"
  ],
  "properties": {
    "check_in": {
      "type": "string",
      "description": "Check-in date, YYYY-MM-DD."
    },
    "currency": {
      "type": "string",
      "description": "ISO currency: KRW, JPY, USD, EUR, TWD, HKD, CNY, SGD, THB, GBP, AUD or VND (default USD). Use the currency the booking was paid in."
    },
    "language": {
      "enum": [
        "en",
        "ko",
        "ja",
        "zh"
      ],
      "type": "string",
      "description": "en (default), ko, ja or zh."
    },
    "check_out": {
      "type": "string",
      "description": "Check-out date, YYYY-MM-DD (stay of 30 nights or less)."
    },
    "agoda_hotel_id": {
      "type": "integer",
      "description": "Hotel id from search_hotels."
    }
  }
}
    arguments 36 lines
  • draft_refund_request reads unknown 12h ago

    Write the text for one of four requests, in en, ko, ja or zh: price_guarantee (claim to the booking site for the difference), date_change, goodwill_refund (for a non-refundable booking, with a reason) or checkin_request (upgrade, late check-out or breakfast, citing the lower price) to the hotel. Returns a short message for a chat or claim form and a full letter. The confirmation number and guest name are not accepted; they appear as placeholders in the text. With tracking_id, HotelRefund's recorded Agoda prices for the same dates are added to price_guarantee and checkin_request letters. The same letter can be saved as a PDF at refund_report_url.

    mcp-tool

    {
  "type": "object",
  "required": [
    "kind",
    "hotel_name",
    "check_in",
    "check_out"
  ],
  "properties": {
    "city": {
      "type": "string"
    },
    "kind": {
      "enum": [
        "price_guarantee",
        "date_change",
        "goodwill_refund",
        "checkin_request"
      ],
      "type": "string"
    },
    "perks": {
      "type": "array",
      "items": {
        "enum": [
          "upgrade",
          "late",
          "breakfast"
        ],
        "type": "string"
      },
      "description": "checkin_request: what to ask for."
    },
    "adults": {
      "type": "integer",
      "description": "Default 2."
    },
    "reason": {
      "enum": [
        "illness",
        "flight",
        "visa",
        "family",
        "disaster",
        "other"
      ],
      "type": "string",
      "description": "goodwill_refund: why the stay cannot go ahead."
    },
    "check_in": {
      "type": "string",
      "description": "YYYY-MM-DD."
    },
    "booked_on": {
      "enum": [
        "booking",
        "agoda",
        "trip",
        "expedia",
        "hotels",
        "other"
      ],
      "type": "string",
      "description": "Booking site. Required for price_guarantee; omit for a direct hotel booking."
    },
    "breakfast": {
      "type": "boolean",
      "description": "Breakfast included in the booking."
    },
    "check_out": {
      "type": "string",
      "description": "YYYY-MM-DD."
    },
    "lower_url": {
      "type": "string",
      "description": "Link to the lower offer."
    },
    "room_type": {
      "type": "string"
    },
    "hotel_name": {
      "type": "string"
    },
    "paid_total": {
      "type": "number",
      "description": "Total paid, taxes included. Required for price_guarantee."
    },
    "booked_date": {
      "type": "string",
      "description": "YYYY-MM-DD."
    },
    "lower_total": {
      "type": "number",
      "description": "Required for price_guarantee."
    },
    "tracking_id": {
      "type": "integer",
      "description": "Optional HotelRefund tracking for the same stay."
    },
    "new_check_in": {
      "type": "string",
      "description": "date_change: requested new check-in, YYYY-MM-DD. Omit to ask which dates are possible."
    },
    "lower_seen_at": {
      "type": "string",
      "description": "When the lower price was seen, e.g. 2026-10-02 14:30."
    },
    "new_check_out": {
      "type": "string",
      "description": "date_change: requested new check-out, YYYY-MM-DD."
    },
    "paid_currency": {
      "type": "string",
      "description": "ISO currency of paid_total."
    },
    "lower_currency": {
      "type": "string"
    },
    "letter_language": {
      "enum": [
        "en",
        "ko",
        "ja",
        "zh"
      ],
      "type": "string",
      "description": "Language of the text: en (default), ko, ja or zh. Usually the language the booking site or hotel reads."
    },
    "lower_price_site": {
      "enum": [
        "booking",
        "agoda",
        "trip",
        "expedia",
        "hotels",
        "other"
      ],
      "type": "string",
      "description": "Required for price_guarantee."
    },
    "cancellation_policy": {
      "enum": [
        "free_cancellation",
        "non_refundable"
      ],
      "type": "string"
    },
    "lower_price_site_other": {
      "type": "string"
    }
  }
}
    arguments 152 lines
  • get_price_history reads unknown 12h ago

    Return the recorded prices for one tracking (tracking_id): current, first, lowest and highest price, percentage change and trend since tracking started, and the time series of observed prices. Also returns booking_guidance — a book-now-or-wait signal computed from this stay's full tracked record (share of observations lower than now, distance from the median, overall spread, days left), and headline + summary sentences (in language: en, ko, ja or zh) that explain the read the same way the page does. track_page_url is the booking-decision page in that language. And report_url / csv_url: every observation with UTC timestamps as a printable page and a CSV, which people use as evidence for best-price-guarantee claims, refund requests and check-in negotiation. When available, seasonality adds the destination's forecast monthly rates for the hotel's star band (a separate scale from the tracked prices — it says whether the stay month is a high or low month for the city, and which nearby month is cheapest). A tracking created moments ago may report awaiting_first_price until its first check completes; no_rates means there is no sellable rate for these dates right now (sold out or not open yet) and it is re-checked daily.

    mcp-tool

    {
  "type": "object",
  "required": [
    "tracking_id"
  ],
  "properties": {
    "language": {
      "enum": [
        "en",
        "ko",
        "ja",
        "zh"
      ],
      "type": "string",
      "description": "Language for booking_guidance.headline/summary and track_page_url: en (default), ko, ja or zh."
    },
    "tracking_id": {
      "type": "integer",
      "description": "Tracking id from track_hotel_price or list_tracked_hotels."
    }
  }
}
    arguments 22 lines
  • search_hotels reads unknown 15h ago

    Resolve a hotel to the agoda_hotel_id that track_hotel_price needs. This is a lookup step, not a hotel search engine: it returns catalog entries (name, address, stars, rating, review count) and no prices — for prices, track the hotel or use list_hotel_deals. Give a city, region or airport name (Korean, Japanese, Chinese or English) and, when the user named a hotel, the hotel filter; the city is resolved to the best catalog match. A hotel name alone (no city) also works for well-reviewed hotels: it searches every city and returns each hotel with its city — confirm the city with the user before tracking. If it finds nothing, ask for the city. If several cities match, other_city_matches lists them — pass one of their city_id values (instead of city) to search that city. Typical flow: search_hotels → track_hotel_price → get_price_history.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "city": {
      "type": "string",
      "description": "City, region or airport name, e.g. \"Sapporo\", \"삿포로\", \"札幌\". Optional when hotel is given; otherwise required unless city_id is given."
    },
    "hotel": {
      "type": "string",
      "description": "Hotel name, e.g. \"Hilton Sapporo\", \"신라호텔\", \"ソウル新羅ホテル\". With a city it filters that city; without a city it searches well-reviewed hotels in every city. Omit (with a city) to list notable hotels."
    },
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "Max hotels to return (default 8)."
    },
    "city_id": {
      "type": "integer",
      "description": "Catalog city id from a previous result (other_city_matches). Overrides city."
    },
    "country": {
      "type": "string",
      "description": "Optional ISO 3166-1 alpha-2 country code, e.g. \"KR\". With a hotel name and no city, ranks equally matching hotels from this country first; other countries still appear. Pass it only when the user is looking in that country."
    }
  }
}
    arguments 27 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 80b0da7e1080cb8e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/80b0da7e1080cb8e/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/80b0da7e1080cb8e/badge.svg)](https://brick.blue/agent/80b0da7e1080cb8e?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.