# EPW.tools (remote · epw.tools)

EnergyPlus weather files (EPW, DDY, STAT) and design conditions for any site, OpenStudio-MCP ready.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `epw.tools`: 75/100 (this document), [markdown](https://verifymcp.io/servers/carlobianchi89-epwtools/api-mcp.md), [page](https://verifymcp.io/servers/carlobianchi89-epwtools/api-mcp)
- pypi · `epwtools`: 63/100, [markdown](https://verifymcp.io/servers/carlobianchi89-epwtools/epwtools.md), [page](https://verifymcp.io/servers/carlobianchi89-epwtools/epwtools)

## Channel facts

- Endpoint: `https://epw.tools/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.5`

## 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-11-21.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - 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**: 77/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 1536 tokens (~118/item across 13 items; 9 tools + 4 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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.

## Install

### How do I install the EPW.tools MCP server?

EPW.tools is a hosted endpoint at https://epw.tools/api/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 carlobianchi89-epwtools 'https://epw.tools/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "carlobianchi89-epwtools": {
      "url": "https://epw.tools/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "carlobianchi89-epwtools": {
      "type": "http",
      "url": "https://epw.tools/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.carlobianchi89-epwtools]
url = "https://epw.tools/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "carlobianchi89-epwtools": {
      "type": "remote",
      "url": "https://epw.tools/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add carlobianchi89-epwtools --url 'https://epw.tools/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  carlobianchi89-epwtools:
    url: "https://epw.tools/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "carlobianchi89-epwtools": {
      "Transport": "http",
      "Url": "https://epw.tools/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add carlobianchi89-epwtools -t streamable-http -u 'https://epw.tools/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "carlobianchi89-epwtools": {
      "type": "http",
      "url": "https://epw.tools/api/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-11-20 (score 75, +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-11-18 (score 74, +1)

- [security] Tool “list_cmip6_models” rewrote its description, which is the text the model reads
- [security] Tool “generate_future_climate” rewrote its description, which is the text the model reads

### 2026-11-17 (score 73, 0)

- [security] Tool “generate_tmy” rewrote its description, which is the text the model reads
- [security] Tool “get_nearest_stations” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [cosmetic] “generate_tmy” added an optional parameter “data_source”
- [cosmetic] “generate_tmy” added an optional parameter “tmy_method”
- [cosmetic] “generate_tmy” added an optional parameter “use_case”

### 2026-11-16 (score 73, +1)

- [security] Tool “get_design_conditions” rewrote its description, which is the text the model reads

### 2026-11-15 (score 72, 0)

- [security] Tool “generate_epw” rewrote its description, which is the text the model reads
- [security] Tool “generate_future_climate” rewrote its description, which is the text the model reads
- [security] Tool “get_design_conditions” rewrote its description, which is the text the model reads
- [security] Tool “list_cmip6_models” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 89 → 101
- [cosmetic] “generate_epw” added an optional parameter “station_id”

### 2026-11-14 (score 72, +1)

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

### 2026-11-12 (score 71, +1)

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

### 2026-11-11 (score 70, 0)

- [security] Tool “get_job_result” rewrote its description, which is the text the model reads
- [functional] Schema quality: fair → good

## MCP tools (9)

### `get_nearest_stations` (~98 tokens)

Nearest weather stations to a point (name, WMO id, distance, years of record). Free, no key.

meteostat_hourly_end (also given as hourly_end) is the end date of the Meteostat station inventory, not the
station's last report: newer hours are read from NOAA GHCNh.

Input parameters:

- `lat` (number, required)
- `lon` (number, required)
- `n` (integer)

Output parameters:

- `result` (string)

### `get_design_conditions` (~207 tokens)

Heating and cooling design conditions for any site, free, in one of two modes that are never mixed.

mode="ashrae_method": the ASHRAE Handbook Ch. 14 method replicated at the nearest ASHRAE station for the
chosen edition (2025, 2021, 2017, 2013, 2009, 2005); about 0.23 degC mean absolute difference from the published tables.
mode="enhanced": EPW.tools Enhanced, not the ASHRAE method: values at the site itself, cooling moved to the
coming decade (heating from the station record), with a tested 90 % range. The DDY file for Enhanced costs 1 credit through the web or the API.

Input parameters:

- `current_climate` (boolean)
- `edition` (string)
- `lat` (number, required)
- `location_name`
- `lon` (number, required)
- `mode` (string)

Output parameters:

- `result` (string)

### `list_cmip6_models` (~166 tokens)

The models available for future-climate morphing: `default` is what a request without a model gets (the
CMIP6 ensemble median, id "ensemble-median"); `models` are global CMIP6 models (NASA NEX-GDDP, 25 km);
\`regional` are EURO-CORDEX pairs (12.5 km, Europe only, 27-72 N / 25 W-45 E) usable as `model` ids. A
EURO-CORDEX pair follows the RCP scenarios: its `scenarios` are the SSP ids it accepts (never ssp370) and
\`forcing` names the RCP run each one is served from; the file is named and labelled by that RCP. Free.

Output parameters:

- `result` (string)

### `analyze_epw` (~66 tokens)

Summary statistics of any public EPW by URL (OneBuilding, EnergyPlus, a shared file): location header,
dry-bulb mean/min/max, annual global horizontal irradiation, data range warnings. Free, no key. 10 MB max.

Input parameters:

- `url` (string, required)

Output parameters:

- `result` (string)

### `generate_epw` (~166 tokens)

Start an actual-year (AMY) EPW + DDY + STAT for any point, 1990 to last year. 1 credit; +2 with
urban_street_level (53 US cities: hourly street-level air temperature from citizen stations). station_id
(from get_nearest_stations) builds the year from that station instead of the nearest usable one. Returns a
job_id; poll with get_job_result.

Input parameters:

- `api_key` (string, required)
- `data_source` (string)
- `dc_edition` (string)
- `lat` (number, required)
- `location_name` (string)
- `lon` (number, required)
- `station_id`
- `urban_street_level` (boolean)
- `year` (integer, required)

Output parameters:

- `result` (string)

### `generate_tmy` (~205 tokens)

Start a typical meteorological year from a chosen period (at least 5 years; 10-20 is usual). 1 credit.
tmy_method: "nrel" (Sandia method, default) or "onebuilding" (ISO 15927-4; paid). data_source: "hybrid"
(station weather + reanalysis sun, default), "merra2" or "meteostat". use_case: weight preset "default", "pv",
"daylighting", "ventilation", "hvac" or "csp". Left out, each takes the server default.

Input parameters:

- `api_key` (string, required)
- `data_source`
- `dc_edition` (string)
- `end_year` (integer, required)
- `lat` (number, required)
- `location_name` (string)
- `lon` (number, required)
- `start_year` (integer, required)
- `tmy_method`
- `use_case`

Output parameters:

- `result` (string)

### `generate_future_climate` (~222 tokens)

Start a CMIP6-morphed future EPW (Belcher 2005). scenario: ssp126, ssp245, ssp370, ssp585; horizon: any
decade 2030-2100; model: leave empty for the default, the CMIP6 ensemble median (per month and variable, the
median change of the ten CMIP6 models; recommended), or one id from list_cmip6_models. A EURO-CORDEX model takes ssp126, ssp245 or ssp585 only and
the file is the RCP2.6, RCP4.5 or RCP8.5 run, labelled as that RCP; ssp370 is refused. 3 credits.

Input parameters:

- `api_key` (string, required)
- `base_year` (integer)
- `horizon` (integer)
- `lat` (number, required)
- `location_name` (string)
- `lon` (number, required)
- `model` (string)
- `scenario` (string)

Output parameters:

- `result` (string)

### `generate_forecast` (~86 tokens)

Start a forecast EPW for the next 1-15 days (operational sims, MPC, demand response). 1 credit; more than
7 days needs an account that has bought credits.

Input parameters:

- `api_key` (string, required)
- `days` (integer)
- `lat` (number, required)
- `location_name` (string)
- `lon` (number, required)

Output parameters:

- `result` (string)

### `get_job_result` (~65 tokens)

Status of a job started by a generate_* tool; when complete, the download URLs. The links are valid for a
short time (see downloads_note); call this tool again for fresh ones.

Input parameters:

- `api_key` (string, required)
- `job_id` (string, required)

Output parameters:

- `result` (string)

## Diagnostics

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

## Score history

- 2026-11-21: 75
- 2026-11-20: 75
- 2026-11-19: 74
- 2026-11-18: 74
- 2026-11-17: 73
- 2026-11-16: 73
- 2026-11-15: 72
- 2026-11-14: 72
- 2026-11-13: 71
- 2026-11-12: 71
- 2026-11-11: 70
- 2026-11-10: 70
- 2026-11-09: 69
- 2026-11-08: 69
- 2026-11-07: 68
- 2026-11-06: 68
- 2026-11-05: 67
- 2026-11-04: 67

## Common questions

### What is the EPW.tools MCP server?

EPW.tools is an MCP server listed in the public MCP registry as io.github.carlobianchi89/epwtools. EnergyPlus weather files (EPW, DDY, STAT) and design conditions for any site, OpenStudio-MCP ready. This page covers its hosted endpoint (https://epw.tools/api/mcp).

### Is the EPW.tools MCP server safe to use?

EPW.tools scores 75 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 EPW.tools MCP server expose?

EPW.tools exposes 9 tools: get_nearest_stations, get_design_conditions, list_cmip6_models, analyze_epw, generate_epw, and 4 more. Their descriptions and schemas cost roughly 1,281 tokens of context every time the server is loaded.

### Does the EPW.tools MCP server require authentication?

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

### Is the EPW.tools MCP server still maintained?

EPW.tools is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the EPW.tools MCP server?

VerifyMCP ran 12 checks on EPW.tools, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about EPW.tools: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://epw.tools/api/mcp
- Repository: https://github.com/carlobianchi89/epwtools-python
- Website: https://epw.tools/ai-weather-files
- Changelog RSS feed: https://verifymcp.io/servers/carlobianchi89-epwtools/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/carlobianchi89-epwtools/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/carlobianchi89-epwtools/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/carlobianchi89-epwtools/api-mcp
