# OpenWeather for agents (remote · mcp.openweathermap.org)

OpenWeather data for AI agents: list feeds, sign up, check balance, get a top-up link, fetch data.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `mcp.openweathermap.org`: 81/100 (this document), [markdown](https://verifymcp.io/servers/org-openweathermap-agents/mcp.md), [page](https://verifymcp.io/servers/org-openweathermap-agents/mcp)

## Channel facts

- Endpoint: `https://mcp.openweathermap.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-22.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1323 tokens (~220/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the OpenWeather for agents MCP server?

OpenWeather for agents is a hosted endpoint at https://mcp.openweathermap.org/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.

### Claude

```bash
claude mcp add --transport http org-openweathermap-agents 'https://mcp.openweathermap.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-openweathermap-agents": {
      "url": "https://mcp.openweathermap.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-openweathermap-agents": {
      "type": "http",
      "url": "https://mcp.openweathermap.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-openweathermap-agents]
url = "https://mcp.openweathermap.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-openweathermap-agents": {
      "type": "remote",
      "url": "https://mcp.openweathermap.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-openweathermap-agents --url 'https://mcp.openweathermap.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-openweathermap-agents:
    url: "https://mcp.openweathermap.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-openweathermap-agents": {
      "Transport": "http",
      "Url": "https://mcp.openweathermap.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-openweathermap-agents -t streamable-http -u 'https://mcp.openweathermap.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-openweathermap-agents": {
      "type": "http",
      "url": "https://mcp.openweathermap.org/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-22 (score 81, +1)

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

### 2026-09-20 (score 80, +1)

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

### 2026-09-18 (score 79, +1)

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

### 2026-09-15 (score 78, +1)

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

### 2026-09-13 (score 77, +1)

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

### 2026-09-11 (score 76, +1)

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

### 2026-09-10 (score 75, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “account_status” rewrote its description, which is the text the model reads
- [security] Tool “fetch_data” rewrote its description, which is the text the model reads
- [security] Tool “sign_up” rewrote its description, which is the text the model reads

### 2026-09-09 (score 75, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “fetch_data” rewrote its description, which is the text the model reads

## MCP tools (6)

### `list_products` (~88 tokens)

List products

Lists every data product the Forum serves, as the platform's own catalogue answer: slug, title, lifecycle state, price in credits per call (1 credit = $0.001; the quoted price is the charged price), licence and attribution text, and the address of the product's route specification. Needs no key and charges nothing. Call get_product next for a product's routes and required parameters.

Output parameters:

- `account`
- `body`
- `body_text` (string)
- `configure` (object)
- `fault` (object)
- `headers` (object)
- `key_source` (string)
- `record` (object)
- `request_id` (string)
- `status` (integer|null)
- `transport` (object)
- `upstream` (string|null)
- `usage` (object)

### `get_product` (~99 tokens)

Get product

Returns one product by slug: its live catalogue entry (price, licence, lifecycle state, the specification address) together with the routes fetch_data can call and the parameters each route requires, taken from the platform's published product record. Needs no key and charges nothing. Use it before fetch_data — the route names come from here; an unknown slug answers with the slugs the catalogue serves.

Input parameters:

- `product` (string, required): a product slug from list_products

Output parameters:

- `account`
- `body`
- `body_text` (string)
- `configure` (object)
- `fault` (object)
- `headers` (object)
- `key_source` (string)
- `record` (object)
- `request_id` (string)
- `status` (integer|null)
- `transport` (object)
- `upstream` (string|null)
- `usage` (object)

### `sign_up` (~200 tokens)

Sign up

Creates a Forum account for an email address under the Terms version currently served, and returns the account, its secret — the one string that runs the account, shown exactly once — and its first data key, shown exactly once. It grants the account no credits of its own: a new account's free calls are the daily credit account of each product that gives one, spendable on that product alone and replaced every night, and list_products states which products give one and how much. The result's configure block is the client configuration entry that sends the data key from then on; until the client reconnects, pass data_key.key as data_key on fetch_data. Keep the secret with the owner and pass it as secret on account_status and get_topup_link. An address that already has an account answers 409 email_exists with next_action login_to_link.

Input parameters:

- `email` (string, required): the owner's email address — the account's identity; one account per address

Output parameters:

- `account`
- `body`
- `body_text` (string)
- `configure` (object)
- `fault` (object)
- `headers` (object)
- `key_source` (string)
- `record` (object)
- `request_id` (string)
- `status` (integer|null)
- `transport` (object)
- `upstream` (string|null)
- `usage` (object)

### `account_status` (~188 tokens)

Account status

Reads the account behind the secret: tier, accepted Terms version, the products it may call, the balance in credits the account bought minus the spend those credits funded, the last 30 days of usage per day, product and key, and the 50 latest balance movements. A product's own daily credits are spent before that balance and are no part of it, so a call can be served while it reads zero; list_products carries each product's credit account. Pass the secret sign_up returned as the secret argument; the data key your client configuration sends cannot read the account and answers 403 wrong_credential. Charges nothing; without a string the platform answers 401 invalid_key.

Input parameters:

- `secret` (string): the account's secret — the string sign_up returned as secret; the client configuration's header holds the data key, which this tool cannot use; when both are present the argument wins

Output parameters:

- `account`
- `body`
- `body_text` (string)
- `configure` (object)
- `fault` (object)
- `headers` (object)
- `key_source` (string)
- `record` (object)
- `request_id` (string)
- `status` (integer|null)
- `transport` (object)
- `upstream` (string|null)
- `usage` (object)

### `get_topup_link` (~212 tokens)

Get top-up link

Opens a top-up for the account and returns the payment intent with hosted_url, the payment provider's short-lived page where a human completes the payment — no tool pays, and card details never touch the Forum. amount_minor is in cents; the platform accepts USD only and a minimum of 1000 (= $10). Pass the secret sign_up returned as the secret argument; the data key cannot open a payment. Asking again while a page is open returns the same page. Bought credits appear in account_status once the payment completes.

Input parameters:

- `amount_minor` (integer, required): the amount in the currency's minor unit (cents); the platform's minimum is 1000 = $10 and the platform checks it
- `currency` (string): USD is the only currency the platform accepts; the platform refuses any other
- `secret` (string): the account's secret — the string sign_up returned as secret; the data key in the client configuration cannot open a payment; when both are present the argument wins

Output parameters:

- `account`
- `body`
- `body_text` (string)
- `configure` (object)
- `fault` (object)
- `headers` (object)
- `key_source` (string)
- `record` (object)
- `request_id` (string)
- `status` (integer|null)
- `transport` (object)
- `upstream` (string|null)
- `usage` (object)

### `fetch_data` (~312 tokens)

Fetch data

Fetches one data response: GET data.openweathermap.org/{product}/{route} with the query parameters you pass, using the data key from your client configuration's Authorization header or the data_key argument — never the secret, which fetches nothing. A successful call is billed the product's price per call; a refused call costs nothing. The result carries the payload with the platform's meta block (licence and attribution) and the rate-limit headers; the balance is read with account_status, never from a data response. Every refusal is the platform's error envelope unchanged — a code from https://agents.openweathermap.org/errors.json; 402 payment_required means the key is known but cannot pay for this product now, and 401 invalid_key means it is authorized for no product at all, most often because every credit is spent. Both carry an action_url: a human tops up there (get_topup_link returns the page) and the same key serves again within the engine's build interval plus the region's poll interval.

Input parameters:

- `data_key` (string): only when the client cannot send an Authorization header — the data_key.key sign_up returned in this session; when both are present the argument wins
- `params` (object): query parameters, sent as given; the parameters a route requires are in get_product
- `product` (string, required): a product slug from list_products
- `route` (string, required): a route from get_product, without the product prefix — e.g. current or timeline/1h

Output parameters:

- `account`
- `body`
- `body_text` (string)
- `configure` (object)
- `fault` (object)
- `headers` (object)
- `key_source` (string)
- `record` (object)
- `request_id` (string)
- `status` (integer|null)
- `transport` (object)
- `upstream` (string|null)
- `usage` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-openweathermap-agents/mcp#diagnostics

## Score history

- 2026-09-22: 81
- 2026-09-21: 80
- 2026-09-20: 80
- 2026-09-19: 79
- 2026-09-18: 79
- 2026-09-17: 78
- 2026-09-16: 78
- 2026-09-15: 78
- 2026-09-14: 77
- 2026-09-13: 77
- 2026-09-12: 76
- 2026-09-11: 76
- 2026-09-10: 75
- 2026-09-09: 75
- 2026-09-08: 75
- 2026-09-07: 75
- 2026-09-06: 74
- 2026-09-05: 74
- 2026-09-04: 73

## Common questions

### What is the OpenWeather for agents MCP server?

OpenWeather for agents is an MCP server listed in the public MCP registry as org.openweathermap/agents. OpenWeather data for AI agents: list feeds, sign up, check balance, get a top-up link, fetch data. This page covers its hosted endpoint (https://mcp.openweathermap.org/mcp).

### Is the OpenWeather for agents MCP server safe to use?

OpenWeather for agents scores 81 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 OpenWeather for agents MCP server expose?

OpenWeather for agents exposes 6 tools: list_products, get_product, sign_up, account_status, get_topup_link, fetch_data. Their descriptions and schemas cost roughly 1,099 tokens of context every time the server is loaded.

### Does the OpenWeather for agents MCP server require authentication?

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

### Is the OpenWeather for agents MCP server still maintained?

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

## Links

- Remote endpoint: https://mcp.openweathermap.org/mcp
- Website: https://openweathermap.org/
- Changelog RSS feed: https://verifymcp.io/servers/org-openweathermap-agents/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-openweathermap-agents/mcp.json
- HTML version of this page: https://verifymcp.io/servers/org-openweathermap-agents/mcp