# Zovo Weather History (remote · weather-history.zovo.one)

Past weather & daily logs

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `weather-history.zovo.one`: 74/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-weather-history/weather-history.md), [page](https://verifymcp.io/servers/theluckystrike-weather-history/weather-history)

## Channel facts

- Endpoint: `https://weather-history.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-10-23.

- **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**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 580 tokens (~193/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo Weather History MCP server?

Zovo Weather History is a hosted endpoint at https://weather-history.zovo.one/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 theluckystrike-weather-history 'https://weather-history.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-weather-history": {
      "url": "https://weather-history.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-weather-history": {
      "type": "http",
      "url": "https://weather-history.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-weather-history]
url = "https://weather-history.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-weather-history": {
      "type": "remote",
      "url": "https://weather-history.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-weather-history --url 'https://weather-history.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-weather-history:
    url: "https://weather-history.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-weather-history": {
      "Transport": "http",
      "Url": "https://weather-history.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-weather-history -t streamable-http -u 'https://weather-history.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-weather-history": {
      "type": "http",
      "url": "https://weather-history.zovo.one/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-10-23 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-22 (score 74)

First indexed and scored.

## MCP tools (2)

### `find_weather_stations` (~187 tokens)

Find weather stations

Use this when the user wants weather history, historical weather data, or past weather by zip code and needs reporting stations near a US city, ZIP or address. Returns date-specific coverage and distance for up to ten qualifying stations plus three with insufficient records. Dates default to the thirty days ending five days before today UTC; up to 366 days. Do not use for forecasts, current conditions or places outside the US.

Input parameters:

- `end_date` (string): Calendar date YYYY-MM-DD, e.g. 2026-09-01.
- `place` (string, required): US city and state, ZIP or street address, 2 to 200 characters; e.g. Denver, CO. For logs a US station ID such as USW00094728 also works.
- `start_date` (string): Calendar date YYYY-MM-DD, e.g. 2026-09-01.

Output parameters:

- `end_date` (string)
- `kind` (string)
- `place` (object)
- `source` (object)
- `start_date` (string)
- `stations` (array)

### `generate_weather_log` (~320 tokens)

Generate weather log

Use this when the user wants weather history, historical weather data, historical weather by date and location, or a daily weather data download. Reads station observations and generates Excel and CSV weather logs with rain days for construction delay and thresholds. US only; up to five sites and 366 days, from 1900 through today UTC. Files expire in about an hour. Do not use for forecasts, current conditions or certified weather reports.

Input parameters:

- `end_date` (string, required): Calendar date YYYY-MM-DD, e.g. 2026-09-01.
- `freeze_f` (number): Freeze-day maximum degrees F, inclusive; e.g. 32.
- `gust_mph` (number): Peak gust minimum mph, inclusive; e.g. 40. Average wind is not a substitute.
- `heat_f` (number): Heat-day minimum degrees F, inclusive; e.g. 90.
- `rain_in` (number): Rain-day minimum in inches, inclusive; e.g. 0.10.
- `sites` (array, required): Up to five US places, ZIPs, addresses or station IDs after removing blanks and duplicates; e.g. ["Denver, CO","10024"].
- `snow_in` (number): Snow-day minimum in inches, inclusive; e.g. 1.0.
- `start_date` (string, required): Calendar date YYYY-MM-DD, e.g. 2026-09-01.
- `weather_day_rule` (array): Weather day is any selected threshold, e.g. ["rain","snow"].

Output parameters:

- `downloads` (object)
- `duplicates_removed` (number)
- `end_date` (string)
- `kind` (string)
- `preview` (array)
- `sites` (array)
- `source` (object)
- `start_date` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-weather-history/weather-history#diagnostics

## Score history

- 2026-10-23: 74
- 2026-10-22: 74

## Common questions

### What is the Zovo Weather History MCP server?

Zovo Weather History is an MCP server listed in the public MCP registry as io.github.theluckystrike/weather-history. Past weather & daily logs. This page covers its hosted endpoint (https://weather-history.zovo.one/mcp).

### Is the Zovo Weather History MCP server safe to use?

Zovo Weather History scores 74 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 Zovo Weather History MCP server expose?

Zovo Weather History exposes 2 tools: find_weather_stations, generate_weather_log. Their descriptions and schemas cost roughly 507 tokens of context every time the server is loaded.

### Does the Zovo Weather History MCP server require authentication?

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

### Is the Zovo Weather History MCP server still maintained?

Zovo Weather History is still listed as active in the MCP registry. We last reached this channel on 23 October 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://weather-history.zovo.one/mcp
- Website: https://weather-history.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-weather-history/weather-history.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-weather-history/weather-history.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-weather-history/weather-history