# HotelRefund Price Tracker (remote · hotelrefund.net)

Tracks Agoda hotel prices for your dates, keeps checking, and shows what changed — with evidence.

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `hotelrefund.net`: 70/100 (this document), [markdown](https://verifymcp.io/servers/net-hotelrefund-price-tracker/hotelrefund.md), [page](https://verifymcp.io/servers/net-hotelrefund-price-tracker/hotelrefund)

## Channel facts

- Endpoint: `https://hotelrefund.net/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2269 tokens (~283/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_refund_guide" implies "refund" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the HotelRefund Price Tracker MCP server?

HotelRefund Price Tracker is a hosted endpoint at https://hotelrefund.net/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.

### Claude

```bash
claude mcp add --transport http net-hotelrefund-price-tracker 'https://hotelrefund.net/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "net-hotelrefund-price-tracker": {
      "url": "https://hotelrefund.net/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "net-hotelrefund-price-tracker": {
      "type": "http",
      "url": "https://hotelrefund.net/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.net-hotelrefund-price-tracker]
url = "https://hotelrefund.net/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-hotelrefund-price-tracker": {
      "type": "remote",
      "url": "https://hotelrefund.net/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add net-hotelrefund-price-tracker --url 'https://hotelrefund.net/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  net-hotelrefund-price-tracker:
    url: "https://hotelrefund.net/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "net-hotelrefund-price-tracker": {
      "Transport": "http",
      "Url": "https://hotelrefund.net/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add net-hotelrefund-price-tracker -t streamable-http -u 'https://hotelrefund.net/mcp'
```

### Other

```json
{
  "mcpServers": {
    "net-hotelrefund-price-tracker": {
      "type": "http",
      "url": "https://hotelrefund.net/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 70, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “track_hotel_price” rewrote its description, which is the text the model reads

### 2026-09-19 (score 69, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “track_hotel_price” rewrote its description, which is the text the model reads

### 2026-09-18 (score 69, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “track_hotel_price” rewrote its description, which is the text the model reads

### 2026-09-17 (score 68, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “track_hotel_price” rewrote its description, which is the text the model reads

### 2026-09-16 (score 68, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “track_hotel_price” rewrote its description, which is the text the model reads

### 2026-09-15 (score 67, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “track_hotel_price” rewrote its description, which is the text the model reads

### 2026-09-14 (score 67, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “track_hotel_price” rewrote its description, which is the text the model reads

### 2026-09-13 (score 66, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “track_hotel_price” rewrote its description, which is the text the model reads

## MCP tools (8)

### `search_hotels` (~266 tokens)

Find the agoda_hotel_id for a hotel

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. 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.

Input parameters:

- `city` (string): City, region or airport name, e.g. "Sapporo", "삿포로", "札幌". Required unless city_id is given.
- `city_id` (integer): Catalog city id from a previous result (other_city_matches). Overrides city.
- `hotel` (string): Optional hotel-name filter within the city, e.g. "Hilton", "힐튼". Omit to list notable hotels.
- `limit` (integer): Max hotels to return (default 8).

### `track_hotel_price` (~432 tokens)

Start tracking a hotel price

Today is 2026-09-20 (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-09-19 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).

Input parameters:

- `agoda_hotel_id` (integer, required): Hotel id from search_hotels.
- `check_in` (string, required): Check-in date, YYYY-MM-DD (today up to 540 days ahead).
- `check_out` (string, required): Check-out date, YYYY-MM-DD (after check_in, stay of 60 nights or less).
- `currency` (string): Optional ISO currency for recorded prices: KRW, JPY, USD, EUR, TWD, HKD, CNY, SGD, THB, GBP, AUD or VND. Defaults by language.
- `language` (string): Optional locale for the tracked rate: ko-kr, ja-jp, en-us, zh-cn, zh-tw or zh-hk (default en-us).

### `get_price_history` (~292 tokens)

Get price history for a tracking

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 own observations, with the trend slope, volatility, days left, a short-horizon predicted range, and headline + summary sentences (in language: en, ko, ja or zh) that explain the read the same way the page does, including when a price jump was ignored as a level shift. 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.

Input parameters:

- `language` (string): Language for booking_guidance.headline/summary and track_page_url: en (default), ko, ja or zh.
- `tracking_id` (integer, required): Tracking id from track_hotel_price or list_tracked_hotels.

### `list_tracked_hotels` (~94 tokens)

List publicly tracked hotels

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.

Input parameters:

- `language` (string): Language of each track_page_url: en (default), ko, ja or zh.
- `limit` (integer): Max items to return (default 20).

### `list_hotel_deals` (~228 tokens)

List today's hotel deals

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.

Input parameters:

- `city` (string): Optional city, region or airport name, e.g. "Tokyo", "도쿄", "東京". Omit for the worldwide list.
- `city_id` (integer): Catalog city id from a previous search_hotels or list_hotel_deals result. Overrides city.
- `limit` (integer): Max deals to return (default 20).

### `get_hotel_price_calendar` (~331 tokens)

Price by check-in date for one hotel

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.

Input parameters:

- `agoda_hotel_id` (integer, required): Hotel id from search_hotels.
- `currency` (string): KRW, JPY, USD, EUR, TWD, HKD, CNY, SGD, THB, GBP, AUD or VND (default USD).
- `days` (integer): How many consecutive check-in dates (default 28, max 35).
- `language` (string): Agoda locale for the rate: ko-kr, ja-jp, en-us, zh-cn, zh-tw or zh-hk (default en-us).
- `nights` (integer): Stay length for every date (default 1).
- `start_date` (string): First check-in date to show, YYYY-MM-DD (default today; past dates are moved to today).

### `get_refund_guide` (~178 tokens)

Read a hotel refund or cancellation guide

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.

Input parameters:

- `language` (string): Language for the returned url: en (default), ko, ja or zh.
- `topic` (string): 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.

### `get_service_status` (~77 tokens)

Check service status and coverage

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/net-hotelrefund-price-tracker/hotelrefund#diagnostics

## Score history

- 2026-09-20: 70
- 2026-09-19: 69
- 2026-09-18: 69
- 2026-09-17: 68
- 2026-09-16: 68
- 2026-09-15: 67
- 2026-09-14: 67
- 2026-09-13: 66
- 2026-09-12: 66
- 2026-09-11: 65
- 2026-09-10: 65
- 2026-09-09: 65
- 2026-09-08: 64
- 2026-09-07: 64
- 2026-09-06: 63
- 2026-09-05: 63
- 2026-09-04: 62
- 2026-09-03: 63
- 2026-09-02: 64
- 2026-09-01: 63

## Common questions

### What is the HotelRefund Price Tracker MCP server?

HotelRefund Price Tracker is an MCP server listed in the public MCP registry as net.hotelrefund/price-tracker. Tracks Agoda hotel prices for your dates, keeps checking, and shows what changed, with evidence. This page covers its hosted endpoint (https://hotelrefund.net/mcp).

### Is the HotelRefund Price Tracker MCP server safe to use?

HotelRefund Price Tracker scores 70 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 HotelRefund Price Tracker MCP server expose?

HotelRefund Price Tracker exposes 8 tools: search_hotels, track_hotel_price, get_price_history, list_tracked_hotels, list_hotel_deals, and 3 more. Their descriptions and schemas cost roughly 1,898 tokens of context every time the server is loaded.

### Does the HotelRefund Price Tracker MCP server require authentication?

No. We connected to HotelRefund Price Tracker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the HotelRefund Price Tracker MCP server still maintained?

HotelRefund Price Tracker is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://hotelrefund.net/mcp
- Website: https://hotelrefund.net/track
- Changelog RSS feed: https://verifymcp.io/servers/net-hotelrefund-price-tracker/hotelrefund.xml
- Changelog JSON feed: https://verifymcp.io/servers/net-hotelrefund-price-tracker/hotelrefund.json
- HTML version of this page: https://verifymcp.io/servers/net-hotelrefund-price-tracker/hotelrefund