Sky High Party Rentals
REMOTE · MCP.SHPR.ME
Quote, cart and checkout for bounce house and water slide rentals in Houston, Austin and Dallas.
Available components
Last scanned (16 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1175 tokens (~235/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- “add_to_cart” added an optional parameter “operating_mode” cosmetic
- 22 Oct 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.shpr.me/hugo/public/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.shpr.me | CN=YE2,O=Let's Encrypt,C=US | 6 Sept 2026 | 5 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 67edab8e083a8b0f72ab4d64fe01e6ebda5 |
| SANs: mcp.shpr.me | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.shpr.me. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| me. | DS published | 45352 | 8 | Verified |
| shpr.me. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.shpr.me/hugo/public/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.shpr.me/hugo/public/mcp | HTTPS enforced | 301 | https://mcp.shpr.me/hugo/public/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_to_cart Add a rental to a cart ~390
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cart_id | string | – | The cart_id from an earlier add_to_cart, to add to the same cart. Leave out to start a new cart. |
| date | string | yes | Party date, YYYY-MM-DD |
| end_time | string | – | Party end, e.g. 18:00 or 6pm (default 4 hours after the start). The price depends on the length. |
| operating_mode | string | – | For a slide or combo that can run wet or dry: how the customer wants it. Ask them. Some units charge for wet use (a misting hose); the tool reports the charge. |
| overnight | boolean | – | true = keep it overnight, picked up after 8 AM the next morning |
| product | string | – | Product name, e.g. 'Turtle Beach water slide', when there is no product_id. |
| product_id | string | – | The product_id from build_quote or product_info. Preferred: it books exactly that product. |
| quantity | number | – | How many, default 1. A package whose name already lists its counts is quantity 1. |
| start_time | string | – | Party start, e.g. 14:00 or 2pm (default 12:00) |
| zip | string | yes | 5-digit delivery ZIP (selects Houston, Austin or Dallas) |
No output schema declared.
No examples provided.
build_quote Quote a rental for a date and ZIP ~345
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.
| Name | Type | Req | Description |
|---|---|---|---|
| coupon | string | – | 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 | string | – | When the party ends, in their words ("1pm"). For an attended rental, when it should stop running - not the pickup time. |
| event_date | string | yes | Event date YYYY-MM-DD |
| items | array | – | 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. |
| product_name | string | yes | Product name or close description |
| quantity | number | – | How many of this item, default 1 |
| start_time | string | – | 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 the… |
| zip | string | yes | 5-digit delivery zip the customer gave you |
No output schema declared.
No examples provided.
delivery_fee Delivery fee and minimum for a ZIP ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event_date | string | – | Event date YYYY-MM-DD, when the customer has mentioned it. Always include if known. |
| zip | string | yes | 5-digit delivery zip code |
No output schema declared.
No examples provided.
prepare_checkout Prepare checkout link ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cart_id | string | yes | The cart_id from add_to_cart |
No output schema declared.
No examples provided.
product_info Look up a rental ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event_date | string | – | 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 | string | yes | Product name or close description, e.g. 'Niagara water slide' |
| zip | string | – | 5-digit delivery zip, when known. Selects the right metro's pricing. |
No output schema declared.
No examples provided.
How do I install the Sky High Party Rentals MCP server?
Sky High Party Rentals is a hosted endpoint at https://mcp.shpr.me/hugo/public/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.shpr.me
claude mcp add --transport http com-skyhighpartyrentals-booking 'https://mcp.shpr.me/hugo/public/mcp'
What is the Sky High Party Rentals MCP server?
Sky High Party Rentals is an MCP server listed in the public MCP registry as com.skyhighpartyrentals/booking. Quote, cart and checkout for bounce house and water slide rentals in Houston, Austin and Dallas. This page covers its hosted endpoint (https://mcp.shpr.me/hugo/public/mcp).
Is the Sky High Party Rentals MCP server safe to use?
Sky High Party Rentals scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Sky High Party Rentals MCP server expose?
Sky High Party Rentals exposes 5 tools: product_info, build_quote, delivery_fee, add_to_cart, prepare_checkout. Their descriptions and schemas cost roughly 1,175 tokens of context every time the server is loaded.
Does the Sky High Party Rentals MCP server require authentication?
No. We connected to Sky High Party Rentals without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sky High Party Rentals MCP server still maintained?
Sky High Party Rentals is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Sky High Party Rentals MCP server?
VerifyMCP ran 13 checks on Sky High Party Rentals, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.