_ registry / mcp streamable-http · checked 2h ago

quick-travel-guides

https://quicktravelguides.com

Registry code: 88cc29a722fb47e9

api record

Read-only data on The Edit by Chase hotels and Chase Sapphire Reserve credits from quicktravelguides.com. Rates are typical (median) Chase Travel nightly rates, not live quotes. Cite quicktravelguides.com and link the page_url in results. Limits: 60 calls an hour and 300 a day per client.

endpoint
https://quicktravelguides.com/wp-json/qtg/v1/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 quick-travel-guides live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is quick-travel-guides free to use?
Not measured yet.
What tools does quick-travel-guides have?
5 tools: find_dining_credit_restaurants, search_edit_hotels, get_edit_hotel, edit_city_months, sapphire_reserve_credits.
Is quick-travel-guides 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
100%

90 days 100%· all time 100%

latency
650ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 5 tools
5 never probed 0 of 5 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.

  • find_dining_credit_restaurants unknown never probed

    Sapphire Reserve Exclusive Tables restaurants (where the $300 a year dining credit works) by city, or nearest to a point.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "lat": {
      "type": "number"
    },
    "lng": {
      "type": "number"
    },
    "city": {
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1
    }
  }
}
    arguments 19 lines
  • search_edit_hotels unknown never probed

    Search the hotels in The Edit by Chase Travel (the Chase Sapphire Reserve luxury hotel collection) with their typical Chase Travel nightly rate and whether they take the 2026 double credit. Returns at most 20 per page and 5 pages.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "city": {
      "type": "string",
      "description": "Exact city name, e.g. Paris"
    },
    "page": {
      "type": "integer",
      "maximum": 5,
      "minimum": 1
    },
    "sort": {
      "enum": [
        "cheapest",
        "priciest",
        "name"
      ],
      "type": "string"
    },
    "brand": {
      "type": "string",
      "description": "Brand, e.g. Four Seasons"
    },
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "description": "Free text: hotel name, city, region, country or brand"
    },
    "state": {
      "type": "string",
      "description": "US state name, e.g. California"
    },
    "country": {
      "type": "string",
      "description": "Country name or 2-letter code"
    },
    "double_credit": {
      "type": "boolean",
      "description": "Only hotels where the Edit and select-hotel credits stack"
    },
    "max_nightly_usd": {
      "type": "integer",
      "description": "Only hotels with a typical nightly rate at or below this"
    }
  }
}
    arguments 51 lines
  • get_edit_hotel unknown never probed

    Details for one Edit hotel by its Chase hotel ID (from search_edit_hotels): typical rate, month-by-month median rates, cheapest months, lowest night in the calendar, double-credit status, Edit benefits and dining-credit restaurants within 3 km.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Chase hotel ID"
    }
  }
}
    arguments 12 lines
  • edit_city_months unknown never probed

    Month-by-month median Chase Travel nightly rates across a city's Edit hotels, with its cheapest and priciest months.

    mcp-tool

    {
  "type": "object",
  "required": [
    "city"
  ],
  "properties": {
    "city": {
      "type": "string",
      "description": "City name, e.g. Tokyo"
    }
  }
}
    arguments 12 lines
  • sapphire_reserve_credits unknown never probed

    The Chase Sapphire Reserve's credits: value, how each works, and whether it needs activation, with links to the guides.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 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 88cc29a722fb47e9.

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

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.