open-signals MCP server
io.github.Civops-Platform/open-signalsCivops-Platformstreamable-httpv0.1.0Scanned
Public hazard, water, weather and EPA data with source, age and licence on every reading.
9 tools: 9 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the open-signals MCP server can do
The open-signals MCP server is published by the GitHub account Civops-Platform. It has 9 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
2 tools bring in text other people can write (get_readings and get_dataset_part).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 15, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Only reads 9Show 9 read-only tools
get_dataset_partThe URL of one part of a dataset as GeoJSON, plus its description.Reads text others writeNo findings
Why it is in this group
- The name "get_dataset_part" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it The URL of one part of a dataset as GeoJSON, plus its description. Fetch the URL for the features; parts can be several megabytes.
get_layerOne 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…No findings
Why it is in this group
- The name "get_layer" says "get": a word for reading.
Description, as the server wrote it 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.
get_readingsFetch current readings from one source, each with value, unit, a one-line summary, place and provenance (source, URL, fetch time, licence).Reads text others writeNo findings
Why it is in this group
- The name "get_readings" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
get_sourceOne catalogue entry in full.No findings
Why it is in this group
- The name "get_source" says "get": a word for reading.
Description, as the server wrote it One catalogue entry in full.
list_datasetsStatic public datasets this server holds as GeoJSON (wildfire burn perimeters, public-land share by county, federal campgrounds, fire-weather stations), with source, licence, featu…No findings
Why it is in this group
- The name "list_datasets" says "list": a word for reading.
Description, as the server wrote it 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").
list_hubsProjects and catalogues that collect sources (God's Eye View, World Monitor, the MCP Registry, Source Cooperative, ...), with how each relates to this one.No findings
Why it is in this group
- The name "list_hubs" says "list": a word for reading.
Description, as the server wrote it 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_layersMap layers this server can draw as GeoJSON, with unit, source, licence, whether it is available here, and how to read it.No findings
Why it is in this group
- The name "list_layers" says "list": a word for reading.
Description, as the server wrote it Map layers this server can draw as GeoJSON, with unit, source, licence, whether it is available here, and how to read it.
list_placesNamed places the fetchers read for, with their upstream ids (CO-OPS station, USGS gauge, eBird region) and tags.No findings
Why it is in this group
- The name "list_places" says "list": a word for reading.
Description, as the server wrote it Named places the fetchers read for, with their upstream ids (CO-OPS station, USGS gauge, eBird region) and tags.
search_sourcesSearch the catalogue of public data sources (weather, water, hazards, flights, ships, energy, filings, trade, ...).No findings
Why it is in this group
- The name "search_sources" says "search": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:57 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:get_layerOnly readsinputSchema
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http open-signals https://open-signals.civops.io/mcpclaude mcp add --transport http open-signals https://open-signals.civops.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__open-signals__search_sources",
"mcp__open-signals__get_source",
"mcp__open-signals__list_hubs",
"mcp__open-signals__list_places",
"mcp__open-signals__get_readings",
"mcp__open-signals__list_datasets",
"mcp__open-signals__get_dataset_part",
"mcp__open-signals__list_layers",
"mcp__open-signals__get_layer"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as open-signals. Review it before you use it.
Capability tags behind 2 rules
- mcp__open-signals__get_readings untrusted-input
- mcp__open-signals__get_dataset_part untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Civops-Platform/open-signals/verify?hash=118d4fe07028825fadb06589eaa5273b8b5557193e428c2bc8f160dc3ddb97ce" | jq -e '.changed == false'Pinned hash 118d4fe07028, from Nov 15, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Civops-Platform/open-signals/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Civops-Platform/open-signals)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:15 UTC.
open-signals MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the open-signals MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the open-signals MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the open-signals MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the open-signals MCP server have?
- 9 tools: 9 read. search_sources, get_source, list_hubs, list_places, get_readings, list_datasets, get_dataset_part, list_layers and 1 more.
Does the open-signals MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the open-signals MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the open-signals MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.