_ registry / mcp streamable-http · checked 41m ago

rate-ranger

https://www.rateranger.io

Registry code: 337224cdf9b58aea

api record

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.

endpoint
https://www.rateranger.io/api/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 rate-ranger live?
Yes — it answered the hub's last check (checked 41m ago). It answered 98% of checks over the last 30 days.
Is rate-ranger free to use?
Not measured yet.
What tools does rate-ranger have?
2 tools: check_hotel_booking, submit_hotel_booking.
Is rate-ranger 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
97.8%

90 days 98.7%· all time 98.7%

latency
405ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 312 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • monitor a booked hotel's price
  • check hotel price monitoring status
takes → gives
data → data
tools
1 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 2 tools
2 never probed 0 of 2 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.

  • check_hotel_booking reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "token"
      ],
      "properties": {
        "token": {
          "type": "string",
          "description": "The read_token from submit_hotel_booking."
        }
      }
    }
    arguments 12 lines
  • submit_hotel_booking changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "email",
        "bookings"
      ],
      "properties": {
        "agent": {
          "type": "string",
          "description": "Optional name for you, such as my-assistant/1.0. Logged for debugging only."
        },
        "email": {
          "type": "string",
          "description": "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."
        },
        "bookings": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "hotel_name",
              "city",
              "country",
              "check_in_date",
              "check_out_date",
              "total_price"
            ],
            "properties": {
              "city": {
                "type": "string",
                "description": "City, not district or area."
              },
              "country": {
                "type": "string",
                "description": "ISO 3166-1 alpha-2, for example JP or ID. Required, and it matters more than it looks: it decides which rate source can find the hotel at all."
              },
              "currency": {
                "type": "string",
                "description": "ISO 4217. Defaults to USD."
              },
              "num_rooms": {
                "type": "integer",
                "description": "Defaults to 1."
              },
              "room_type": {
                "type": "string",
                "description": "Free text. Optional."
              },
              "hotel_name": {
                "type": "string",
                "description": "The property as it is normally listed. Closer to the official name is better; it is matched against live hotel data."
              },
              "num_guests": {
                "type": "integer",
                "description": "Defaults to 2."
              },
              "total_price": {
                "type": "number",
                "description": "The whole cost of the stay, not a nightly rate. Decimals are fine here; only the web form restricts them."
              },
              "check_in_date": {
                "type": "string",
                "description": "YYYY-MM-DD, in the future."
              },
              "check_out_date": {
                "type": "string",
                "description": "YYYY-MM-DD, after check-in."
              },
              "booking_platform": {
                "type": "string",
                "description": "Where they booked: booking.com, expedia, hotels.com, agoda, trip.com, priceline, direct, or other."
              }
            }
          },
          "maxItems": 10,
          "minItems": 1,
          "description": "One to ten bookings for that traveller."
        }
      }
    }
    arguments 80 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 337224cdf9b58aea.

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

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.