Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ClimbCast

REMOTE · CLIMBCAST.IO · SCANNED OCT 4

Read-only conditions and forecast accuracy for covered objectives in WA, OR, and BC. No account.

Available components

+3 this week 77 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 333 tokens (~83/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the ClimbCast MCP server?

ClimbCast is a hosted endpoint at https://climbcast.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · climbcast.io

# add to Claude Code
claude mcp add --transport http io-climbcast-climbcast 'https://climbcast.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-climbcast-climbcast": {
      "url": "https://climbcast.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-climbcast-climbcast": {
      "type": "http",
      "url": "https://climbcast.io/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.io-climbcast-climbcast]
url = "https://climbcast.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-climbcast-climbcast": {
      "type": "remote",
      "url": "https://climbcast.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-climbcast-climbcast --url 'https://climbcast.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-climbcast-climbcast:
    url: "https://climbcast.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-climbcast-climbcast": {
      "Transport": "http",
      "Url": "https://climbcast.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-climbcast-climbcast -t streamable-http -u 'https://climbcast.io/mcp'
// mcp.json
{
  "mcpServers": {
    "io-climbcast-climbcast": {
      "type": "http",
      "url": "https://climbcast.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Oct 26 +1
    • Tool “get_forecast_accuracy” now declares an output schema ▲ functional
    • Tool “get_objective_conditions” now declares an output schema ▲ functional
    • Tool “get_route_conditions” now declares an output schema ▲ functional
    • Tool “search_objectives” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
    • Schema quality: good → excellent functional
    • “search_objectives” reworded the description of “region” cosmetic
  • 2 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 74

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Oct 2026 · Probed https://climbcast.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=climbcast.io CN=YE1,O=Let's Encrypt,C=US 8 Sept 2026 7 Dec 2026 ECDSA 256 ECDSA-SHA384 548d05e3f84f46f038b8278e6375a138ed6
SANs: *.climbcast.io, climbcast.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of climbcast.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
climbcast.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy script-src 'self' https://www.googletagmanager.com https://www.google-analytics.com https://*.clerk.accounts.dev https://*.clerk.com https://clerk.climbcast.io https://challenges.cloudflare.com https://js.stripe.com https://us-assets.i.posthog.com 'nonce-6E2h5xe67CZqPu6RlTUeNA=='; default-src 'self'; script-src-attr 'none'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' data: https://fonts.gstatic.com; img-src 'self' data: https://*.tile.opentopomap.org https://unpkg.com https://www.google-analytics.com https://www.googletagmanager.com https://clerk.climbcast.io https://img.clerk.com; connect-src 'self' https://www.google-analytics.com https://www.googletagmanager.com https://nominatim.openstreetmap.org https://*.clerk.accounts.dev https://*.clerk.com https://clerk.climbcast.io https://challenges.cloudflare.com https://api.revenuecat.com https://api.rc-backup.com https://e.revenue.cat https://js.stripe.com https://us-assets.i.posthog.com https://*.sentry.io https://sentry.io; w
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), camera=(), microphone=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://climbcast.io/mcp Verified 200
http (plaintext) http://climbcast.io/mcp HTTPS enforced 301 https://climbcast.io/mcp
MCP tools · 4 exposed · ~333 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_forecast_accuracy ~60

Returns stored public regional forecast accuracy, including observed-station or model-proxy truth lineage, data sufficiency, and eligibility. Informational only.

NameTypeReqDescription
region_idstringyesPublic accuracy region identifier, for example pnw-olympics.

Structured output declared, but exposes no named fields.

No examples provided.

get_objective_conditions ~68

Returns public conditions for a covered objective: summit weather, source provenance, and timestamps, in JSON or markdown. Informational only.

NameTypeReqDescription
formatstring–Text representation; structured data is included in either format.
slugstringyesPublic objective slug returned by search_objectives.

Structured output declared, but exposes no named fields.

No examples provided.

get_route_conditions ~83

Returns seven days of public route conditions, anchored to the route high point and aspect, with source provenance and timestamps. Informational only.

NameTypeReqDescription
formatstring–Text representation; structured data is included in either format.
route_idstringyesRoute identifier returned by search_objectives.
slugstringyesPublic objective slug returned by search_objectives.

Structured output declared, but exposes no named fields.

No examples provided.

search_objectives ~122

Searches the public coverage catalog by name or alias, with optional region and activity filters. Coverage follows the current public scope; region filters include WA, OR, and BC. Informational only.

NameTypeReqDescription
activitystring–Optional visible activity filter.
limitinteger–Maximum number of matching objectives.
querystringyesObjective name or alias; matching ignores case and accents.
regionstring–Optional state or province code or name: WA, Washington, OR, Oregon, BC, British Columbia, or B.C. Matching ignores case.

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the ClimbCast MCP server?

ClimbCast is an MCP server listed in the public MCP registry as io.climbcast/climbcast. Read-only conditions and forecast accuracy for covered objectives in WA, OR, and BC. No account. This page covers its hosted endpoint (https://climbcast.io/mcp).

Is the ClimbCast MCP server safe to use?

ClimbCast scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ClimbCast MCP server expose?

ClimbCast exposes 4 tools: get_forecast_accuracy, get_objective_conditions, get_route_conditions, search_objectives. Their descriptions and schemas cost roughly 333 tokens of context every time the server is loaded.

Does the ClimbCast MCP server require authentication?

No. We connected to ClimbCast without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ClimbCast MCP server still maintained?

ClimbCast is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.