EPW.tools
REMOTE · EPW.TOOLS · 2 COMPONENTS
EnergyPlus weather files (EPW, DDY, STAT) and design conditions for any site, OpenStudio-MCP ready.
Available components
Last scanned (14 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +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.
- 18 Nov 26 +1
- 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 security
- 17 Nov 26 0
- 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 security
- Schema quality: pass → fail ▼ functional
- “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” cosmetic
- 16 Nov 26 +1
- Tool “get_design_conditions” rewrote its description, which is the text the model reads security
- 15 Nov 26 0
- 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 security
- Schema quality: 89 → 101 ▼ functional
- “generate_epw” added an optional parameter “station_id” cosmetic
- 14 Nov 26 +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.
- 12 Nov 26 +1
- 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 security
- 11 Nov 26 0
- Tool “get_job_result” rewrote its description, which is the text the model reads security
- Schema quality: fair → good functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://epw.tools/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=epw.tools | CN=YE1,O=Let's Encrypt,C=US | 17 Nov 2026 | 15 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6eb8d5cfd6689cc7fcfbfcfe2e0cdbf2637 |
| SANs: *.epw.tools, epw.tools | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of epw.tools. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| tools. | DS published | 1547 | 8 | Verified |
| epw.tools. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'sha256-Du+OJKJSbdUgz5nrHeWWINvez6XKDDU/tyj/5c2uvwo=' 'sha256-2LHBnlJIfBKxCRinGaARoHtfHYFk1ScHtcEMPpztmo8=' 'unsafe-inline' https://accounts.google.com https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://accounts.google.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data: blob: https:; connect-src 'self' https://accounts.google.com https://server.arcgisonline.com https://services.arcgisonline.com https://cloudflareinsights.com; frame-src https://accounts.google.com; worker-src 'self' blob:; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'; report-uri /api/csp-report |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(self), microphone=(), camera=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://epw.tools/api/mcp | Verified | 200 | |
| http (plaintext) | http://epw.tools/api/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_epw ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
generate_epw ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | – |
| data_source | string | – | – |
| dc_edition | string | – | – |
| lat | number | yes | – |
| location_name | string | – | – |
| lon | number | yes | – |
| station_id | – | – | – |
| urban_street_level | boolean | – | – |
| year | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
generate_forecast ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | – |
| days | integer | – | – |
| lat | number | yes | – |
| location_name | string | – | – |
| lon | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
generate_future_climate ~222
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | – |
| base_year | integer | – | – |
| horizon | integer | – | – |
| lat | number | yes | – |
| location_name | string | – | – |
| lon | number | yes | – |
| model | string | – | – |
| scenario | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
generate_tmy ~205
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | – |
| data_source | – | – | – |
| dc_edition | string | – | – |
| end_year | integer | yes | – |
| lat | number | yes | – |
| location_name | string | – | – |
| lon | number | yes | – |
| start_year | integer | yes | – |
| tmy_method | – | – | – |
| use_case | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_design_conditions ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| current_climate | boolean | – | – |
| edition | string | – | – |
| lat | number | yes | – |
| location_name | – | – | – |
| lon | number | yes | – |
| mode | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_job_result ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | – |
| job_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_nearest_stations ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| lon | number | yes | – |
| n | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_cmip6_models ~166
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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.
remote · epw.tools
claude mcp add --transport http carlobianchi89-epwtools 'https://epw.tools/api/mcp'
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.