# open-signals (remote · open-signals.civops.io)

Public hazard, water, weather and EPA data with source, age and licence on every reading.

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

## Components

- remote · `open-signals.civops.io`: 61/100 (this document), [markdown](https://verifymcp.io/servers/civops-platform-open-signals/open-signals.md), [page](https://verifymcp.io/servers/civops-platform-open-signals/open-signals)

## Channel facts

- Endpoint: `https://open-signals.civops.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-18.

- **Endpoint Security**: 46/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 check failed: the endpoint is reachable over plaintext HTTP.
  - 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**: 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).
  - Tool/resource definitions use about 1295 tokens (~99/item across 13 items; 9 tools + 4 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 74% of tool parameters carry a description.
- **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**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the open-signals MCP server?

open-signals is a hosted endpoint at https://open-signals.civops.io/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 civops-platform-open-signals 'https://open-signals.civops.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "civops-platform-open-signals": {
      "url": "https://open-signals.civops.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "civops-platform-open-signals": {
      "type": "http",
      "url": "https://open-signals.civops.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.civops-platform-open-signals]
url = "https://open-signals.civops.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "civops-platform-open-signals": {
      "type": "remote",
      "url": "https://open-signals.civops.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add civops-platform-open-signals --url 'https://open-signals.civops.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  civops-platform-open-signals:
    url: "https://open-signals.civops.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "civops-platform-open-signals": {
      "Transport": "http",
      "Url": "https://open-signals.civops.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add civops-platform-open-signals -t streamable-http -u 'https://open-signals.civops.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "civops-platform-open-signals": {
      "type": "http",
      "url": "https://open-signals.civops.io/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-18 (score 61, +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-10-16 (score 60, +1)

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

### 2026-10-14 (score 59, +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-10-13 (score 58, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 58)

First indexed and scored.

## MCP tools (9)

### `search_sources` (~139 tokens)

Search the catalogue of public data sources (weather, water, hazards, flights, ships, energy, filings, trade, ...). Each entry gives the API, coverage, cadence, auth needed and licence. Use it to find where a kind of data comes from before writing a fetcher.

Input parameters:

- `fetchable` (boolean): true: only sources this server can fetch now; false: only catalogued ones.
- `license` (string)
- `query` (string): Words matched against name, id, coverage, topics and licence note.
- `topic` (string): One topic, e.g. weather, water, fires, flights, energy.

### `get_source` (~21 tokens)

One catalogue entry in full.

Input parameters:

- `id` (string, required)

### `list_hubs` (~42 tokens)

Projects and catalogues that collect sources (God's Eye View, World Monitor, the MCP Registry, Source Cooperative, ...), with how each relates to this one.

### `list_places` (~44 tokens)

Named places the fetchers read for, with their upstream ids (CO-OPS station, USGS gauge, eBird region) and tags.

Input parameters:

- `tag` (string)

### `get_readings` (~418 tokens)

Fetch current readings from one source, each with value, unit, a one-line summary, place and provenance (source, URL, fetch time, licence). Sources this server will not republish (non-commercial, restricted or unreviewed licence) answer with an error naming the licence.

Input parameters:

- `bbox` (string): noaa-nwps only: xmin,ymin,xmax,ymax in degrees (≤400 sq deg); default the Great Lakes basin.
- `coops` (string): NOAA CO-OPS station id(s), comma-separated, e.g. 9063085.
- `ebird` (string): eBird region code(s), e.g. US-OH-095.
- `elevated` (boolean): usgs-volcanoes only: true keeps volcanoes above normal.
- `forecast` (boolean): false drops modelled future values.
- `lat` (number): Ad-hoc point latitude (with lng). For weather and WSI.
- `limit` (number): 1-1000, default 100.
- `lng` (number): Ad-hoc point longitude (with lat).
- `metric` (string): Only readings of this metric.
- `min` (string): usgs-earthquakes only: all | 1.0 | 2.5 | 4.5 | significant.
- `place` (string): Comma-separated catalogue place ids (see list_places).
- `since` (string): ISO date or datetime; only readings at or after it.
- `source` (string, required): A source id with a fetcher (search_sources with fetchable=true).
- `state` (string): epa-echo only: two-letter US state, default OH.
- `tag` (string): Catalogue places with this tag, e.g. waterfowl, ice-fishing.
- `usgs` (string): USGS monitoring location id(s), e.g. USGS-04193500.
- `window` (string): usgs-earthquakes only: hour | day | week.

### `list_datasets` (~57 tokens)

Static public datasets this server holds as GeoJSON (wildfire burn perimeters, public-land share by county, federal campgrounds, fire-weather stations), with source, licence, feature count and parts (one per state, or "all").

### `get_dataset_part` (~65 tokens)

The URL of one part of a dataset as GeoJSON, plus its description. Fetch the URL for the features; parts can be several megabytes.

Input parameters:

- `id` (string, required)
- `part` (string, required): Two-letter state, or "all" for single-part datasets.

### `list_layers` (~37 tokens)

Map layers this server can draw as GeoJSON, with unit, source, licence, whether it is available here, and how to read it.

### `get_layer` (~373 tokens)

One map layer as a GeoJSON FeatureCollection: one point per place with the reading on the date (else the latest observed before it, never a guess), or one point per event for event layers.

Input parameters:

- `bbox` (string)
- `continuing` (boolean): volcanoes_world: only eruptions in progress
- `coops` (string): NOAA CO-OPS station id(s), comma-separated, e.g. 9063085.
- `country` (string): power_plants: ISO alpha-3, e.g. DEU
- `date` (string): YYYY-MM-DD; default today (US Eastern).
- `ebird` (string): eBird region code(s), e.g. US-OH-095.
- `elevated` (boolean)
- `erupted_since` (number): volcanoes_world: year, default 1900
- `fuel` (string): power_plants: coal, oil/gas, nuclear, hydropower, wind, utility-scale solar, geothermal or bioenergy
- `id` (string, required)
- `indicator` (string)
- `lat` (number): Ad-hoc point latitude (with lng). For weather and WSI.
- `lng` (number): Ad-hoc point longitude (with lat).
- `min` (string)
- `min_mw` (number)
- `place` (string): Comma-separated catalogue place ids (see list_places).
- `state` (string)
- `status` (string): power_plants: operating | construction
- `tag` (string): Catalogue places with this tag, e.g. waterfowl, ice-fishing.
- `usgs` (string): USGS monitoring location id(s), e.g. USGS-04193500.
- `window` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/civops-platform-open-signals/open-signals#diagnostics

## Score history

- 2026-10-18: 61
- 2026-10-17: 60
- 2026-10-16: 60
- 2026-10-15: 59
- 2026-10-14: 59
- 2026-10-13: 58
- 2026-10-12: 58

## Common questions

### What is the open-signals MCP server?

open-signals is an MCP server listed in the public MCP registry as io.github.Civops-Platform/open-signals. Public hazard, water, weather and EPA data with source, age and licence on every reading. This page covers its hosted endpoint (https://open-signals.civops.io/mcp).

### Is the open-signals MCP server safe to use?

open-signals scores 61 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 open-signals MCP server expose?

open-signals exposes 9 tools: search_sources, get_source, list_hubs, list_places, get_readings, and 4 more. Their descriptions and schemas cost roughly 1,196 tokens of context every time the server is loaded.

### Does the open-signals MCP server require authentication?

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

### Is the open-signals MCP server still maintained?

open-signals is still listed as active in the MCP registry. We last reached this channel on 18 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://open-signals.civops.io/mcp
- Repository: https://github.com/Civops-Platform/open-signals
- Website: https://open-signals.civops.io/
- Changelog RSS feed: https://verifymcp.io/servers/civops-platform-open-signals/open-signals.xml
- Changelog JSON feed: https://verifymcp.io/servers/civops-platform-open-signals/open-signals.json
- HTML version of this page: https://verifymcp.io/servers/civops-platform-open-signals/open-signals