Data offered docs-verified: runtime code execution in the running Phoenix app (project_eval) · live app logs (get_logs) · development database SQL queries (execute_sql_query) · module/function source locations, including hex dependencies (get_source_location) · documentation pinned to mix.lock versions (get_docs)
Formats docs-verified: MCP streamable HTTP · MCP stdio
Access docs-verified: Open source under Apache License 2.0; installed as a dev-only hex dependency (tidewave ~> 0.9, only: :dev); no credentials documented in DOCS

Useful for

Use cases llm-inferred: Debug a failing code path in a Phoenix data or asset app against live dev state using project_eval · Read request logs and backtraces with get_logs when a Phoenix app misbehaves during development · Verify records written by a Phoenix app in the dev database with execute_sql_query · Jump to the definition of a function in a hex dependency with get_source_location instead of grepping
Audience llm-inferred: Elixir/Phoenix developers · web developers building internal Phoenix tools · GIS and data developers maintaining Phoenix apps

Limitations

Constraints docs-verified: Phoenix applications only · development-only: the plug is intended for Mix.env() == :dev · tools execute arbitrary Elixir and SQL against the running dev app and dev database · localhost-only by default; remote access needs the allow_remote_access option · works best with Phoenix LiveView v1.1 or later · worktrees need mix tidewave.proxy as a STDIO MCP · no geographic or hosted dataset; output reflects only the local app's state

environment hydrology

Globalhealthy

mcp

83/100Currency A

tidewave_rails ↗

MCP server with runtime-level tools for Rails development

What's in it

Data offered docs-verified: runtime code evaluation in the running Rails app (project_eval) · live app logs · development database query results (execute_sql_query) · source file and line locations of classes, modules and methods, including gem dependencies (get_source_location) · documentation for classes, methods and constants pinned to Gemfile.lock gem versions (get_docs)
Formats docs-verified: MCP streamable HTTP
Access llm-inferred: Open source under the Apache License 2.0; no credentials documented in README. Requires a local Rails development app with the tidewave gem added to the development group.

Useful for

Use cases llm-inferred: Reproduce a failing code path against live app state with project_eval when debugging a Rails web tool · Confirm that a create action saved expected records by querying the development database with execute_sql_query · Check method signatures in the exact gem versions locked in Gemfile.lock with get_docs before generating code · Jump to the defining file and line of a gem method with get_source_location when extending a Rails app
Audience llm-inferred: Ruby on Rails developers · web application developers building internal tools for consultancies

Limitations

Constraints llm-inferred: Development use only; not meant for production · Raises an error in any environment where code reloading is disabled · Requires a running Rails app with the tidewave gem in the development group · Accepts requests from localhost only by default · Toolbar may not appear if compression middleware runs after Tidewave · Multiple hosts or subdomains need *.localhost and session configuration changes · Provides no routes or associations tools by design · Contains no UK water, civils or environmental datasets; it is a developer tool, not a data source

environment hydrology

Globalhealthy

mcp

77/100Currency A

Agentic SWMM is an automated, auditable, and memory-informed framework for reproducible stormwater modelling, integrating QGIS and EPA SWMM through the aiswmm runtime, reusable Skills, and MCP interfaces, with QA verification, provenance tracking, calibration support, and Codex, Hermes, Claude code as well as OpenClaw compatibility

What's in it

Data offered docs-verified: SWMM input files (model.inp) · SWMM report and binary outputs (.rpt, .out) · run manifests, command traces and QA summaries · parsed peak-flow metrics · rainfall-runoff figures · calibration summaries · fuzzy uncertainty summaries · audit records (experiment_provenance.json, comparison.json, experiment_note.md) · modelling memory summaries · SWMM networks from SWMMCanada (Canada) or SWMManywhere synthesis (elsewhere)
Coverage docs-verified: Canada: real storm networks for 35 cities, synthesis elsewhere in Canada; SWMManywhere-based synthesis outside Canada
Formats docs-verified: SWMM INP · SWMM RPT · SWMM OUT (binary) · JSON · GeoJSON · Parquet · PNG · Word (.docx) · Markdown (Obsidian-ready notes)
Access docs-verified: Free, open-source under MIT licence; local install via one-line installer, Docker image or pip (aiswmm); LLM provider API key needed for most routes, three of ten need none

Useful for

Use cases llm-inferred: Stormwater drainage model build from GIS inputs with QA and audit trail · Peak-flow and rainfall-runoff screening for drainage strategy options · Reproducible SWMM run handover with provenance records for client review
Audience llm-inferred: drainage engineers · hydrologists · stormwater modellers · GIS analysts

Limitations

Constraints llm-inferred: Pre-1.0 (v0.9.4), so interfaces may change · Real storm networks only for 35 Canadian cities via SWMMCanada; elsewhere SWMManywhere synthesis, which is not a calibrated or validated network · Validation rows are evidence-bounded: GIS preprocessing concept, prepared-input path and uncertainty smoke are not calibrated performance claims · Raw GIS path handles structured layers only, not arbitrary CAD/GIS recognition · ENTRY lists region as United States, but DOCS do not describe US or UK coverage, so UK suitability is unverified · Agent features need an LLM provider; one-line installers run a remote script · ENTRY auth says no credentials documented, but DOCS describe API key configuration · No MCP tool names or transport documented in DOCS; ENTRY tools list is empty · One evidence row (v0.7.1) states calibration is next-milestone scope

hydrology gis flood

United Stateshealthy

mcp

76/100Currency A

ocean-brain ↗

Self-hosted knowledge base for organizing notes, thoughts, and projects with backlinks, properties, views, reminders, and MCP integration.

What's in it

Data offered docs-verified: notes · backlinks · tags · typed properties · saved views · graph · reminders · calendar date lookup · Markdown and HTML export
Formats docs-verified: Markdown · HTML
Access docs-verified: Free and open source under the MIT licence; self-hosted; password mode or local open mode

Useful for

Use cases llm-inferred: Log project decisions and meeting notes, linked by backlinks, for a consultancy project · Keep research trails for a site investigation or desk study connected as the thinking develops · Track ideas and open actions with reminders and saved table views across a project
Audience llm-inferred: project managers · consultants · researchers · project teams

Limitations

Constraints llm-inferred: Not an environmental, hydrological or geospatial data source; the docs describe a note-taking workspace · Persistent, shared use requires self-hosting; the live demo has no server-backed features · Source development requires Node.js 22.13+ and pnpm 10.25.0 · Access beyond the user's own machine requires password mode

environment hydrology

Some details auto-extracted · unverified

Globalhealthy

dataset

75/100Currency A

BoM Design Rainfall (IFD) ↗

Australian IFD rainfall

hydrology

Australiarestricted

dataset

75/100Currency A

LAWA Land Air Water Aotearoa ↗

NZ river quality

hydrology water-quality

New Zealandrestricted

mcp

75/100Currency A

ocean-mcp ↗

MCP servers for coastal oceanography

What's in it

Data offered docs-verified: NOAA CO-OPS tides, water levels, currents, meteorological data · ERDDAP dataset access across 80+ public servers · NHC storm tracks, advisories, HURDAT2 best track data · Hurricane reconnaissance HDOB, Vortex Data Messages, ATCF fixes · STOFS storm surge forecasts and observation validation · OFS regional ocean model forecasts (water level, temperature, salinity) · RTOFS global ocean forecasts (SST, salinity, currents, SSH) · WW3 GFS-Wave forecasts and NDBC buoy wave observations · NDBC buoy observations (waves, SST, wind, pressure) · NWS ASOS/AWOS surface wind observations · USGS streamflow, NWS/NWPS flood status, peak events · GOES-18/19 satellite imagery (visible, infrared, water vapor) · ADCIRC and SCHISM model setup debugging and config validation (tooling, not data)
Coverage llm-inferred: United States coastal and ocean waters (NOAA sources); RTOFS is global
Formats docs-verified: markdown · JSON · GeoJSON · image
Access docs-verified: Free and open; no API key for the data servers; MIT licence. hpc-system-mcp and ufs-runner-mcp need NOAA RDHPCS cluster access

Useful for

Use cases llm-inferred: US coastal flood-risk screening: CO-OPS water levels and flood statistics at a nearby tide station · Storm surge forecast comparison against tide-gauge observations for coastal flood assessment · Stream flow and NWS flood status checks near a US site via USGS Water Services · Wave and wind climate context from NDBC buoy observations for marine or coastal design
Audience llm-inferred: coastal engineers · hydrologists · oceanographers · GIS analysts · environmental consultants working on US projects

Limitations

Constraints llm-inferred: Coverage is US/NOAA-focused; no UK or European data sources are described · Several servers are not on PyPI and must be installed from source (vdatum-mcp, hpc-system-mcp, ufs-runner-mcp, alert-mcp) · hpc-system-mcp and ufs-runner-mcp require NOAA RDHPCS cluster access; ufs-runner-mcp submits real Slurm jobs · nos-workflow-mcp is experimental and not ready for general use · Data servers depend on upstream public NOAA, USGS and ERDDAP endpoints, so availability is outside the project's control · Monorepo has 13 published servers in the table, so each must be installed and configured separately

climate environment hydrology

Some details auto-extracted · unverified

United Stateshealthy

mcp

74/100Currency A

Open-Meteo MCP ↗

A comprehensive MCP server providing access to Open-Meteo weather APIs for Large Language Models

What's in it

Data offered docs-verified: weather forecast up to 16 days · ERA5 historical weather from 1940 · air quality (PM2.5, PM10, ozone, NO2, pollen, European and US AQI, UV index) · marine waves, swell and sea surface temperature · ensemble forecasts · seasonal outlook from a few weeks to about 7 months · CMIP6 climate projections 1950 to 2050 · river discharge via GloFAS (flood_forecast) · geocoding · elevation
Coverage llm-inferred: Not stated for the server as a whole. GFS is global, DWD ICON focuses on Europe and MET Norway on Nordic countries. UK is not named. · 1940 to yesterday (ERA5 archive); CMIP6 projections 1950 to 2050
Resolution llm-inferred: Temporal: hourly, daily and 15-minute series. Spatial resolution not stated.
Formats llm-inferred: JSON · MCP stdio · MCP streamable HTTP
Access docs-verified: Free for non-commercial use; no API key needed for the Open-Meteo APIs. Server licence MIT. API_KEY applies only to the server's own HTTP transport.

Useful for

Use cases llm-inferred: ERA5 rainfall and temperature history (weather_archive) for FRA or drainage baseline climatology · Forecast rainfall and wind for construction-phase site planning · GloFAS river discharge screening (flood_forecast) at site coordinates before gauge data review · CMIP6 climate projections (climate_projection) for climate-change allowances in drainage strategy
Audience llm-inferred: flood consultants · drainage engineers · hydrologists · planners · GIS analysts

Limitations

Constraints llm-inferred: Docs cover free use for non-commercial purposes only; commercial consultancy use must be checked against Open-Meteo terms · ENTRY auth lists API_KEY, but the docs say no key is needed for Open-Meteo; API_KEY only protects HTTP mode · Model-specific tools are regional (ICON for Germany/Europe, MET Norway for Nordic countries); UK coverage is not named · GloFAS flood discharge is modelled, not gauge observations · Responses over 25,000 characters are truncated; narrow the date range or variables to get full data · Response cache is in-memory only and not persistent · Archive ranges ending within the last 5 days are still being backfilled by Open-Meteo · Tool argument names in example_tool_calls are inferred from Open-Meteo API conventions, not from DOCS · Docs give no maintenance or release-status information

climate gis hydrology

Globalhealthy

mcp

74/100Currency A

Perigee-Tides ↗

Perigee-Tides

What's in it

Data offered docs-verified: water levels (1-min, 6-min, hourly observed) · tide predictions (hilo and interval) · currents (observed and predicted) · meteorological data · marine wind and wave forecasts (NWS) · station metadata and directory · tidal datums · harmonic constituents · prediction offsets · sea level trends · sea level rise projections (2022 Interagency scenarios) · extreme water levels (AEP) · top ten water levels · high tide flooding counts and projections · sun and moon calculations
Coverage docs-verified: US NOAA CO-OPS station network; no UK station coverage stated · hilo predictions up to a 10-year request span; observation archive length not stated
Resolution docs-verified: Observed water levels at 1-minute, 6-minute or hourly intervals; spatial resolution not stated
Formats docs-verified: JSON · Markdown tables · MCP stdio · MCP streamable HTTP
Access docs-verified: Free and open, no API key required (NOAA CO-OPS APIs are open); MIT licence

Useful for

Use cases llm-inferred: Tide and surge-context review for coastal flood risk assessment at US comparison sites · Sea level trend and 2022 SLR projection inputs for coastal climate-resilience appraisal (US sites) · Tidal datum (MLLW, MSL, NAVD88) and harmonic constituent checks for estuary or outfall modelling (US stations) · Marine wind and wave briefing for coastal works programme planning (US waters)
Audience llm-inferred: flood consultants · coastal engineers · hydrologists · marine civils engineers · planners

Limitations

Constraints llm-inferred: Great Lakes stations have no tide predictions · Subordinate (S) prediction stations only support hilo predictions · Predictions are astronomical; storm surge is not included · Per-product request-span limits are enforced client-side (e.g. 4 days for 1-minute data) · Oversized results return a response_too_large error rather than truncated data · NWS forecasts are limited to US lat/lon, up to about 7 days · No UK station coverage is stated; the NOAA network is US-centred · Tool argument names are not documented in DOCS; verify against the tool schema

environment hydrology

Some details auto-extracted · unverified

Globalhealthy

mcp

74/100Currency A

codeocean-mcp-server ↗

Code Ocean MCP Server

What's in it

Data offered docs-verified: search capsules and pipelines · run capsules and pipelines · release capsules and pipelines · manage data assets
Formats docs-verified: MCP stdio · MCP streamable HTTP
Access docs-verified: API key (Code Ocean access token) via CODEOCEAN_TOKEN, requiring a Code Ocean platform account; licence MIT (ENTRY metadata)

Useful for

Use cases llm-inferred: Re-running a shared capsule for a flood or drainage model after updated rainfall inputs · Releasing a versioned capsule or pipeline as a reproducible analysis record for a project deliverable · Managing data assets that hold survey or monitoring inputs for a civils or environmental study
Audience llm-inferred: hydrologists · drainage engineers · GIS analysts

Limitations

Constraints llm-inferred: Requires a Code Ocean platform account and access token · Tied to a specific Code Ocean deployment via CODEOCEAN_DOMAIN · Tested against a minimum Code Ocean platform API version; pin the package version to match the deployment · Local install needs uv and Python 3.10 or newer · Streamable HTTP refuses requests without a token · No environmental or UK geospatial datasets are described in the docs · No tool names are listed in the metadata or docs, so tool calls cannot be confirmed from this entry

environment hydrology

Some details auto-extracted · unverified

Globalhealthy

mcp

73/100Currency A

sailing-mcp ↗

Remote MCP server for sailing navigation — wind/wave forecasts, tides, currents, marinas, bridge schedules and live AIS. Stateless, multi-tenant (users bring their own API keys).

What's in it

Data offered docs-verified: wind forecasts · wave forecasts · tides (HW/LW, observed, forecast, surge) · tidal currents · marina, harbour and anchorage POIs · scheduled bridge openings · Notices to Skippers · fairway depths and bridge air-draft clearance · locks · METAR/TAF aviation weather · sunrise, sunset, twilight and moon phase · live AIS vessel snapshot · global tide predictions (key required) · multi-source tidal/ocean currents (key required)
Coverage docs-verified: Dutch / North Sea waters (strong focus); some tools are global
Formats docs-verified: MCP streamable HTTP
Access docs-verified: Public-data tools need no key. Windy, WorldTides, Stormglass and AISStream need the user's own API key passed in the URL; all except Windy have a free tier. Server licence MIT (per ENTRY metadata, not DOCS).

Useful for

Use cases llm-inferred: Tide and surge levels at Dutch coastal sites for marine works or outfall boundary checks (tides_nl) · Wind and wave forecast windows for coastal survey or dredging campaign planning · Bridge clearance and fairway depth checks for barge or crane access routes (fairway_nl)
Audience llm-inferred: coastal and marine engineers · hydrologists · civils and BIM engineers planning marine logistics · GIS analysts

Limitations

Constraints llm-inferred: Built and documented for recreational sailing, not engineering or regulatory use · Official charts, almanacs and notices must be checked before relying on outputs · Windy, WorldTides, Stormglass and AISStream need user-supplied API keys; keyed tools only appear when the key is present · AISStream is community-fed and sparse mid-ocean · Some bridges may show '(name unknown)' where OSM has no nearby named bridge · All tool times are UTC · Depends on third-party public endpoints (RWS, NDW, OSM/Overpass, aviationweather.gov, Open-Meteo) with no stated SLA · No public hosted endpoint is documented; the user must run or host an instance (docs use a 'your-host' placeholder) · ENTRY metadata lists OAuth, but DOCS describe API-key URL parameters and state 'No OAuth required' for Claude.ai · Likely single-maintainer personal project ('Built by @ai_kulikov'), so maintenance risk

climate environment hydrology civils-bim

Some details auto-extracted · unverified

Globalhealthy

mcp

73/100Currency A

tideways-mcp-server ↗

tideways-mcp-server

What's in it

Data offered llm-inferred: application performance totals: requests, errors and p95 response time · per-transaction timeline and response-time histogram · application issues: errors, slow SQL, deprecations, warnings, notices · individual slow request traces · day, week and month history reports · configuration and code bottleneck observations (e.g. N+1 queries)
Coverage docs-verified: up to 30 days (performance windows within the last ~30 days)
Resolution docs-verified: 15-minute buckets (performance summary)
Formats docs-verified: MCP stdio
Access docs-verified: Tideways API token required (scopes: metrics, traces, errors), so a Tideways account is needed; read-only (GET only); licence MIT

Useful for

Use cases llm-inferred: Diagnose why a client's web application or portal was slow in a given window, using Tideways performance data · Triage errors and slow SQL in a client-hosted web app during handover or post-release review · Check a client web platform's request volume and p95 response times across a project's services
Audience llm-inferred: web application developers · DevOps and site reliability engineers maintaining Tideways-monitored applications

Limitations

Constraints llm-inferred: Not an environmental, hydrological, water or civils data source; it is application performance monitoring for web apps, so the 'environment' category in the entry does not match its content · Unofficial, community-maintained server, not affiliated with or supported by Tideways · Requires a Tideways account and API token; the token must have the metrics, traces and errors scopes · Rate limit is per Tideways organisation per clock hour and is shared by all of its tokens and projects; its size depends on the plan · History is available for production and the default service only · Issues are returned 10 per page · Performance data covers roughly the last 30 days · All times are UTC · Requires Node.js 22+ or Docker to run

environment hydrology

Some details auto-extracted · unverified

Globalhealthy

skill

73/100Currency A

vellum ↗

The living surface — a shared ocean where AI agents leave short thoughts and weave lineages. MCP + REST, open to any agent. https://vellum.linxule.com/for-ai.txt

What's in it

Data offered docs-verified: short AI-agent text fragments ('voices') flowing in six thematic currents: attention, silence, space, ephemeral, memory, light · lineage trees of voices woven forward from other voices
Formats docs-verified: MCP streamable HTTP · REST/HTTP JSON endpoints
Access docs-verified: Free and open: no account or API key required; MIT licence

Useful for

Use cases llm-inferred: Testing MCP streamable-HTTP client configuration against a live public server before wiring similar tools into a project · Evaluating agent-to-agent write and lineage APIs for a internal prototype (not a source of environmental or water data) · Reference example of an open MCP server with self-correcting error responses and rate-limited REST endpoints
Audience llm-inferred: MCP and AI agent developers · AI tooling evaluators

Limitations

Constraints llm-inferred: Not environmental, hydrological, geospatial or civils data; it is a public shared text space and nothing published to it is private · No geographic or temporal coverage or update schedule; regions 'Global' in the entry is not a data coverage statement · Rate-limited per IP; session limits of 7 imprints, 5 weaves and 15 witnesses; per-agent limits of 12 imprints and 20 weaves per hour · Entry kind is 'skill' but the project is an MCP server plus REST API; the tools array is empty in the entry metadata · Community-launched crypto tokens are referenced in the docs and are unrelated to the data or access model

environment hydrology

Some details auto-extracted · unverified

Globalhealthy

mcp

72/100Currency A

Swiss Environment MCP ↗

MCP server for Swiss environmental data – air quality (NABEL), hydrology, natural hazards (BAFU)

What's in it

Data offered docs-verified: NABEL air quality: NO2, O3, PM10, PM2.5, SO2, CO per station (16 stations) · Hydrological gauging: water level, flow rate, temperature · Flood warnings filtered by danger level · Bathing water quality (E. coli, enterococci), multi-year series · Natural hazard bulletin (SLF/BAFU), DE/FR/IT/EN · Wildfire danger index by canton and region · Snow depth (HS) and 24 h new snow (HN_1D) per SLF/IMIS station · Avalanche danger levels (EAWS 1–5) per warning region · Federal hunting statistics per species, canton and year · BAFU dataset catalogue search and metadata (opendata.swiss, CKAN) · Aircraft noise exposure (dB bracket) at LV95 point; airfield noise cadastre register · Swiss LRV and WHO 2021 air limit checks; LSV noise limit checks
Coverage docs-verified: Switzerland · Hunting statistics 2015–2024; hydrology history queries capped at 30 days
Formats docs-verified: MCP stdio · MCP streamable HTTP · MCP SSE
Access docs-verified: Free, no API key or authentication required (all endpoints public). Data under BAFU Open Government Data licence (free reuse with mandatory attribution). Server code MIT.

Useful for

Use cases llm-inferred: Hydrology baseline from nearest Swiss gauging station (levels, flows) for water-resource projects · Air quality baseline check against Swiss LRV and WHO 2021 limits for EIA screening · Aircraft noise screening of planning sites using LV95 coordinates · Natural hazard screening (flood, avalanche, wildfire) in site due diligence
Audience llm-inferred: hydrologists · environmental consultants · planners · GIS analysts

Limitations

Constraints docs-verified: Swiss data only; not applicable to UK sites · Hydro station search has no canton filter; flood warnings are nationwide with no canton filter · env_hydro_history returns latest value plus an access path for real-time series, not full series · Aircraft noise contours are isolines: results are a dB bracket/upper bound, orientation aid only, not legally binding · Coordinates must be LV95 (EPSG:2056); WGS84 input is rejected · Hazard overview/regions tools are routers only; the naturgefahren.ch aggregate API was discontinued · Per-query caps apply and each API call times out after 30 seconds · Subject to upstream terms of service (BAFU, hydrodaten.admin.ch, naturgefahren.ch, waldbrandgefahr.ch) · Requires Python 3.11+ for local install · Tool budget is declared exhausted (21 tools); metadata lists tools as empty

environment hydrology

Some details auto-extracted · unverified

Switzerlandhealthy

mcp

72/100Currency A

USGS Water MCP ↗

Query real-time and historical water data from ~8,000 USGS stream gages and groundwater wells via MCP. STDIO or Streamable HTTP.

What's in it

Data offered docs-verified: real-time instantaneous values (~15 min) for up to 100 sites · daily and instantaneous time series over a date range · current conditions ranked against period-of-record percentiles · site discovery by bounding box, state, county or HUC · site metadata (drainage area, altitude, HUC, coordinates) · groundwater depth to water level (parameter 72019) · discharge (00060) and gage height (00065) parameter codes · USGS parameter code catalog (~19,600 codes)
Coverage docs-verified: United States and territories
Resolution docs-verified: Temporal: ~15 min for instantaneous values; one value per day for daily series
Update frequency docs-verified: ~15 min real-time for instantaneous readings
Formats docs-verified: MCP JSON (structuredContent) · markdown (rendered tool text) · application/json (resources) · DuckDB table (DataCanvas spillover) · MCP stdio · MCP streamable HTTP
Access docs-verified: Free and public; no API key required. Licence: Apache-2.0. Self-hosting needs a local install (bunx, npx or Docker); a public hosted endpoint is also listed.

Useful for

Use cases llm-inferred: FRA baseline flows from nearest gauge: find sites by bbox, then pull daily mean discharge (00060) for the baseline period · Current conditions check at gauges during a flood or drought review, using percentile ranking as indicative only · Groundwater depth baseline from monitoring wells via parameter 72019 · Monitoring site inventory for a catchment by HUC code, filtered to sites with instantaneous data
Audience llm-inferred: hydrologists · flood risk consultants · drainage engineers · GIS analysts · ecologists (groundwater and surface water baselines)

Limitations

Constraints llm-inferred: Covers US and territories only; no UK data · Percentile ranking is approximate and is not a flood-stage or drought determination · Readings return up to 100 sites per call, with at most 100 series and the 10 most recent records per series · Series inline output is capped at 500 records; larger results need CANVAS_PROVIDER_TYPE=duckdb · Dataframe tools and spillover require CANVAS_PROVIDER_TYPE=duckdb; table drop is opt-in via WATER_DATAFRAME_DROP_ENABLED · Pre-1.0 release (v0.3.0), so the interface may change · Relies on the USGS NWIS service being available; upstream failures are returned as retryable errors · Public hosted endpoint is not operated by USGS and has no stated uptime guarantee

hydrology

Some details auto-extracted · unverified

United Stateshealthy

mcp

72/100Currency A

ocean-agent ↗

Tell your AI to trade. MCP server + autonomous bot for Pacifica perpetual futures.

environment hydrology

Some details auto-extracted · unverified

Globalhealthy

Browse all 167 sources →