Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Parky — Park Planning

REMOTE · MCP.PARKYPASS.COM · SCANNED OCT 7

Find Disney and Universal rides, posted waits, park hours, and crowd forecasts with Parky.

+2 this week 76 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1922 tokens (~128/item across 15 items; 15 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 Management33
  • Stability observed for 10 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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 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
Install

How do I install the Parky — Park Planning MCP server?

Parky — Park Planning is a hosted endpoint at https://mcp.parkypass.com/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.parkypass.com

# add to Claude Code
claude mcp add --transport http com-parkypass-parky 'https://mcp.parkypass.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-parkypass-parky": {
      "url": "https://mcp.parkypass.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-parkypass-parky": {
      "type": "http",
      "url": "https://mcp.parkypass.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-parkypass-parky]
url = "https://mcp.parkypass.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-parkypass-parky": {
      "type": "remote",
      "url": "https://mcp.parkypass.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-parkypass-parky --url 'https://mcp.parkypass.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-parkypass-parky:
    url: "https://mcp.parkypass.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-parkypass-parky": {
      "Transport": "http",
      "Url": "https://mcp.parkypass.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-parkypass-parky -t streamable-http -u 'https://mcp.parkypass.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-parkypass-parky": {
      "type": "http",
      "url": "https://mcp.parkypass.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “parky_get_hours” rewrote its description, which is the text the model reads security
    • Tool “parky_get_waits” rewrote its description, which is the text the model reads security
    • Schema quality: 506 → 1922 ▼ functional
    • Server version: 0.1.0 → 0.2.0 functional
    • New tool “parky_get_best_time” functional
    • New tool “parky_get_bus_times” functional
    • New tool “parky_get_event_nights” functional
    • New tool “parky_get_lightning_lane” functional
    • New tool “parky_get_park_availability” functional
    • New tool “parky_get_park_conditions” functional
    • New tool “parky_get_ride_facts” functional
    • New tool “parky_get_ride_outages” functional
    • New tool “parky_get_ride_reliability” functional
    • New tool “parky_get_showtimes” functional
    • New tool “parky_get_ticket_prices” functional
    • “parky_get_crowd_outlook” reworded the description of “park_id” cosmetic
    • “parky_get_hours” reworded the description of “days” cosmetic
    • “parky_get_hours” reworded the description of “park_id” cosmetic
    • “parky_get_waits” reworded the description of “park_id” cosmetic
  • 3 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 73

    First indexed and scored.

Diagnostics

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 7 Oct 2026 · Probed https://mcp.parkypass.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.parkypass.com CN=YE2,O=Let's Encrypt,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA384 5bcbaaa0ee729fb28df37f227f71c439800
SANs: mcp.parkypass.com
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.parkypass.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
parkypass.com. absent 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.parkypass.com/mcp Verified 200
http (plaintext) http://mcp.parkypass.com/mcp HTTPS enforced 308 https://mcp.parkypass.com/mcp
MCP tools · 15 exposed · ~1,806 tokens

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 →

Tool Tokens
parky_find_experience ~91

Use this when a visitor names or describes a park or ride and you need its canonical Parky ID. Searches only parks in Parky's current Disney and Universal release scope. It does not retrieve current wait times.

NameTypeReqDescription
park_idstring–Optional canonical Parky park ID to narrow ride search.
querystringyesPark or ride name, such as EPCOT or Hagrid's.

No output schema declared.

No examples provided.

parky_get_best_time ~121

Use this when a visitor asks when to ride something to avoid long waits on a specific day within the next 30 days. Resolve the ride ID first. Returns hourly predicted waits with bounds, the typical wait by hour for that weekday, and the best and worst windows in park-local time; these are estimates, not guarantees.

NameTypeReqDescription
datestring–Park-local date, YYYY-MM-DD, up to 30 days ahead; defaults to today.
ride_idstringyesCanonical Parky ride ID from parky_find_experience.

No output schema declared.

No examples provided.

parky_get_bus_times ~82

Use this when a visitor asks when the next Walt Disney World bus leaves a resort or stop for a park or Disney Springs. Pass a stop name or ID; without one, it lists the stops. Predictions come from Disney's own bus tracking.

NameTypeReqDescription
stopstring–Stop name or ID, such as Art of Animation; omit to list stops.

No output schema declared.

No examples provided.

parky_get_crowd_outlook ~134

Use this when a visitor asks how crowded one supported park may be within the next 30 park-local days. Resolve the park ID first. Returns a forecast and range, not a guarantee or a live wait.

NameTypeReqDescription
datestring–First date in the park's local time zone, YYYY-MM-DD; defaults to today.
daysinteger–Number of consecutive days, 1 to 30; defaults to 1.
park_idstringyesCanonical Parky park ID from parky_find_experience (a park key such as magic-kingdom also works).

No output schema declared.

No examples provided.

parky_get_event_nights ~146

Use this when a visitor asks about separately ticketed event nights at a supported resort, such as Mickey's Not-So-Scary Halloween Party, Disney Jollywood Nights or Halloween Horror Nights: which nights are on sale or sold out, and the lowest price. Covers up to 60 days. Parky cannot sell tickets.

NameTypeReqDescription
fromstring–First night, YYYY-MM-DD; defaults to today.
resortstringyesResort key or shorthand: wdw, dlr, uor or ush.
tostring–Last night, YYYY-MM-DD; defaults to 29 days after from; at most 60 days in all.

No output schema declared.

No examples provided.

parky_get_hours ~151

Use this when a visitor asks about operating hours for one supported park within the next 60 park-local days. Resolve the park ID first. Schedule windows have guest-facing categories and labels; Early Entry is an eligibility-based window, not a separate ticketed event. These are reported schedules, which the operator may change.

NameTypeReqDescription
datestring–First date in the park's local time zone, YYYY-MM-DD; defaults to today.
daysinteger–Number of consecutive days, 1 to 14; defaults to 1.
park_idstringyesCanonical Parky park ID from parky_find_experience (a park key such as magic-kingdom also works).

No output schema declared.

No examples provided.

parky_get_lightning_lane ~153

Use this when a visitor asks what Lightning Lane (or Universal Express) costs at one supported park on a date, or which rides have Lightning Lane return times available now and how soon. Return times exist only for today; prices cover the next 30 park-local days. Parky cannot buy or book Lightning Lane.

NameTypeReqDescription
datestring–Park-local date for prices, YYYY-MM-DD; defaults to today. Return times are only for today.
park_idstringyesCanonical Parky park ID from parky_find_experience (a park key such as magic-kingdom also works).
ride_idstring–Optional canonical ride ID to return one ride's return window.

No output schema declared.

No examples provided.

parky_get_park_availability ~128

Use this when a visitor asks whether a park has reservations or blockout dates for a ticket or pass type on given dates at a supported resort. Returns availability by segment (ticket or pass type) for up to 7 days, from Disney's and Universal's own calendars.

NameTypeReqDescription
datestring–First date, YYYY-MM-DD; defaults to today.
daysinteger–Number of days, 1 to 7; defaults to 3.
resortstringyesResort key or shorthand: wdw, dlr, uor or ush.

No output schema declared.

No examples provided.

parky_get_park_conditions ~97

Use this when a visitor asks about the weather, storms, heat, lightning or weather alerts at one supported park right now, or how many rides are down. Weather is the National Weather Service's latest observation and alerts; it is current conditions, not a forecast.

NameTypeReqDescription
park_idstringyesCanonical Parky park ID from parky_find_experience (a park key such as magic-kingdom also works).

No output schema declared.

No examples provided.

parky_get_ride_facts ~87

Use this when a visitor asks about a ride itself: height requirement, ride length, top speed, biggest drop, ride type, land, or whether it offers Lightning Lane. Resolve the ride ID first. Facts vary by ride; missing facts are omitted rather than guessed.

NameTypeReqDescription
ride_idstringyesCanonical Parky ride ID from parky_find_experience.

No output schema declared.

No examples provided.

parky_get_ride_outages ~160

Use this when a visitor asks whether or when a ride broke down: with ride_id, each outage of that ride over the last 1 to 30 days with start and end times; without ride_id, every outage at the park today including rides down right now. Outages come from Disney's and Universal's own live feeds.

NameTypeReqDescription
daysinteger–Days of one ride's history, 1 to 30; defaults to 7. Ignored without ride_id.
park_idstringyesCanonical Parky park ID from parky_find_experience (a park key such as magic-kingdom also works).
ride_idstring–Optional canonical ride ID for one ride's outage history.

No output schema declared.

No examples provided.

parky_get_ride_reliability ~112

Use this when a visitor asks how often a ride breaks down or which rides at a park are least reliable. Returns 30-day uptime percentage, outages per day, and average and longest outage, least reliable first. Resolve the park ID first.

NameTypeReqDescription
park_idstringyesCanonical Parky park ID from parky_find_experience (a park key such as magic-kingdom also works).
ride_idstring–Optional canonical ride ID to return one ride only.

No output schema declared.

No examples provided.

parky_get_showtimes ~97

Use this when a visitor asks when a show, parade, fireworks or character meet happens at one supported park today or within the next week. Times are usually published for today only.

NameTypeReqDescription
datestring–Park-local date, YYYY-MM-DD; defaults to today.
park_idstringyesCanonical Parky park ID from parky_find_experience (a park key such as magic-kingdom also works).

No output schema declared.

No examples provided.

parky_get_ticket_prices ~118

Use this when a visitor asks what park tickets cost at a supported resort for a start date within the next year (walt-disney-world, disneyland-resort, universal-orlando, universal-studios-hollywood). Returns the prices Disney or Universal showed Parky on its last check. Parky cannot sell or book tickets.

NameTypeReqDescription
datestring–Ticket start date, YYYY-MM-DD; defaults to today.
resortstringyesResort key or shorthand: wdw, dlr, uor or ush.

No output schema declared.

No examples provided.

parky_get_waits ~129

Use this when a visitor asks for current posted ride waits or operating status at one supported park. Resolve the park ID first. Each entry has a type: ride (always listed; "unavailable", not closed, when no live value is reported), experience, show or meet (listed only while reported). This tool does not predict future waits.

NameTypeReqDescription
park_idstringyesCanonical Parky park ID from parky_find_experience (a park key such as magic-kingdom also works).
ride_idstring–Optional canonical ride ID to return one ride only.

No output schema declared.

No examples provided.

Common questions

What is the Parky — Park Planning MCP server?

Parky — Park Planning is an MCP server listed in the public MCP registry as com.parkypass/parky. Find Disney and Universal rides, posted waits, park hours, and crowd forecasts with Parky. This page covers its hosted endpoint (https://mcp.parkypass.com/mcp).

Is the Parky — Park Planning MCP server safe to use?

Parky — Park Planning scores 76 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 Parky — Park Planning MCP server expose?

Parky — Park Planning exposes 15 tools: parky_find_experience, parky_get_waits, parky_get_hours, parky_get_crowd_outlook, parky_get_lightning_lane, and 10 more. Their descriptions and schemas cost roughly 1,806 tokens of context every time the server is loaded.

Does the Parky — Park Planning MCP server require authentication?

No. We connected to Parky — Park Planning without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Parky — Park Planning MCP server still maintained?

Parky — Park Planning is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.