What's new in geo/water MCPs — week ending 2026-10-15
By Chris Cameron-Hann · Published
A reproducible weekly registry comparison of added, changed and removed geo and water MCP records.
This week's comparison covers 2026-10-09 through 2026-10-15, using UTC commit dates (end exclusive: 2026-10-16T00:00:00.000Z). It compares committed data/listings.json snapshots, not working-tree changes.
Evidence and scope
Baseline: empty baseline: no committed registry snapshot before the window. End snapshot: d6ec9737ef022f30ef8fed2f1cfd5dd0fa82a850. This is an initial registry inventory: additions mean first recorded in this repository, not newly launched this week.
Scope: non-placeholder MCP records tagged GIS, terrain, flood, hydrology, environment or climate. Tags are discovery metadata, so inclusion is not an editorial recommendation. API, dataset, plugin and directory records are excluded. A record entering or leaving this scope counts as added or removed. Timestamp-only and other untracked metadata changes are ignored.
Recorded changes: 804 added, 0 changed, 0 removed. Each section shows at most 15 entries, ordered by slug; the linked snapshots contain the full comparison evidence.
Added to the registry
- ArcGisPro-AI-assistant — regions: Global; registry score: 47; recorded health: healthy.
- 2s.io — regions: Global; registry score: 53; recorded health: healthy.
- sailing-mcp — regions: Global; registry score: 73; recorded health: healthy.
- tideways-mcp-server — regions: Global; registry score: 59; recorded health: healthy.
- geolibre-cli — regions: Global; registry score: 57; recorded health: healthy.
- QGIS-MCP — regions: Global; registry score: 65; recorded health: healthy.
- epanet-mcp — regions: United States; registry score: 55; recorded health: healthy.
- geoassist-mcp — regions: United States; registry score: 58; recorded health: healthy.
- timcp — regions: Global; registry score: 56; recorded health: healthy.
- osm-mcp — regions: Global; registry score: 59; recorded health: healthy.
- tideways-mcp-server — regions: Global; registry score: 73; recorded health: healthy.
- amap-weather-mcp-server — regions: China; registry score: 44; recorded health: healthy.
- openstreetmap-mcp — regions: Global; registry score: 63; recorded health: healthy.
- gagelink — regions: United Kingdom, United States, France; registry score: 66; recorded health: healthy.
- ng-postcode — regions: Global; registry score: 71; recorded health: healthy.
Changed records
No changes recorded in the tracked fields.
Removed from the registry or scope
No removals recorded in this scope.
What I would check next
Use the comparison as a review queue. Check geography, upstream terms and the available tools before trying a connector on a project. A healthy registry URL does not establish that a full MCP session succeeds, and an improved score is not a benchmark result. Keep the upstream identifiers and request details with any observations you retain.