Rate Ranger
REMOTE · WWW.RATERANGER.IO · SCANNED SEP 25
Watch a hotel's price after your user booked it, and email them when it drops enough to rebook.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 335 tokens (~167/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Rate Ranger MCP server?
Rate Ranger is a hosted endpoint at https://www.rateranger.io/api/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.
remote · www.rateranger.io
claude mcp add --transport http io-rateranger-hotel-price-monitor 'https://www.rateranger.io/api/mcp'
{
"mcpServers": {
"io-rateranger-hotel-price-monitor": {
"url": "https://www.rateranger.io/api/mcp"
}
}
} {
"servers": {
"io-rateranger-hotel-price-monitor": {
"type": "http",
"url": "https://www.rateranger.io/api/mcp"
}
}
} [mcp_servers.io-rateranger-hotel-price-monitor] url = "https://www.rateranger.io/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-rateranger-hotel-price-monitor": {
"type": "remote",
"url": "https://www.rateranger.io/api/mcp",
"enabled": true
}
}
} openclaw mcp add io-rateranger-hotel-price-monitor --url 'https://www.rateranger.io/api/mcp' --transport streamable-http
mcp_servers:
io-rateranger-hotel-price-monitor:
url: "https://www.rateranger.io/api/mcp" {
"McpServers": {
"io-rateranger-hotel-price-monitor": {
"Transport": "http",
"Url": "https://www.rateranger.io/api/mcp"
}
}
} assistant mcp add io-rateranger-hotel-price-monitor -t streamable-http -u 'https://www.rateranger.io/api/mcp'
{
"mcpServers": {
"io-rateranger-hotel-price-monitor": {
"type": "http",
"url": "https://www.rateranger.io/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://www.rateranger.io/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rateranger.io | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 8 Feb 2026 | 9 Mar 2027 | RSA 2048 | SHA256-RSA | 2bc8ee49f1421d0c2526a752ead548b |
| SANs: rateranger.io, www.rateranger.io | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.rateranger.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| rateranger.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.rateranger.io/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.rateranger.io/api/mcp | HTTPS enforced | 301 | https://www.rateranger.io/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_hotel_booking ~85
Check one booking you submitted, using the read token returned at submission. Use it to find out whether the traveller has confirmed yet: `confirmed` is false until they click the emailed link, and while it is false nothing is being monitored. Check here before telling your user their booking is being tracked.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | The read_token from submit_hotel_booking. |
No output schema declared.
No examples provided.
submit_hotel_booking ~210
Enrol a hotel booking the traveller has ALREADY made into free price monitoring. Rate Ranger watches what the hotel charges for the same dates and emails them if it drops far enough to be worth rebooking. IMPORTANT: this monitors nothing on its own. The traveller is emailed one confirmation link, and no price is checked until they click it. Tell your user to expect that email. Do not tell them the booking is being tracked until check_hotel_booking says it is. Unconfirmed bookings are deleted after 7 days. Use this only for a booking that already exists. It does not search for or make reservations.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Optional name for you, such as my-assistant/1.0. Logged for debugging only. |
| bookings | array | yes | One to ten bookings for that traveller. |
| string | yes | The traveller's own email address. One per call. The confirmation and any later price alerts go here, so it must be an address they actually read. |
No output schema declared.
No examples provided.
What is the Rate Ranger MCP server?
Rate Ranger is an MCP server listed in the public MCP registry as io.rateranger/hotel-price-monitor. Watch a hotel's price after your user booked it, and email them when it drops enough to rebook. This page covers its hosted endpoint (https://www.rateranger.io/api/mcp).
Is the Rate Ranger MCP server safe to use?
Rate Ranger scores 75 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 Rate Ranger MCP server expose?
Rate Ranger exposes 2 tools: submit_hotel_booking, check_hotel_booking. Their descriptions and schemas cost roughly 295 tokens of context every time the server is loaded.
Does the Rate Ranger MCP server require authentication?
No. We connected to Rate Ranger without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Rate Ranger MCP server still maintained?
Rate Ranger is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.