_ registry / mcp streamable-http

status-live-nationalparks

https://status.live

Registry code: f29b2a27ffbf6630

api record

Live ride status and wait times at 140 theme parks, with local time and weather.

from a public catalogue that lists it, not from the operator

endpoint
https://status.live/nationalparks/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is status-live-nationalparks live?
Not measured yet: the hub has not completed a check of this server.
Is status-live-nationalparks free to use?
Not measured yet.
What tools does status-live-nationalparks have?
3 tools: nationalparks_search_parks, nationalparks_get_park_status, nationalparks_find_campgrounds.
Is status-live-nationalparks safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
unknown
uptime
—
latency
—

last good check

priced tools
0

of 3 tools

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • nationalparks_search_parks unknown never probed

    Find the national parks this server covers: US National Park Service units (national parks, plus monuments, seashores and recreation areas with campgrounds) and Canada's national parks (Parks Canada). Search by name, park id (e.g. "yose", "banff"), US state, Canadian province, or "canada". Returns ids for nationalparks_get_park_status.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 25,
          "maximum": 200,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "default": "",
          "description": "Name, park code, state code or state name, case-insensitive"
        }
      }
    }
    arguments 17 lines
  • nationalparks_get_park_status unknown never probed

    Right now at one park. For US parks: the National Park Service's current alerts (closures, dangers, fire bans, water outages), National Weather Service warnings, air quality (US AQI), active wildfires within 50 km, road events inside the park and access-road conditions where available, which campgrounds and visitor centers are open today by their published schedules, webcams, sunrise/sunset and moon phase, and a model weather forecast. For Canadian parks: Parks Canada bulletins, Environment Canada weather alerts, satellite fire hotspots, air quality, road conditions where available, and the forecast. Live parts come with an as-of time. Accepts a park id (e.g. "yose", "banff") or name.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "park"
      ],
      "properties": {
        "park": {
          "type": "string",
          "description": "Park code (e.g. \"yose\") or name (e.g. \"Yosemite\")"
        },
        "include_campgrounds": {
          "type": "boolean",
          "default": true,
          "description": "List each campground; set false for just the count"
        }
      }
    }
    arguments 18 lines
  • nationalparks_find_campgrounds unknown never probed

    National Park Service campgrounds nearest a point, with whether each is open today by its published schedule, site counts and reservation links. Schedules only: check nationalparks_get_park_status for current alerts.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "latitude",
        "longitude"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "max_km": {
          "type": "number",
          "default": 100,
          "maximum": 500,
          "exclusiveMinimum": 0
        },
        "latitude": {
          "type": "number",
          "maximum": 90,
          "minimum": -90
        },
        "longitude": {
          "type": "number",
          "maximum": 180,
          "minimum": -180
        },
        "open_today_only": {
          "type": "boolean",
          "default": true
        }
      }
    }
    arguments 36 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f29b2a27ffbf6630.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f29b2a27ffbf6630/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f29b2a27ffbf6630/badge.svg)](https://brick.blue/agent/f29b2a27ffbf6630?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.