status.live theme parks is an MCP server with 2 tools an agent can call, among them themeparks_get_park_status, themeparks_search_parks. It answers at https://status.live/themeparks/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 6 October 2026; the last check, on 22 November 2026, succeeded.
Live ride status and wait times at 140 theme parks, with local time and weather.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
themeparks_get_park_status | Live ride status for one theme park: every ride open or closed with its posted wait time, grouped by area, plus the park's local time and a model weather forecast. Pass `ride` to answer about specific rides ("Space Mountain"). Data comes fr Inputs: park, ride, include_rides |
themeparks_search_parks | Find the theme parks this server covers, by name, id, country (e.g. "Japan") or operator (e.g. "Six Flags", "Disney"). Returns park ids for themeparks_get_park_status. Leave query empty to list everything. Inputs: query, limit |
Every block below points at https://status.live/themeparks/mcp. Pick your client and copy.
claude mcp add --transport http status-live-theme-parks https://status.live/themeparks/mcp
{
"mcpServers": {
"status-live-theme-parks": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://status.live/themeparks/mcp"]
}
}
}{
"mcpServers": {
"status-live-theme-parks": {
"url": "https://status.live/themeparks/mcp"
}
}
}{
"servers": {
"status-live-theme-parks": {
"type": "http",
"url": "https://status.live/themeparks/mcp"
}
}
}{
"context_servers": {
"status-live-theme-parks": {
"url": "https://status.live/themeparks/mcp"
}
}
}{
"mcpServers": {
"status-live-theme-parks": {
"serverUrl": "https://status.live/themeparks/mcp"
}
}
}{
"mcpServers": {
"status-live-theme-parks": {
"url": "https://status.live/themeparks/mcp"
}
}
}name: status.live theme parks
version: 0.0.1
schema: v1
mcpServers:
- name: status.live theme parks
type: streamable-http
url: https://status.live/themeparks/mcp{
"mcpServers": {
"status-live-theme-parks": {
"httpUrl": "https://status.live/themeparks/mcp"
}
}
}{
"mcpServers": {
"status-live-theme-parks": {
"type": "http",
"url": "https://status.live/themeparks/mcp"
}
}
}{
"mcpServers": {
"status-live-theme-parks": {
"url": "https://status.live/themeparks/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fstatus.live%2Fthemeparks%2Fmcp&type=streamable_http&id=status-live-theme-parks&name=status.live%20theme%20parks
It answered our last check on 22 November 2026 in 103 ms. Over 4 checks since 6 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by status.live and served from status.live, the vendor's own domain: https://status.live/themeparks/mcp.
2, as returned by the server's own tools/list on 22 November 2026: themeparks_get_park_status, themeparks_search_parks.
It answered our last check on 22 November 2026 in 103 ms. Over 4 checks since 6 October 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://status.live/themeparks/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: live.status. Endpoint host: status.live. ARD identifier: urn:air:live.status:mcp:themeparks.
First indexed 6 October 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.