jaxa-earth-mcp
Related Servers
Alternatives to jaxa-earth-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables retrieval of satellite vegetation statistics (NDVI) and searches of Sentinel-2 scene catalogs, returning results as JSON.71 npmMIT
- AlicenseAqualityCmaintenanceGives AI assistants read-only, key-free access to Sentinel-2 NDVI time series, ESA WorldCover land-cover shares, and Copernicus 30 m elevation and slope for a point or small area, returning the scene IDs, units, and caveats behind every number. Built-in sanity checks and a verify tool recompute key values through an independent path so the assistant can flag cloudy, low-confidence, or mismatched results instead of guessing.6MIT
- AlicenseAqualityBmaintenanceIt enables AI agents to search public STAC catalogs and compute Sentinel-2 NDVI, NDWI, and NBR statistics over a bounding box without downloading whole images, with cloud masking and optional map or GeoTIFF outputs.533 PyPIMIT
- -licenseNot gradedqualityNot gradedmaintenanceEnables satellite imagery analysis through Google Earth Engine, allowing users to search datasets, calculate vegetation indices like NDVI, filter collections by location and date, and export imagery to cloud storage. Supports major satellite datasets including Sentinel-2, Landsat, and MODIS for applications like agriculture monitoring and deforestation tracking.-
- AlicenseNot gradedqualityBmaintenanceEnables querying U.S. Drought Monitor weekly statistics — severity, DSCI, population, and drought duration — across national, state, county, HUC watershed, tribal, and climate-division areas. Supports area comparison, timeseries retrieval, drought-week counting, and read-only SQL analysis over staged datasets, with no API key required.123 npm2Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProduction-ready satellite imagery analysis server that enables natural language queries for Earth observation data, including land cover classification, vegetation monitoring, water detection, change detection, and automated environmental reporting.MIT
TDQS
Scored across 3 tools
Each tool targets a clearly distinct operation: a single-month anomaly versus same-month normal, a multi-month observed time series, and a collection-ID search. The names and descriptions make the boundary between the two NDVI tools explicit (single month anomaly vs. inclusive range of observations). No realistic risk of misselection.
All three follow a consistent snake_case verb_noun pattern (get_ndvi_anomaly, get_ndvi_time_series, search_collections). The get_ndvi_* prefix groups the related NDVI tools predictably, and the shared parameter conventions (YYYY-MM, WGS84 bbox) reinforce coherence.
Three tools is thin for a server whose apparent purpose is JAXA Earth data access; the surface covers NDVI statistics and collection discovery only. Each tool is justified, but the server feels narrowly scoped rather than well-rounded.
The NDVI workflow has a reasonable lifecycle (discover collection, get anomaly, get time series), but there is no access to other JAXA products or indices, no raster/imagery retrieval, and no point- or region-summary tools beyond bbox NDVI stats. Notable gaps, though the stated NDVI use case is workable.