Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Rate Ranger

REMOTE · WWW.RATERANGER.IO

Watch a hotel's price after your user booked it, and email them when it drops enough to rebook.

0 this week 79 Trust /100

Last scanned (12 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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
Transport & Reachability100
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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 7 Nov 26 +1
    • Stability: 0.97 → pass security
  • 6 Nov 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
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
Diagnostics

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 21 Nov 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. DS published 38690 8 Verified
rateranger.io. No DS 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
MCP tools · 2 exposed · ~295 tokens

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 →

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

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

NameTypeReqDescription
agentstring–Optional name for you, such as my-assistant/1.0. Logged for debugging only.
bookingsarrayyesOne to ten bookings for that traveller.
emailstringyesThe 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.

Install

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

# add to Claude Code
claude mcp add --transport http io-rateranger-hotel-price-monitor 'https://www.rateranger.io/api/mcp'
Common questions

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 79 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Rate Ranger MCP server?

VerifyMCP ran 12 checks on Rate Ranger, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Rate Ranger: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.