_ registry / mcp streamable-http · checked 2h ago

Tomorrow.io Weather

https://api.tomorrow.io

Registry code: 9ddbcd08dc7fc198

api record
endpoint
https://api.tomorrow.io/v4/weather-intelligence/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 Tomorrow.io Weather live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is Tomorrow.io Weather free to use?
Yes — the hub reached it with no key and no payment.
What tools does Tomorrow.io Weather have?
9 tools: tio_mcp_apps_show_aqi_6, tio_mcp_apps_show_upcoming, tio_mcp_apps_show_summary, tio_mcp_apps_show_current_6, tio_mcp_apps_show_aqi_mini, tio_mcp_apps_show_aqi_pollen, tio_mcp_apps_show_aqi_pollutant, tio_mcp_apps_show_fire, ….
Is Tomorrow.io 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
100%

90 days 100%· all time 100%

latency
248ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 9 tools
1 open 8 never probed 1 of 9 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.

  • tio_mcp_apps_list_widgets open 2h ago

    List the available weather and air quality views that can be shown. USE when the user asks what types of weather information are available, or wants to know what views/widgets they can explore. For actual weather data, use the other tools directly: - show_upcoming / show_summary — weather forecast - show_aqi_mini — air quality - show_aqi_pollen — pollen levels - show_fire — fire risk

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "category": {
          "enum": [
            "air-quality",
            "weather",
            "fire"
          ],
          "type": "string",
          "description": "Filter by category: \"air-quality\", \"weather\", or \"fire\""
        },
        "response_format": {
          "enum": [
            "markdown",
            "json"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Response format: \"markdown\" for human-readable, \"json\" for structured data"
        },
        "multiLocationOnly": {
          "type": "boolean",
          "description": "If true, return only widgets that support multiple locations"
        }
      },
      "additionalProperties": false
    }
    arguments 29 lines
  • tio_mcp_apps_show_aqi_6 unknown 2h ago

    Compare air quality across 2-6 locations side by side. USE when the user wants to compare air quality in multiple cities.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "locations"
      ],
      "properties": {
        "units": {
          "enum": [
            "metric",
            "imperial"
          ],
          "type": "string",
          "default": "metric",
          "description": "Unit system: \"metric\" or \"imperial\""
        },
        "locations": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "latitude",
              "longitude"
            ],
            "properties": {
              "latitude": {
                "type": "number",
                "maximum": 90,
                "minimum": -90,
                "description": "Latitude"
              },
              "longitude": {
                "type": "number",
                "maximum": 180,
                "minimum": -180,
                "description": "Longitude"
              }
            },
            "additionalProperties": false
          },
          "maxItems": 6,
          "minItems": 2,
          "description": "Array of 2-6 locations with lat/lng coordinates"
        }
      },
      "additionalProperties": false
    }
    arguments 47 lines
  • tio_mcp_apps_show_upcoming unknown never probed

    Show the weather forecast for a location — current conditions plus the next 6 days. USE when the user asks about the weather, forecast, temperature, or conditions for a specific place. This is the default weather tool — use it for any general weather question.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "latitude",
        "longitude"
      ],
      "properties": {
        "units": {
          "enum": [
            "metric",
            "imperial"
          ],
          "type": "string",
          "default": "metric",
          "description": "Unit system: \"metric\" or \"imperial\""
        },
        "latitude": {
          "type": "number",
          "maximum": 90,
          "minimum": -90,
          "description": "Latitude of the location"
        },
        "longitude": {
          "type": "number",
          "maximum": 180,
          "minimum": -180,
          "description": "Longitude of the location"
        }
      },
      "additionalProperties": false
    }
    arguments 32 lines
  • tio_mcp_apps_show_summary unknown never probed

    Show a concise weather summary for a location — current conditions, a natural-language forecast for the next 24 hours, and how today compares to yesterday. USE when the user wants a quick overview or summary of the weather, or asks "what's it like outside?"

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "latitude",
        "longitude"
      ],
      "properties": {
        "units": {
          "enum": [
            "metric",
            "imperial"
          ],
          "type": "string",
          "default": "metric",
          "description": "Unit system: \"metric\" or \"imperial\""
        },
        "latitude": {
          "type": "number",
          "maximum": 90,
          "minimum": -90,
          "description": "Latitude of the location"
        },
        "longitude": {
          "type": "number",
          "maximum": 180,
          "minimum": -180,
          "description": "Longitude of the location"
        }
      },
      "additionalProperties": false
    }
    arguments 32 lines
  • tio_mcp_apps_show_current_6 unknown never probed

    Compare current weather across 2-6 locations side by side. USE when the user wants to compare weather in multiple cities, or asks about conditions in several places at once.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "locations"
      ],
      "properties": {
        "units": {
          "enum": [
            "metric",
            "imperial"
          ],
          "type": "string",
          "default": "metric",
          "description": "Unit system: \"metric\" or \"imperial\""
        },
        "locations": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "latitude",
              "longitude"
            ],
            "properties": {
              "latitude": {
                "type": "number",
                "maximum": 90,
                "minimum": -90,
                "description": "Latitude"
              },
              "longitude": {
                "type": "number",
                "maximum": 180,
                "minimum": -180,
                "description": "Longitude"
              }
            },
            "additionalProperties": false
          },
          "maxItems": 6,
          "minItems": 2,
          "description": "Array of 2-6 locations with lat/lng coordinates"
        }
      },
      "additionalProperties": false
    }
    arguments 47 lines
  • tio_mcp_apps_show_aqi_mini unknown 2h ago

    Show the current air quality index (AQI) for a location, alongside weather conditions. USE when the user asks about air quality, pollution levels, or whether it's safe to exercise outdoors.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "latitude",
        "longitude"
      ],
      "properties": {
        "units": {
          "enum": [
            "metric",
            "imperial"
          ],
          "type": "string",
          "default": "metric",
          "description": "Unit system: \"metric\" or \"imperial\""
        },
        "latitude": {
          "type": "number",
          "maximum": 90,
          "minimum": -90,
          "description": "Latitude of the location"
        },
        "longitude": {
          "type": "number",
          "maximum": 180,
          "minimum": -180,
          "description": "Longitude of the location"
        }
      },
      "additionalProperties": false
    }
    arguments 32 lines
  • tio_mcp_apps_show_aqi_pollen unknown never probed

    Show pollen levels (tree, grass, and weed) and air quality for a location. USE when the user asks about pollen, allergies, hay fever, or pollen forecasts.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "latitude",
        "longitude"
      ],
      "properties": {
        "units": {
          "enum": [
            "metric",
            "imperial"
          ],
          "type": "string",
          "default": "metric",
          "description": "Unit system: \"metric\" or \"imperial\""
        },
        "latitude": {
          "type": "number",
          "maximum": 90,
          "minimum": -90,
          "description": "Latitude of the location"
        },
        "longitude": {
          "type": "number",
          "maximum": 180,
          "minimum": -180,
          "description": "Longitude of the location"
        }
      },
      "additionalProperties": false
    }
    arguments 32 lines
  • tio_mcp_apps_show_aqi_pollutant unknown never probed

    Show detailed air pollutant concentrations (PM2.5, PM10, O3, NO2, CO, SO2) for a location. USE when the user asks about specific pollutants, particle matter, or detailed air quality data.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "latitude",
        "longitude"
      ],
      "properties": {
        "units": {
          "enum": [
            "metric",
            "imperial"
          ],
          "type": "string",
          "default": "metric",
          "description": "Unit system: \"metric\" or \"imperial\""
        },
        "latitude": {
          "type": "number",
          "maximum": 90,
          "minimum": -90,
          "description": "Latitude of the location"
        },
        "longitude": {
          "type": "number",
          "maximum": 180,
          "minimum": -180,
          "description": "Longitude of the location"
        }
      },
      "additionalProperties": false
    }
    arguments 32 lines
  • tio_mcp_apps_show_fire unknown never probed

    Show the wildfire risk index (FWI) and wind conditions across 2-6 locations. USE when the user asks about fire risk, wildfire danger, or fire weather conditions.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "locations"
      ],
      "properties": {
        "units": {
          "enum": [
            "metric",
            "imperial"
          ],
          "type": "string",
          "default": "metric",
          "description": "Unit system: \"metric\" or \"imperial\""
        },
        "locations": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "latitude",
              "longitude"
            ],
            "properties": {
              "latitude": {
                "type": "number",
                "maximum": 90,
                "minimum": -90,
                "description": "Latitude"
              },
              "longitude": {
                "type": "number",
                "maximum": 180,
                "minimum": -180,
                "description": "Longitude"
              }
            },
            "additionalProperties": false
          },
          "maxItems": 6,
          "minItems": 2,
          "description": "Array of 2-6 locations with lat/lng coordinates"
        }
      },
      "additionalProperties": false
    }
    arguments 47 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 9ddbcd08dc7fc198.

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