_ registry / mcp http-sse · checked 1h ago

snowdata-content

https://mcp.snowdata.ai

Registry code: 5f288bddf94ad6f0

api record

Live verified resort snow, forecasts, powder search, trip planning & grounded Q&A for 430+ resorts.

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

endpoint
https://mcp.snowdata.ai/api/mcp
protocol
http-sse ·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 snowdata-content live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is snowdata-content free to use?
Yes — the hub reached it with no key and no payment.
What tools does snowdata-content have?
10 tools: snowdata_search_knowledge, snowdata_live_data_mcp_pointer, snowdata_get_page, snowdata_get_intelligence_overview, snowdata_get_company_profile, snowdata_get_resort_onboarding, snowdata_get_llms_context, snowdata_get_faqs, ….
Is snowdata-content 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
live
uptime, 30 days
100%

90 days 99.3%· all time 99.3%

latency
628ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 680 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • get company information about a snow data provider
  • search site faqs and pages
  • learn how resorts submit snow data
takes → gives
text → text
tools
10 reads
note
documentation mirror
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 10 tools
7 open 3 never probed 7 of 10 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.

  • snowdata_get_intelligence_overview reads open 4h ago

    SnowSure intelligence cards on Snowdata homepage and API contract.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • snowdata_get_company_profile reads open 12h ago

    Company facts, contacts, linked properties, pricing, network stats.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • snowdata_get_resort_onboarding reads open 21h ago

    How resorts submit snow data and where Snowdata distributes it. Intake URL and channels.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • snowdata_get_llms_context reads open 4h ago

    Return llms.txt or extended llms-full.txt for LLM crawlers.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "extended": {
          "type": "boolean",
          "description": "If true, return llms-full.txt"
        }
      },
      "additionalProperties": false
    }
    arguments 11 lines
  • snowdata_get_faqs reads open 4h ago

    Frequently asked questions by topic.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "topic": {
          "enum": [
            "general",
            "resorts",
            "developers",
            "ai",
            "intelligence",
            "mcp"
          ],
          "type": "string",
          "description": "general | resorts | developers | ai | intelligence | mcp"
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • snowdata_list_pages reads open 12h ago

    List all Snowdata corporate site pages with summaries and URLs.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • snowdata_get_developer_guide reads open 12h ago

    MCP install for live snow data, tool list, example queries, REST API and spec links.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • snowdata_search_knowledge reads unknown 21h ago

    Search Snowdata site knowledge (pages, FAQs, company facts).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "Search terms"
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • snowdata_live_data_mcp_pointer reads unknown never probed

    Pointer to mcp.snowdata.ai for LIVE resort snow — use this when users ask about current conditions, not this content server.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • snowdata_get_page reads unknown 21h ago

    Get full structured content for a Snowdata site path (e.g. /for-resorts).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "path"
      ],
      "properties": {
        "path": {
          "type": "string",
          "description": "Site path starting with /"
        }
      },
      "additionalProperties": false
    }
    arguments 14 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 5f288bddf94ad6f0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5f288bddf94ad6f0/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/5f288bddf94ad6f0/badge.svg)](https://brick.blue/agent/5f288bddf94ad6f0?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
100%

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.