ParkAlert MCP
Related Servers
Alternatives to ParkAlert MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceProvides access to Disney parks data including attractions, dining locations, height requirements, Lightning Lane status, and other park information for Walt Disney World and Disneyland resorts through structured queries and fuzzy search.72-
- AlicenseNot gradedqualityCmaintenanceEnables access to live theme park wait times, schedules, and attraction data from ThemeParks.wiki.6MIT
- FlicenseNot gradedqualityDmaintenanceEnables management of Atlassian Statuspage incidents, components, and subscribers through natural language.-

@pipeworx/statuspageofficial
AlicenseNot gradedqualityCmaintenanceMCP server that answers service status and uptime questions by reading Atlassian Statuspage feeds from hundreds of vendors, with keyless access and tools for checking status, incidents, and vendor listings.2MIT- AlicenseAqualityCmaintenanceProvides Belgian railway travel information via the iRail API, including station search, live departures/arrivals, route planning, and network disturbances.5MIT
- AlicenseNot gradedqualityDmaintenanceEnables users to interact with Washington DC Metro (WMATA) transit system through natural language queries. Provides real-time train arrivals, service alerts, station information, trip planning, and accessibility updates.1,036MIT
TDQS
Scored across 2 tools
The two tools accept the same park/ride arguments and both return status plus wait time, so an agent could reasonably pick either for a wait or status question. However, the descriptions clearly steer status checks to get_ride_status and wait-time questions to get_wait_time, reducing confusion.
Both tools follow the same get_<resource>_<metric> pattern: get_ride_status and get_wait_time. The naming is predictable and mirrors the two core queries perfectly.
Two tools is on the thin side for a general-purpose MCP server, but the scope is intentionally narrow: live Disney ride status and standby wait times. The count feels minimal but not unreasonable for that focused domain.
The core domain is covered: agents can check whether a ride is operating, down, or closed, and get standby wait minutes with status context to interpret Nones. Minor gaps exist, such as no way to list all rides in a park, but the main user intents are served.