Off-Nadir Delta
OfficialRelated Servers
Alternatives to Off-Nadir Delta
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for real-time global intelligence, AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking, enabling agents and scripts to access curated news feeds, country instability indices, and market data.90,631AGPL 3.0
- AlicenseCqualityDmaintenanceMCP server for the Geopera geospatial data platform that enables AI agents to discover imagery, place and manage orders, and run analytics using the same API as other Geopera clients.100MIT
- AlicenseNot gradedqualityDmaintenanceProduction-grade MCP server wrapping SkyFi's satellite imagery platform API. Enables AI agents to conversationally search, price, order, and monitor satellite imagery through the Model Context Protocol.MIT
- AlicenseNot gradedqualityBmaintenanceA standalone Model Context Protocol server that lets AI clients search satellite scenes, fetch weather and climate series, query geographic layers, and compute vegetation indices and gradual-pattern analyses over environmental time series, returning structured results with source and limit metadata. It exposes 16 tools over stdio, streamable HTTP or legacy SSE and runs its own data retrieval and calculations.1MIT
- FlicenseBqualityDmaintenanceA Python MCP server for discovering and analyzing Sentinel-2 L2A imagery, enabling AI agents to search scenes, check quality, and compute spectral indices like NDVI, NDWI, and NBR from remote COG windows.4-
- AlicenseAqualityCmaintenanceEnables MCP clients such as Claude, Codex, Cursor, and OpenCode to search and retrieve news articles and clustered real-world events from roughly 150,000 sources worldwide, with tools for keyword/concept/location/date filtering, full-text lookup by URI or URL, entity name-to-URI resolution, token usage checks, and raw access to any newsapi.ai API endpoint. Results are returned as compact JSON to conserve context, and both local stdio and remote HTTP deployment are supported.7MIT
TDQS
Scored across 20 tools
Most tools have clearly distinct purposes across signal querying, imagery planning, analyst Q&A, and monitoring. A few adjacent tools (e.g., plan_event_imagery vs search_imagery, rank_imaging_priority vs survey_observable_events) require careful reading of descriptions, but the boundaries are explicit enough to avoid gross misselection.
All tool names follow a consistent verb_noun snake_case pattern (get_, query_, create_, delete_, list_, plan_, rank_, survey_, predict_, assess_, ask_), with no camelCase or mixed conventions.
At 20 tools, the server is broad in scope but the count is on the heavy side. Each tool serves a distinct function, but the overall surface feels dense compared to a typical well-scoped server (3-15 tools). No redundancy, but the large number increases cognitive load.
The server covers core workflows well, but lifecycle coverage is incomplete: monitored areas have create/list/get but no delete or update, and standing orders lack a true update (only pause/resume via delete_standing_order). This creates dead ends for users wanting to modify or remove monitoring. Signal querying and imagery planning are thorough.