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

sky-high-party-rentals

https://mcp.shpr.me

Registry code: 3e3ecdc02b4fbb53

api record

Quote, cart and checkout for bounce house and water slide rentals in Houston, Austin and Dallas.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.shpr.me/hugo/public/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 sky-high-party-rentals live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is sky-high-party-rentals free to use?
Yes — the hub reached it with no key and no payment.
What tools does sky-high-party-rentals have?
5 tools: product_info, build_quote, delivery_fee, add_to_cart, prepare_checkout.
Is sky-high-party-rentals 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
491ms

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
1 open 4 never probed 1 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.

  • prepare_checkout open 2h ago

    Get a cart ready for checkout. Re-checks that everything is still available for the date and that the cart meets that date's minimum, then returns the items, the price breakdown (delivery, fees, tax, total, deposit due today), what the customer still has to enter, and handoff_url: a private link that opens this exact cart at checkout on any phone or computer. This tool never pays or places the order: the customer pays on that page, or, once they have authorized it, you complete checkout there for them. Give handoff_url to the customer only.

    mcp-tool

    {
      "type": "object",
      "required": [
        "cart_id"
      ],
      "properties": {
        "cart_id": {
          "type": "string",
          "description": "The cart_id from add_to_cart"
        }
      }
    }
    arguments 12 lines
  • product_info unknown never probed

    Look up a Sky High rental product by name. Returns the page URL, units in stock, how many times families have booked it, and price. ALWAYS pass event_date (and zip when you know it) - with a date this returns the EXACT price for that date and whether it is available, which you should quote directly. Prices returned here are LIVE - prefer them over any knowledge-file price, and never send the customer to the product page to find a price this tool can give you.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_name"
      ],
      "properties": {
        "zip": {
          "type": "string",
          "description": "5-digit delivery zip, when known. Selects the right metro's pricing."
        },
        "event_date": {
          "type": "string",
          "description": "Event date YYYY-MM-DD. Always pass it when the customer has said their date - it returns the exact price for that day."
        },
        "product_name": {
          "type": "string",
          "description": "Product name or close description, e.g. 'Niagara water slide'"
        }
      }
    }
    arguments 20 lines
  • build_quote unknown never probed

    Build a complete, real quote for one rental on a specific date and delivery zip: exact dated item price, availability, delivery fee, that date's minimum order, the total, and the booking link. Use this the moment you know the product, the date and the zip - it is the fastest way to answer 'how much?' properly. If you are missing the date or zip, ask the customer for it (never guess a zip from their IP or city) and then call this.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_name",
        "event_date",
        "zip"
      ],
      "properties": {
        "zip": {
          "type": "string",
          "description": "5-digit delivery zip the customer gave you"
        },
        "items": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "product_name"
            ],
            "properties": {
              "qty": {
                "type": "number"
              },
              "product_name": {
                "type": "string"
              }
            }
          },
          "description": "Two or more items for the SAME party: pass them all here (product_name = the first one) to get ONE order total with one delivery fee. Never add up separate quotes."
        },
        "coupon": {
          "type": "string",
          "description": "Optional: CHAT10 once you have offered it, or a code the customer typed. Returns with_coupon, the exact discounted total, so you never do discount math yourself."
        },
        "end_time": {
          "type": "string",
          "description": "When the party ends, in their words (\"1pm\"). For an attended rental, when it should stop running - not the pickup time."
        },
        "quantity": {
          "type": "number",
          "description": "How many of this item, default 1"
        },
        "event_date": {
          "type": "string",
          "description": "Event date YYYY-MM-DD"
        },
        "start_time": {
          "type": "string",
          "description": "When the party starts, in their words (\"10am\", \"2:30pm\"). For a rental with an attendant (mechanical bull etc.), when it should start running. Pass start_time AND end_time whenever they have said them: the price depends on party length."
        },
        "product_name": {
          "type": "string",
          "description": "Product name or close description"
        }
      }
    }
    arguments 56 lines
  • delivery_fee unknown never probed

    Look up the delivery fee and minimum order for a Texas delivery zip code. Use when a customer asks what delivery costs or what the minimum order is for their area. ALWAYS pass event_date when the customer has mentioned their party date - minimum orders vary by date and the dated answer is exact. Without a date the answer is the general rule.

    mcp-tool

    {
      "type": "object",
      "required": [
        "zip"
      ],
      "properties": {
        "zip": {
          "type": "string",
          "description": "5-digit delivery zip code"
        },
        "event_date": {
          "type": "string",
          "description": "Event date YYYY-MM-DD, when the customer has mentioned it. Always include if known."
        }
      }
    }
    arguments 16 lines
  • add_to_cart unknown never probed

    Add one rental to a real Sky High cart for a party date, delivery ZIP and hours, and get back a cart_id. Call build_quote first if the customer has not seen the price. To add more items to the SAME party, call again with the cart_id from the first call (one cart, one delivery fee). Safe to repeat: an item already in the cart is not added twice. Added is NOT reserved: nothing is held until the customer pays at checkout. Next step: prepare_checkout with the cart_id.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product",
        "date",
        "zip"
      ],
      "properties": {
        "zip": {
          "type": "string",
          "description": "5-digit delivery ZIP (selects Houston, Austin or Dallas)"
        },
        "date": {
          "type": "string",
          "description": "Party date, YYYY-MM-DD"
        },
        "cart_id": {
          "type": "string",
          "description": "The cart_id from an earlier add_to_cart, to add to the same cart. Leave out to start a new cart."
        },
        "product": {
          "type": "string",
          "description": "Product name, e.g. 'Turtle Beach water slide'. Use the name build_quote or product_info returned."
        },
        "end_time": {
          "type": "string",
          "description": "Party end, e.g. 18:00 or 6pm (default 4 hours after the start). The price depends on the length."
        },
        "quantity": {
          "type": "number",
          "description": "How many, default 1. A package whose name already lists its counts is quantity 1."
        },
        "overnight": {
          "type": "boolean",
          "description": "true = keep it overnight, picked up after 8 AM the next morning"
        },
        "start_time": {
          "type": "string",
          "description": "Party start, e.g. 14:00 or 2pm (default 12:00)"
        }
      }
    }
    arguments 42 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 3e3ecdc02b4fbb53.

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