_ registry / mcp http-sse · checked 15m ago

met-weather

https://met-mcp.met-mcp-worker.workers.dev

Registry code: d80889b6b70c0119

api record

Weather forecasts from MET Norway (Yr): geocoding plus hourly forecasts worldwide.

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

endpoint
https://met-mcp.met-mcp-worker.workers.dev/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 met-weather live?
Yes — it answered the hub's last check (checked 15m ago). It answered 99% of checks over the last 30 days.
Is met-weather free to use?
Yes — the hub reached it with no key and no payment.
What tools does met-weather have?
8 tools: geocode_location, find_weather_stations, get_ocean_forecast, get_historical_weather, get_nowcast, get_sun_events, get_forecast, get_weather_alerts.
Is met-weather 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
99.3%

90 days 99.7%· all time 99.7%

latency
222ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 605 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • unknown → live
_ what it is for
topic
weather & environment forecast
used for
  • get hourly weather forecast
  • geocode a place name
  • get historical station weather
  • get ocean wave forecast
  • get weather alerts in norway
takes → gives
text → data
tools
8 reads
_ 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 8 tools
1 open 7 never probed 1 of 8 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.

  • get_weather_alerts reads open 9h ago

    Official danger warnings (wind, flood, ice, forest fire...) from MET Norway. Covers Norway and its waters. Omit coordinates to get all current alerts. Alert text is in Norwegian.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude in decimal degrees"
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude in decimal degrees"
    }
  }
}
    arguments 18 lines
  • geocode_location reads unknown never probed

    Find latitude and longitude for a place name. Use the coordinates with the other tools.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1,
      "description": "Place name, e.g. 'Bergen' or 'Oslo, Norway'"
    },
    "count": {
      "type": "integer",
      "default": 5,
      "maximum": 10,
      "minimum": 1,
      "description": "Maximum number of matches to return"
    }
  }
}
    arguments 21 lines
  • find_weather_stations reads unknown 17h ago

    Find the nearest official weather stations (Frost). Use the station id (e.g. SN50540) with get_historical_weather.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "latitude",
    "longitude"
  ],
  "properties": {
    "count": {
      "type": "integer",
      "default": 5,
      "maximum": 20,
      "minimum": 1,
      "description": "Maximum number of stations to return"
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude in decimal degrees"
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude in decimal degrees"
    }
  }
}
    arguments 29 lines
  • get_ocean_forecast reads unknown 17h ago

    Wave height, wave direction, and sea temperature. Covers the Norwegian coast and nearby seas.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "latitude",
    "longitude"
  ],
  "properties": {
    "hours": {
      "type": "integer",
      "default": 24,
      "maximum": 48,
      "minimum": 1,
      "description": "How many hours ahead to include"
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude in decimal degrees"
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude in decimal degrees"
    }
  }
}
    arguments 29 lines
  • get_historical_weather reads unknown 9h ago

    Daily historical observations from a weather station (Frost archive, some stations go back over 100 years). Find station ids with find_weather_stations.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "station_id",
    "from",
    "to"
  ],
  "properties": {
    "to": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "End date (exclusive), YYYY-MM-DD"
    },
    "from": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Start date, YYYY-MM-DD"
    },
    "elements": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "default": [
        "mean(air_temperature P1D)",
        "sum(precipitation_amount P1D)",
        "max(wind_speed P1D)"
      ],
      "description": "Frost element ids. Defaults: daily mean temperature, precipitation sum, max wind."
    },
    "station_id": {
      "type": "string",
      "pattern": "^SN\\d+$",
      "description": "Station id from find_weather_stations, e.g. SN50540"
    }
  }
}
    arguments 38 lines
  • get_nowcast reads unknown 17h ago

    Minute-by-minute precipitation for the next 2 hours, radar-based. Nordic region only. Answers 'do I need an umbrella right now?'

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "latitude",
    "longitude"
  ],
  "properties": {
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude in decimal degrees"
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude in decimal degrees"
    }
  }
}
    arguments 22 lines
  • get_sun_events reads unknown 14h ago

    Sunrise, sunset, and solar noon for a coordinate and date. Works worldwide.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "latitude",
    "longitude",
    "date"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Date as YYYY-MM-DD"
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude in decimal degrees"
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude in decimal degrees"
    },
    "utc_offset": {
      "type": "string",
      "default": "+00:00",
      "pattern": "^[+-]\\d{2}:\\d{2}$",
      "description": "UTC offset for the returned times, e.g. '+02:00' for Norwegian summer time"
    }
  }
}
    arguments 34 lines
  • get_forecast reads unknown 9h ago

    Get an hourly weather forecast from MET Norway (Yr) for a coordinate. Works worldwide, best coverage in the Nordics.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "latitude",
    "longitude"
  ],
  "properties": {
    "hours": {
      "type": "integer",
      "default": 24,
      "maximum": 48,
      "minimum": 1,
      "description": "How many hours ahead to include"
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude in decimal degrees"
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude in decimal degrees"
    }
  }
}
    arguments 29 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 d80889b6b70c0119.

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