Productivity

rateranger.io

Tracks hotel booking prices and notifies users of price decreases for potential refunds.

1 endpoint2 known toolsFirst detected September 3, 2026Last detected September 3, 2026

ENDPOINT 1

https://www.rateranger.io/api/mcp

No auth detected

MCP server metadata

Name: rate-ranger
Version: 1.0.0

Capabilities

tools

Server instructions

Rate Ranger watches a hotel's price after the traveller has already booked, and emails them if it drops enough to be worth rebooking. A submission monitors nothing until the traveller confirms by email.

Known tools 2

submit_hotel_booking

Enrol a hotel booking the traveller has ALREADY made into free price monitoring.

Inferred read-only

check_hotel_booking

Check one booking you submitted, using the read token returned at submission.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.rate-ranger]
url = "https://www.rateranger.io/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "rate-ranger": {
      "type": "http",
      "url": "https://www.rateranger.io/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: rate-ranger
Remote MCP URL: https://www.rateranger.io/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "rate-ranger": {
      "url": "https://www.rateranger.io/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "rate-ranger": {
      "type": "http",
      "url": "https://www.rateranger.io/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "rate-ranger",
  "transport": "streamable-http",
  "url": "https://www.rateranger.io/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.