Provider hosted
No sign in
Tools: 55

Canyon Beta

Canyon Beta

Route beta plus a live safety stack for 2,709 canyons across 26 US states — NWS weather and alerts, flash-flood-aware USGS flow, and the hazards upstream of your drop. The resource canyoneers can plan their day around.

https://canyonbeta.com/

Use in your AI tool

Use the tools from this page

Opens ChatGPT on the web or desktop and asks it to use the WebMCP tools available here.

Connect the MCP server

Connect straight to this server’s public endpoint.

Remote MCP URL
https://api.canyonbeta.com/mcp

Use on MCPBundles

We add this server to your workspace, then open Studio — saved access, one connection to many servers, with a history of what ran.

Last probed Sep 14, 2026 · api.canyonbeta.com

55tools discovered

Tools discovered (55)

Showing 25 of 55 from the live probe.

  • Get Server Info

    Describe this server, its limits, common codes, and supported collections.

  • Get Cache Info

    Show whether local caching is enabled, its location, size, and TTL policy.

  • Get Sun Times

    Calculate local and UTC solar events using an IANA timezone. When ``tz`` is omitted, the timezone is resolved locally from the point. ``date`` is an ISO date and defaults to today in that timezone.

  • Get Moon Times

    Calculate local and UTC moonrise/moonset plus phase and illumination. Events are scoped to the local calendar date, so moonset can precede moonrise, and either can be null when it does not occur that date (``always_up``/``never_up`` cover the no-crossing polar cases). Geometry against a flat 0-degree horizon — no terrain, weather, or cloud effects. When ``tz`` is omitted, the timezone is resolved locally from the point. ``date`` is an ISO date and defaults to today i

  • Get Sky Track

    Sample sun and moon azimuth/elevation across one local day. One record per ``interval_minutes`` (5..120) from local 00:00 through 24:00: azimuth in degrees from north, elevation in degrees against a flat 0-degree horizon (negative when below; sun refracted, moon not — no terrain or weather effects). The date's moon phase and illumination summary is in metadata. When ``tz`` is omitted, the timezone is resolved locally from the point. ``date`` is an ISO date and defaults

  • Get Active Alerts

    Get active NWS watches, warnings, and advisories for a point. Check this first for flood and severe-weather safety questions. An empty successful result explicitly means NWS reports no active alerts there.

  • Get Point Forecast

    Get the NWS multi-period forecast for a latitude and longitude.

  • Get Hourly Forecast

    Get 1-168 hours of NWS forecast data with hourly precipitation odds.

  • Get Forecast Discussion

    Get the latest raw NWS Area Forecast Discussion for a three-letter WFO.

  • Get Wfo For Point

    Resolve a point to its NWS office, radar station, grid, and weather zones.

  • Get Watershed For Point

    Get the HUC8 watershed containing a point (USGS WBD). Decimal degrees, WGS84. Returns the 8-digit hydrologic unit code and watershed name; a point outside every HUC8 polygon returns an empty success with ``metadata.no_watershed``. Boundaries essentially never change, so responses cache for 30 days.

  • Get Elevation For Point

    Get the ground elevation at a point (USGS EPQS / 3DEP). Decimal degrees, WGS84. Returns feet (``elevation_ft``, the source value) and metres (``elevation_m``, derived); a point off the 3DEP raster returns an empty success with ``metadata.no_elevation``. Elevation is essentially static, so responses cache for 30 days.

  • Get Flowline For Point

    Get the NHD upstream-main flowline through a point (USGS NLDI). Decimal degrees, WGS84. Returns a public-domain route-line proxy — the drainage centerline through the point, navigated upstream-main up to ``distance_km`` (1-25, default 5) — as ``LineString``/``MultiLineString`` geometry with the source ``comid``. A point off the NHD network returns an empty success with ``metadata.no_flowline``. A centerline approximates, and is not, the precise technical line. Cached 30

  • Get Upstream Fires

    List wildfires intersecting the drainage basin upstream of a point. Burn scars amplify flash-flood and debris-flow response for years, and the rain that floods a canyon falls in its upstream basin. Resolves the NLDI basin for the point, then intersects NIFC/WFIGS fire perimeters (both federal public domain) server-side. A perimeter intersecting the basin does NOT say how much of it burned — the result says so; treat fire history as a reason for extra attention, never a c

  • Get Basin Qpf

    Forecast precipitation over the drainage basin upstream of a point. Flash floods come from rain over the upstream basin, not rain at the canyon. Intersects the NLDI basin with WPC QPF contour polygons (federal PD): 72-hour Day 1-3 headline plus per-day values, all in inches. Values mean "parts of the basin are forecast at least this much" — never a basin average — and synoptic contours cannot resolve single monsoon cells. Radar and active NWS alerts always outrank this.

  • Get Basin Qpe

    Observed precipitation over the drainage basin upstream of a point. Flash floods come from rain that already fell over the upstream basin — often under clear skies at the canyon. Zonal statistics over the NLDI basin against MRMS QPE mosaics (federal PD) for 1-, 24-, and 72-hour windows, in inches (native grid is mm, converted). The basin max is the headline: "some 1 km cell received about this much" — never a basin average. Radar QPE underestimates in beam-blocked ca

  • Get Basin Precip Normals

    Antecedent precipitation vs normal for the basin upstream of a point. How primed the basin is: NWS RFC gauge-corrected precip analysis (federal PD) sampled for 14- and 30-day windows — observed inches, departure from normal, percent of normal. A ~4 km daily product sampled at the query point and basin centroid (wetter sample reported), not full zonal statistics. If no basin resolves, the query point alone is sampled and ``metadata.no_basin`` is true. Context for pace

  • Get Basin Excessive Rain Outlook

    WPC Excessive Rainfall Outlook categories over the upstream basin. The only national outlook defined against flash-flood guidance: Day 1-5 categories (Marginal/Slight/Moderate/High) where they intersect the NLDI basin (federal PD). A day with no polygon is an honest 'no elevated risk outlook' (``outlook: null``), not 'no risk'; categories are regional probabilities, never a canyon-scale forecast. Active NWS alerts and radar always outrank this.

  • Get Gridpoint Conditions

    Raw NWS gridpoint elements and P-VTEC hazards for a point's cell. The grid behind the forecast products: relative humidity, sky cover, temperature, wind speed, thunder probability, snow level and snowfall amount, each as the value in force now with its unit in the field name (the endpoint answers metric; these are converted). Plus the ``hazards`` element decoded from P-VTEC into named events, with unrecognised codes passed through rather than guessed. NOT a replacem

  • Get Soil Moisture

    Near-surface soil moisture at a point and over its upstream basin. How much room the ground has left, as percent of saturation, from the NWS National Water Model land analysis (federal PD). A basin near saturation sheds almost everything that falls; a dry one absorbs a first burst. Sampled at the query point and the basin centroid — representative points, not zonal statistics — with the wetter reported as ``metadata.basin_saturation_percent`` and the analysis time as

  • Get Rock Drying Conditions

    When rain last fell at a cliff, and how hard the air is drying it. Two things a climber cannot judge from the parking lot. MRMS radar QPE sampled at the point gives cumulative rainfall over 1/3/6/24/72 hours; because the windows are cumulative, the first one carrying measurable rain brackets when that rain fell (3h dry + 6h wet means it rained 3-6 hours ago). The NWS gridpoint elements then give the air doing the drying — temperature, relative humidity, wind, sky cov

  • Get Local Storm Reports

    Storm reports people filed near a point in the trailing window. The only OBSERVATION this server carries — every other hazard signal here is a forecast or a model. NWS Local Storm Reports (federal PD) within ``radius_miles`` over the last 24/48/72 hours, nearest first, defaulting to the flood family (Flash Flood, Flood, Debris Flow, Landslide); pass ``flood_only=False`` for every logged event type. Read the result as 'reported' or 'none reported', NEVER as 'clear':

  • Get Basin Ffg

    Flash-flood guidance for the basin upstream of a point. How much rain over 1/3/6 hours begins flash flooding here, per the NWS RFC gridded-FFG mosaic (federal PD), in inches (native mm, converted — verified against hydrologic control points). Sampled at the query point and basin centroid with the LOWER guidance reported (lower floods easier). Guidance cannot see burn scars or slickrock — treat it as generous in canyon terrain. 12/24 h durations are retired upstream a

  • Get Reach Flow

    National Water Model short-range flow for the reach at a point. Most canyon reaches have no gauge; the NWM models every NHD reach. Returns the 18-hour short-range forecast series (hourly, cfs) for the reach's COMID plus ``metadata.max_flow_cfs``. Modeled water, not a gauge: small ephemeral reaches often read 0 through real low flow, and the model cannot see a storm radar has not. The upstream call is slow (~40 s) on a cold cache and cached for an hour after. A point

  • Get Air Quality

    Current EPA AirNow AQI observations near a point. Wildfire smoke decides approach days: AQI per parameter (PM2.5, ozone, PM10) with EPA's own category names for the reporting area nearest the point (50 mi search). Reporting areas are town-scale and may sit far from a canyon — approach-day context, never a health determination. Requires ``AIRNOW_API_KEY`` (free, docs.airnowapi.org). An empty result sets ``metadata.no_reporting_area`` — absence of a reporting area is

Get your MCP into directories

A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.

Directory coverage for brands

Frequently Asked Questions

What is the Canyon Beta MCP server?

Route beta plus a live safety stack for 2,709 canyons across 26 US states — NWS weather and alerts, flash-flood-aware USGS flow, and the hazards upstream of your drop. The resource canyoneers can plan their day around.

How do I connect Canyon Beta to my AI agent?

Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.

How many tools does Canyon Beta provide?

MCPBundles probed 55 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.

What authentication does Canyon Beta require?

No provider sign-in was required during MCPBundles' probe. Your client may still need MCPBundles credentials depending on how you connect.

Maintain this listing

Operate Canyon Beta? Verify ownership to take over this directory entry.

Operate Canyon Beta?

This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.

Claim this listing