Skip to main content
Glama
si-essence

hazardwatch-mcp

by si-essence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to hazardwatch-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-nasa-eonet

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying NASA's Earth Observatory Natural Event Tracker (EONET) for natural events, categories, sources, and visualization layers.
      9 npm
      MIT

    • mcp-gdacs

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying global disaster alerts from GDACS including earthquakes, tropical cyclones, floods, volcanoes, droughts, and wildfires. Supports listing events, getting details, and retrieving GeoJSON or RSS feeds.
      14 npm
      MIT

    • earth-search

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying Sentinel-1/2, Landsat Collection 2, NAIP, and Copernicus DEM imagery by area and date, returning item IDs, footprints, cloud cover, and cloud-optimized GeoTIFF URLs.
      0
      MIT

    • @pipeworx/mcp-nasa-gibs

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching NASA GIBS' 1,300+ satellite imagery layers, retrieving detailed layer metadata, and generating tile URLs for any date and location, covering datasets like true-color mosaics, thermal anomalies, and night lights.
      8 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct resource or filter: point/bbox fires, country fires, EONET list, EONET by id, categories, and the composite proximity view. The main soft spot is nearby_hazards, which overlaps conceptually with fires_near plus eonet_events, though its documented combined/limited semantics make it distinguishable.

    Naming Consistency4/5

    All snake_case with a domain-prefix convention (fires_*, eonet_*) plus a domain-less composite nearby_hazards. The pattern is readable and predictable, with the singular/plural eonet_event vs eonet_events pair being the only slight wrinkle.

    Tool Count5/5

    Six tools is well-scoped for a hazard-watch server, and each earns its place by covering a distinct query shape (point, bbox, country, event list, event detail, categories, combined proximity).

    Completeness4/5

    Covers the core lifecycle of both upstream sources plus a convenience composite, with sensible FIRMS-key fallback behavior. The notable gap is fires_by_country, which is documented as broken upstream (a dead end) and there is no alternate country-level path or source-selection tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources