open-signals
REMOTE · OPEN-SIGNALS.CIVOPS.IO
Public hazard, water, weather and EPA data with source, age and licence on every reading.
Available components
Last scanned (10 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 18 Oct 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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
- Tool/resource definitions use about 1295 tokens (~99/item across 13 items; 9 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 74% of tool parameters carry a description.Partial
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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 18 Oct 26 +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.
- 16 Oct 26 +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.
- 14 Oct 26 +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.
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 58
First indexed and scored.
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 18 Oct 2026 · Probed https://open-signals.civops.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=civops.io | CN=YE1,O=Let's Encrypt,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 535e8e8886aea03f2380f6db3258f3efa02 |
| SANs: *.civops.io, civops.io | ||||||
| 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 open-signals.civops.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| civops.io. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://open-signals.civops.io/mcp | Verified | 200 | |
| http (plaintext) | http://open-signals.civops.io/mcp | Served over HTTP | 200 |
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 →
get_dataset_part ~65
The URL of one part of a dataset as GeoJSON, plus its description. Fetch the URL for the features; parts can be several megabytes.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| part | string | yes | Two-letter state, or "all" for single-part datasets. |
No output schema declared.
No examples provided.
get_layer ~373
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| 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 | – | – |
No output schema declared.
No examples provided.
get_readings ~418
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
get_source ~21
One catalogue entry in full.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
list_datasets ~57
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").
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_hubs ~42
Projects and catalogues that collect sources (God's Eye View, World Monitor, the MCP Registry, Source Cooperative, ...), with how each relates to this one.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_layers ~37
Map layers this server can draw as GeoJSON, with unit, source, licence, whether it is available here, and how to read it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_places ~44
Named places the fetchers read for, with their upstream ids (CO-OPS station, USGS gauge, eBird region) and tags.
| Name | Type | Req | Description |
|---|---|---|---|
| tag | string | – | – |
No output schema declared.
No examples provided.
search_sources ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · open-signals.civops.io
claude mcp add --transport http civops-platform-open-signals 'https://open-signals.civops.io/mcp'
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.