
Status MCP server
Which MCP servers are Status's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-26
- Registry namelive.status/campgroundsverified in the MCP registry
The registry name sits under status.live. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-26
- Tools3
- Server calls itselfstatus-live-campgrounds
- Server version0.3.0
- Protocol version2025-06-18
On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 60 ms.
- Its tools do none of the product's use cases we checked: check whether a ski resort is open today; view surf buoy, tide and swell readings before going out.
- Checked on 1 of the 7 days it takes to judge reliability.
Once connected
- Parameters are untyped or undescribed in 2 of 3 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
- What an agent can do with it0 of 2 use cases
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer679 ms
- Space in an agent's context≈ 755 tokensthe definitions of all its tools (3), which an agent carries on every turn
- Tool definitionsB · 89 of 100
- Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 2 of 3
What an agent can do with it
- cannot · check whether a ski resort is open today
- not sure · look up national park closures and alerts
- cannot · view surf buoy, tide and swell readings before going out
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
campgrounds_searchFind National Park Service, Forest Service and California State Parks campgrounds by name, id, park or national forest (e.g. "Yosemite", "Shasta-Trinity"), or state ("CO", "Colorado"), with whether each is open today and its booking link…
campgrounds_get_statusOne campground: whether it is open today, the season, how to book it (Recreation.gov or the concessioner, or first come first served), fees, rules, its official page, and a model weather forecast. Accepts an id (e.g. "upper-pines") or a…
campgrounds_find_nearNational Park Service, Forest Service and California State Parks campgrounds nearest a latitude/longitude, with distance, whether each is open today and its booking link. NPS campgrounds follow the park's published schedule; Forest…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"campgrounds": {
"type": "http",
"url": "https://status.live/campgrounds/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http status https://status.live/campgrounds/mcpclaude.ai, ChatGPT and other clients: add https://status.live/campgrounds/mcp as a custom connector in the settings.
- live.status/nationalparksanswers, 3 toolsverified in the MCP registry
- live.status/skianswers, 7 toolsverified in the MCP registry
- live.status/status-livenot asked yetverified in the MCP registry
- live.status/surfnot asked yetverified in the MCP registry
- live.status/themeparksnot asked yetverified in the MCP registry
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.