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

threshold-stays

https://threshold.rentals

Registry code: dc030b23884b5081

api record

Threshold lists independent vacation rentals whose hosts are verified by Threshold. Search and availability are cached; always create a quote before telling the guest a final price. Show the guest the quote's house_rules and refund_schedule before checkout, and only set house_rules_accepted after they agree. Never invent amenities or answers: if the property record and FAQ don't answer a question, say so or use ask_host. Property records give an approximate location only. The exact street address, check-in instructions and the host's phone number and email are deliberately withheld: Threshold…

endpoint
https://threshold.rentals/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 threshold-stays live?
Yes — it answered the hub's last check (checked 17m ago). It answered 99% of checks over the last 30 days.
Is threshold-stays free to use?
Yes — the hub reached it with no key and no payment.
What tools does threshold-stays have?
10 tools: get_property, get_quote, cancel_booking, get_booking, ask_host, send_message, request_booking, check_availability, ….
Is threshold-stays 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
99.4%

90 days 99.6%· all time 99.6%

latency
258ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 270 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • search verified vacation rentals
  • check rental availability
  • get a binding price quote
  • request a booking
  • message a host
takes → gives
text, data → data, text
tools
6 reads1 changes data1 moves money2 sends messages
_ 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 10 tools
1 open 9 never probed 1 of 10 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.

  • search_stays reads open 17m ago

    Find verified independent vacation rentals. Filters are strict: every listed amenity must be present. With dates, results include a cached availability signal and an indicative all-in total (no guest service fee). Maps to GET /v1/search.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "pets": {
          "type": "integer",
          "minimum": 0,
          "description": "Number of pets. Only places that allow that many are returned. Service animals don't count as pets."
        },
        "limit": {
          "type": "integer",
          "default": 8,
          "maximum": 20,
          "description": "Most results to return, 1 to 50. Default 8."
        },
        "place": {
          "type": "string",
          "description": "Town and state/country, e.g. 'Asheville, NC'. Use near_lat/near_lng instead when you have coordinates."
        },
        "adults": {
          "type": "integer",
          "default": 2,
          "minimum": 1,
          "description": "Number of adults. Default 2."
        },
        "infants": {
          "type": "integer",
          "minimum": 0,
          "description": "Number of infants under 2."
        },
        "check_in": {
          "type": "string",
          "format": "date",
          "description": "Arrival date, YYYY-MM-DD. With check_out, only places free for the whole stay are returned, with an indicative total."
        },
        "children": {
          "type": "integer",
          "minimum": 0,
          "description": "Number of children aged 2 to 12."
        },
        "near_lat": {
          "type": "number",
          "description": "Latitude to search around, with near_lng. Use instead of place when you have coordinates."
        },
        "near_lng": {
          "type": "number",
          "description": "Longitude to search around, with near_lat."
        },
        "amenities": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Amenity codes, e.g. hot_tub, wifi, ev_charger, dedicated_workspace, pool, fireplace_wood."
        },
        "check_out": {
          "type": "string",
          "format": "date",
          "description": "Departure date, YYYY-MM-DD (the morning the guests leave)."
        },
        "radius_km": {
          "type": "number",
          "default": 30,
          "description": "How far from near_lat/near_lng to search, in kilometres. Default 30."
        },
        "instant_only": {
          "type": "boolean",
          "description": "True to return only places that confirm instantly, without waiting for the host."
        },
        "min_bedrooms": {
          "type": "integer",
          "description": "Fewest bedrooms the place must have."
        },
        "max_total_usd": {
          "type": "number",
          "description": "Maximum all-in total in dollars. Requires dates."
        },
        "min_wifi_mbps": {
          "type": "number",
          "description": "Lowest Wi-Fi download speed needed, in megabits per second."
        },
        "step_free_entrance": {
          "type": "boolean",
          "description": "True to return only places with a step-free way in."
        }
      }
    }
    arguments 86 lines
  • get_property reads unknown 17m ago

    Full record for one property: beds by room, amenities with details, access and stairs, rules, host FAQ, policies, and verification status. The location is approximate on purpose: the exact address and the host's direct contact details are not in the record and are sent to the guest after a confirmed booking, so if asked, say that rather than that they are missing. Maps to GET /v1/properties/{id}.

    mcp-tool

    {
      "type": "object",
      "required": [
        "property_id"
      ],
      "properties": {
        "property_id": {
          "type": "string",
          "description": "The property's id, from search_stays (starts with prop_)."
        }
      }
    }
    arguments 12 lines
  • get_quote reads unknown 17m ago

    Itemized, binding price for exact dates and party, after re-checking the host's live calendars. Valid 10 minutes. Returns house rules and an exact refund schedule to show the guest. Does not reserve the dates. Maps to POST /v1/properties/{id}/quotes.

    mcp-tool

    {
      "type": "object",
      "required": [
        "property_id",
        "check_in",
        "check_out",
        "adults"
      ],
      "properties": {
        "pets": {
          "type": "integer",
          "default": 0,
          "minimum": 0,
          "description": "Number of pets. Default 0. Service animals don't count."
        },
        "adults": {
          "type": "integer",
          "minimum": 1,
          "description": "Number of adults (at least 1)."
        },
        "infants": {
          "type": "integer",
          "default": 0,
          "minimum": 0,
          "description": "Number of infants under 2. Default 0."
        },
        "check_in": {
          "type": "string",
          "format": "date",
          "description": "Arrival date, YYYY-MM-DD."
        },
        "children": {
          "type": "integer",
          "default": 0,
          "minimum": 0,
          "description": "Number of children aged 2 to 12. Default 0."
        },
        "check_out": {
          "type": "string",
          "format": "date",
          "description": "Departure date, YYYY-MM-DD."
        },
        "property_id": {
          "type": "string",
          "description": "The property's id, from search_stays."
        }
      }
    }
    arguments 48 lines
  • cancel_booking changes data unknown never probed

    Two-step. First call with confirm=false to see what the guest gets back if they cancel now (nothing changes). Tell the guest that refund and get their go-ahead, then call again with confirm=true and expected_refund_cents set to the refund amount from the first call. If the refund changed in between, the call fails with refund_changed instead of cancelling. Refunds go to the guest's card automatically. Pass guest_email (the email the booking was made with) unless you connect with an agent token.

    mcp-tool

    {
      "type": "object",
      "required": [
        "booking_id",
        "confirm"
      ],
      "properties": {
        "confirm": {
          "type": "boolean",
          "description": "False to preview the refund without changing anything; true to cancel."
        },
        "booking_id": {
          "type": "string",
          "description": "The booking or request to cancel."
        },
        "guest_email": {
          "type": "string",
          "format": "email",
          "description": "The email the booking was made with. Needed unless you connect with an agent token."
        },
        "expected_refund_cents": {
          "type": "integer",
          "description": "Required when confirm is true: refund.amount from the confirm=false call."
        }
      }
    }
    arguments 26 lines
  • get_booking reads unknown never probed

    Status, amounts, refund schedule, guest ID verification link, and when arrival details will be sent. Maps to GET /v1/bookings/{id}. Pass guest_email (the email the booking was made with) unless you connect with an agent token.

    mcp-tool

    {
      "type": "object",
      "required": [
        "booking_id"
      ],
      "properties": {
        "booking_id": {
          "type": "string",
          "description": "The booking's id, from request_booking (starts with bkg_)."
        },
        "guest_email": {
          "type": "string",
          "format": "email",
          "description": "The email the booking was made with. Needed unless you connect with an agent token."
        }
      }
    }
    arguments 17 lines
  • ask_host sends messages unknown never probed

    Send a question the property record and FAQ don't answer. The answer arrives later; tell the guest you'll follow up. Don't include the guest's contact details. Maps to POST /v1/properties/{id}/questions.

    mcp-tool

    {
      "type": "object",
      "required": [
        "property_id",
        "question"
      ],
      "properties": {
        "question": {
          "type": "string",
          "maxLength": 500,
          "description": "The guest's question, in plain words, up to 500 characters. The host's answer may be added to the listing's FAQ."
        },
        "property_id": {
          "type": "string",
          "description": "The property the question is about."
        }
      }
    }
    arguments 18 lines
  • send_message sends messages unknown never probed

    Send a message to the host on the guest's behalf, e.g. a question about check-in or a late arrival. Only send what the guest asked you to say. The host is emailed and replies appear in get_messages. Open from the request until two weeks after check-out.

    mcp-tool

    {
      "type": "object",
      "required": [
        "booking_id",
        "body"
      ],
      "properties": {
        "body": {
          "type": "string",
          "maxLength": 2000,
          "description": "The message to the host, in the guest's words, up to 2,000 characters."
        },
        "booking_id": {
          "type": "string",
          "description": "The booking the message is about."
        },
        "guest_email": {
          "type": "string",
          "format": "email",
          "description": "The email the booking was made with. Needed unless you connect with an agent token."
        }
      }
    }
    arguments 23 lines
  • request_booking moves money unknown never probed

    Request a stay from a quote. Set house_rules_accepted only after the guest has seen and agreed to the quote's house_rules. If the quote's payment.collected_by is "threshold", the booking starts as awaiting_payment and the response includes payment_url: the guest must open payment_url and add a card within 60 minutes, after which the host gets the request (status pending_host_confirmation). Otherwise the request goes to the host immediately and the host arranges payment after accepting. Returns the booking and a status link to give the guest; poll get_booking for changes.

    mcp-tool

    {
      "type": "object",
      "required": [
        "quote_id",
        "first_name",
        "last_name",
        "email",
        "house_rules_accepted"
      ],
      "properties": {
        "email": {
          "type": "string",
          "format": "email",
          "description": "The guest's email: confirmations, the payment link and the host's messages go there."
        },
        "phone": {
          "type": "string",
          "description": "The guest's phone number in international format, e.g. +15551234567. Optional."
        },
        "quote_id": {
          "type": "string",
          "description": "The quote being booked, from get_quote (starts with quo_)."
        },
        "last_name": {
          "type": "string",
          "description": "The guest's last name."
        },
        "first_name": {
          "type": "string",
          "description": "The guest's first name."
        },
        "special_requests": {
          "type": "string",
          "maxLength": 500,
          "description": "Anything the guest wants the host to know, in their words (arrival time, a question). Optional, up to 500 characters."
        },
        "house_rules_accepted": {
          "type": "boolean",
          "description": "True only after the guest has seen and agreed to the quote's house_rules."
        }
      }
    }
    arguments 42 lines
  • check_availability reads unknown 16h ago

    Day-by-day availability and indicative nightly prices for up to 180 days. Cached; use get_quote to confirm. Useful when the guest's dates are flexible. Maps to GET /v1/properties/{id}/availability.

    mcp-tool

    {
      "type": "object",
      "required": [
        "property_id",
        "from",
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "format": "date",
          "description": "Exclusive"
        },
        "from": {
          "type": "string",
          "format": "date",
          "description": "First night to check, YYYY-MM-DD."
        },
        "property_id": {
          "type": "string",
          "description": "The property's id, from search_stays."
        }
      }
    }
    arguments 24 lines
  • get_messages reads unknown 16h ago

    The conversation between the guest and the host about a booking, oldest first (including the guest's note with the request and the host's note when accepting or declining). Use it to relay the host's replies. Pass guest_email (the email the booking was made with) unless you connect with an agent token.

    mcp-tool

    {
      "type": "object",
      "required": [
        "booking_id"
      ],
      "properties": {
        "booking_id": {
          "type": "string",
          "description": "The booking's id, from request_booking (starts with bkg_)."
        },
        "guest_email": {
          "type": "string",
          "format": "email",
          "description": "The email the booking was made with. Needed unless you connect with an agent token."
        }
      }
    }
    arguments 17 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 dc030b23884b5081.

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

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.