# com.pixelgust/mcp (remote · pixelgust.com)

Weather, climate, terrain, fire and flood risk data for any point or polygon on Earth. Free tier.

- Trust score: 64/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `pixelgust.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/com-pixelgust-mcp/pixelgust.md), [page](https://verifymcp.io/servers/com-pixelgust-mcp/pixelgust)

## Channel facts

- Endpoint: `https://pixelgust.com/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-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 914 tokens (~101/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 95% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-pixelgust-mcp https://pixelgust.com/mcp
```

### Codex

```toml
[mcp_servers.com-pixelgust-mcp]
url = "https://pixelgust.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-pixelgust-mcp --url https://pixelgust.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-pixelgust-mcp:
    url: "https://pixelgust.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-pixelgust-mcp": {
      "type": "http",
      "url": "https://pixelgust.com/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-08-03 (score 64, +1)

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

### 2026-08-01 (score 63, +1)

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

### 2026-07-31 (score 62, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 64, +1)

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

### 2026-07-28 (score 63, +1)

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

### 2026-07-27 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 62)

First indexed and scored.

## MCP tools (9)

### `get_current_weather` (~93 tokens)

Current weather conditions for a point: temperature, humidity, dewpoint, wind speed and direction, precipitation, pressure, cloud cover, solar radiation, plus terrain, land cover, NDVI, population density, and soil context. Source: NOAA GFS 0.25 degree, updated every 6 hours.

Input parameters:

- `lat` (number, required): Latitude in decimal degrees
- `lon` (number, required): Longitude in decimal degrees

### `get_weather_forecast` (~88 tokens)

Daily weather forecast for a point, up to 7 days ahead. day=0 is today, day=6 is six days out. Returns daily mean, min, and max per variable.

Input parameters:

- `day` (integer): Forecast day: 0=today .. 6
- `lat` (number, required): Latitude in decimal degrees
- `lon` (number, required): Longitude in decimal degrees

### `get_historical_climate` (~123 tokens)

10-year historical climate averages (2015-2025, ERA5 reanalysis) for a point. Omit month for the annual average, or pass month 1-12 for that month's climatology with min and max ranges. Use this for questions about typical climate, growing seasons, or what weather to expect at a location and time of year.

Input parameters:

- `lat` (number, required): Latitude in decimal degrees
- `lon` (number, required): Longitude in decimal degrees
- `month` (integer): Optional month 1-12; omit for annual average

### `get_climate_timeseries` (~163 tokens)

Monthly time series 2015-2025 (about 130 monthly values) for one variable at a point, plus the 12-month climatology. Variables: temperature_c, precipitation_mm, dewpoint_c, skin_temperature_c, surface_pressure_hpa, snowfall_cm, total_evaporation_mm, soil_water_layer_1_vol, wind_speed_ms, net_solar_radiation_mj_m2, relative_humidity_pct, cloud_cover_pct, ndvi, fire_weather_index. Use for trend questions (is it getting hotter or drier here?).

Input parameters:

- `lat` (number, required): Latitude in decimal degrees
- `lon` (number, required): Longitude in decimal degrees
- `variable` (string, required): Variable name from the list in the tool description

### `get_terrain` (~65 tokens)

Terrain for a point: elevation, slope, and aspect at 30m resolution (Copernicus DEM), plus Topographic Wetness Index (flood susceptibility indicator).

Input parameters:

- `lat` (number, required): Latitude in decimal degrees
- `lon` (number, required): Longitude in decimal degrees

### `get_hazards` (~70 tokens)

Natural hazard indices for a point: Fire Weather Index (current danger), soil erosion risk (RUSLE, t/ha/yr), and flood susceptibility (Topographic Wetness Index).

Input parameters:

- `lat` (number, required): Latitude in decimal degrees
- `lon` (number, required): Longitude in decimal degrees

### `get_environment` (~61 tokens)

Environmental data for a point: NDVI vegetation index (300m), annual evapotranspiration (MODIS), and ESA WorldCover land cover class.

Input parameters:

- `lat` (number, required): Latitude in decimal degrees
- `lon` (number, required): Longitude in decimal degrees

### `get_proximity` (~57 tokens)

Distances in km from a point to the nearest city, airport, port, hospital, power plant, and other key infrastructure.

Input parameters:

- `lat` (number, required): Latitude in decimal degrees
- `lon` (number, required): Longitude in decimal degrees

### `get_polygon_stats` (~119 tokens)

Aggregate statistics (mean, min, max, std) over a polygon area: weather, terrain, hazards, environment, soil, and population. Coordinates are [longitude, latitude] pairs forming a ring. Maximum area depends on plan (free tier: 100 km2). Use for area questions such as average slope of a farm or population inside a zone.

Input parameters:

- `coordinates` (array, required): [[lon, lat], ...] polygon ring (closed or open)
- `mode` (string)
- `month` (integer): Month for historical mode

## Diagnostics

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

## Score history

- 2026-08-03: 64
- 2026-08-02: 63
- 2026-08-01: 63
- 2026-07-31: 62
- 2026-07-30: 64
- 2026-07-29: 64
- 2026-07-28: 63
- 2026-07-27: 62
- 2026-07-26: 62

## Links

- Remote endpoint: https://pixelgust.com/mcp
- Website: https://pixelgust.com/docs#mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-pixelgust-mcp/pixelgust/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-pixelgust-mcp/pixelgust/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-pixelgust-mcp/pixelgust