offnadir-delta-mcp 1.8.3 → 1.12.0

package/README.md

@@ -16,7 +16,7 @@ satellite can actually resolve it, and produce a collection-ready plan.
 Real-time event and geospatial intelligence for OSINT, geopolitical risk, and GEOINT work —
 source-linked, geolocated, and current, not a training snapshot.
 
-`20` tools · MCP server version `1.8.3` · [full reference](https://offnadir-delta.com/docs/mcp)
+`25` tools · MCP server version `1.12.0` · [full reference](https://offnadir-delta.com/docs/mcp)
 
 ## What it does
 
@@ -77,7 +77,7 @@ locally from a generated catalog, so registries can introspect it without creden
 
 ### First call — free
 
-10 of the 20 tools cost nothing, so the first thing you run is free:
+12 of the 25 tools cost nothing, so the first thing you run is free:
 
 > Give me the latest Daily World Brief. Lead with the three most significant developments,
 > explain why each matters, and cite the supporting signals.
@@ -111,6 +111,8 @@ Whether a satellite can resolve it, which one, and when it next passes.
 | `rank_imaging_priority` | WHERE — and with what class (and therefore cost) of satellite — is observation most worthwhile right now? | 1 tok |
 | `survey_observable_events` | Which events in a window can a given in-app sensor actually RESOLVE? | 1 tok |
 | `predict_satellite_passes` | WHEN can this place next be imaged, and by WHAT — the timing half of collection planning. | 2 tok |
+| `lookup_elevation` | Measure terrain height from the Copernicus DEM GLO-30 — a point (lat + lon), an area (bbox), or a drawn polygon, for which the statistics are computed over the samples INSIDE the ring rather than its bounding box. | free |
+| `analyze_terrain` | Compute FROM the terrain rather than reading heights out of it (that is lookup_elevation). | free |
 
 ### Analyze
 
@@ -122,6 +124,9 @@ Turn reporting into a cited assessment you can audit afterwards.
 | `ask_analyst` | Ask the Delta Analyst an OSINT/GEOINT question. | 5–123 tok |
 | `get_analyst_job` | Fetch the status and result of an ask_analyst run by job_id. | free |
 | `query_claims` | Read the LEDGER of claims this key has been given — every factual assertion the Analyst made, with its evidence class (CONFIRMED / REPORTED / PARTY_CLAIM / ASSESSMENT), how many INDEPENDENT source families backed it, and the publishers. | free |
+| `refine_location` | Research one signal's location further and, if the sources genuinely narrow it, store and return the better coordinate. | 3–29 tok |
+| `measure_index_series` | Measure a spectral index over an area, scene by scene, back through the Sentinel-2 archive — the answer to "how has this changed since <year>". | 0.5 tok |
+| `detect_ships` | Count vessel-like targets in ONE SAR scene over an area, using CFAR detection on Sentinel-1. | 5 tok |
 
 ### Watch
 

package/dist/catalog.js

@@ -13,7 +13,7 @@
  * Actual `tools/call` / `resources/read` / `prompts/get` requests are forwarded
  * to the remote server with the caller's OFFNADIR_DELTA_API_KEY (see index.ts).
  */
-// Generated for Off-Nadir Delta MCP 1.8.3.
+// Generated for Off-Nadir Delta MCP 1.12.0.
 export const TOOLS = [
     {
         "name": "query_signals",
@@ -1510,6 +1510,388 @@ export const TOOLS = [
             "openWorldHint": false,
             "destructiveHint": false
         }
+    },
+    {
+        "name": "lookup_elevation",
+        "description": "Measure terrain height from the Copernicus DEM GLO-30 — a point (lat + lon), an area (bbox), or a drawn polygon, for which the statistics are computed over the samples INSIDE the ring rather than its bounding box. Returns min, max, mean, median, p10, p90 and relief (max − min), the number that governs SAR layover and shadow severity. Free of token charges. Three things the result carries that any answer must respect: it is a SURFACE model (buildings and tree canopy included, so not bare ground); `downsampled: true` means a large area was read below the 30 m posting, so min/max are smoothed inward and the relief is a floor rather than an exact figure; and `covered: false` or `tiles_missing > 0` means open ocean where the model has no data — which is absence, not 0 m. Heights are orthometric on the EGM2008 geoid, not ellipsoidal. Cite the returned `attribution` wherever a height is shown.",
+        "inputSchema": {
+            "type": "object",
+            "properties": {
+                "lat": {
+                    "type": "number",
+                    "minimum": -90,
+                    "maximum": 90,
+                    "description": "Latitude of a single point to measure (use with lon)."
+                },
+                "lon": {
+                    "type": "number",
+                    "minimum": -180,
+                    "maximum": 180,
+                    "description": "Longitude of a single point to measure (use with lat)."
+                },
+                "bbox": {
+                    "type": "array",
+                    "items": {
+                        "type": "number"
+                    },
+                    "minItems": 4,
+                    "maxItems": 4,
+                    "description": "Area to measure as [lon_min, lat_min, lon_max, lat_max] (WGS84)."
+                },
+                "polygon": {
+                    "type": "array",
+                    "items": {
+                        "type": "array",
+                        "items": {
+                            "type": "number"
+                        },
+                        "minItems": 2,
+                        "maxItems": 2
+                    },
+                    "minItems": 3,
+                    "description": "WGS84 ring [[lon, lat], …]. Statistics cover only the samples inside it."
+                }
+            }
+        },
+        "outputSchema": {
+            "type": "object",
+            "properties": {
+                "mode": {
+                    "type": "string",
+                    "description": "Which form was measured: 'point', 'bbox' or 'polygon'."
+                },
+                "elevation": {
+                    "type": "object"
+                },
+                "attribution": {
+                    "type": "string",
+                    "description": "Required Copernicus DEM credit (licence Article 6(b))."
+                }
+            },
+            "required": [
+                "elevation"
+            ]
+        },
+        "annotations": {
+            "readOnlyHint": true,
+            "openWorldHint": false,
+            "destructiveHint": false
+        }
+    },
+    {
+        "name": "analyze_terrain",
+        "description": "Compute FROM the terrain rather than reading heights out of it (that is lookup_elevation). Free of token charges; both operations come from one Copernicus DEM GLO-30 read. `operation: 'sar_geometry'` over a bbox, with an incidence angle and a look azimuth, returns the share of the area lost to LAYOVER and to SHADOW, the share merely foreshortened, and the mean LOCAL incidence angle — the arithmetic behind whether radar can use that ground. It changes with the pass direction (measured on one volcanic flank: 2.6% layover looking west against 0.7% looking east at the same 35°), so the geometry is required rather than assumed. `operation: 'profile'` between two points returns the ground along the line and a LINE-OF-SIGHT verdict including Earth curvature: whether the ends can see each other, where the terrain first rises above the sight line, and the worst clearance. Both results state the sample spacing they were computed at — a coarser grid reads flatter, and therefore more observable, than the ground is. A SURFACE model, so canopy and buildings are included; over a surface model they block a sight line as they would in reality. Cite the returned `attribution`.",
+        "inputSchema": {
+            "type": "object",
+            "required": [
+                "operation"
+            ],
+            "properties": {
+                "operation": {
+                    "type": "string",
+                    "enum": [
+                        "sar_geometry",
+                        "profile"
+                    ],
+                    "description": "'sar_geometry' = layover/shadow over an area; 'profile' = ground along a line plus a line-of-sight verdict."
+                },
+                "bbox": {
+                    "type": "array",
+                    "items": {
+                        "type": "number"
+                    },
+                    "minItems": 4,
+                    "maxItems": 4,
+                    "description": "For 'sar_geometry': area as [lon_min, lat_min, lon_max, lat_max] (WGS84)."
+                },
+                "incidence_deg": {
+                    "type": "number",
+                    "minimum": 10,
+                    "maximum": 80,
+                    "description": "For 'sar_geometry': sensor incidence angle. Sentinel-1 IW spans roughly 29-46 degrees; use the scene's own value when you have it."
+                },
+                "look_azimuth_deg": {
+                    "type": "number",
+                    "minimum": 0,
+                    "maximum": 360,
+                    "description": "For 'sar_geometry': compass bearing the sensor looks along the ground range. A right-looking descending pass looks roughly west (270)."
+                },
+                "lat": {
+                    "type": "number",
+                    "minimum": -90,
+                    "maximum": 90,
+                    "description": "For 'profile': latitude of the observer end."
+                },
+                "lon": {
+                    "type": "number",
+                    "minimum": -180,
+                    "maximum": 180,
+                    "description": "For 'profile': longitude of the observer end."
+                },
+                "to_lat": {
+                    "type": "number",
+                    "minimum": -90,
+                    "maximum": 90,
+                    "description": "For 'profile': latitude of the far end."
+                },
+                "to_lon": {
+                    "type": "number",
+                    "minimum": -180,
+                    "maximum": 180,
+                    "description": "For 'profile': longitude of the far end."
+                },
+                "observer_height_m": {
+                    "type": "number",
+                    "minimum": 0,
+                    "description": "For 'profile': eye height above the ground, default 2 m. Use the real mast or tower height when that is the question."
+                }
+            }
+        },
+        "outputSchema": {
+            "type": "object",
+            "properties": {
+                "operation": {
+                    "type": "string"
+                },
+                "sar_geometry": {
+                    "type": "object"
+                },
+                "profile": {
+                    "type": "object"
+                },
+                "attribution": {
+                    "type": "string",
+                    "description": "Required Copernicus DEM credit (licence Article 6(b))."
+                }
+            }
+        },
+        "annotations": {
+            "readOnlyHint": true,
+            "openWorldHint": false,
+            "destructiveHint": false
+        }
+    },
+    {
+        "name": "refine_location",
+        "description": "Research one signal's location further and, if the sources genuinely narrow it, store and return the better coordinate. Most signals are geolocated once, for free, from a single article's place string: measured across production, about two thirds sit at ±5 km or have no bounded radius at all. This reads the source article and live search for a source that names something finer — a facility, bridge, district, port — resolves it, and verifies it before accepting it. **You are charged only if the precision actually improves**, between 3 and 29 tokens by what the run consumed; a signal that cannot be narrowed costs nothing, and a signal an earlier caller already refined is returned free. Read the result honestly: `improved: false` with a `reason` is the common and correct outcome when no source is more specific — it does NOT mean the event is unlocated, and it is not a failure to retry. When it does improve, `evidence` lists the sources that named the place; a location without evidence is never stored, so do not present a refined point without citing them. `footprint_kind` says whether the answer is a POINT or an AREA — if it is an area, describe an area, because an admin-level place has no finite radius and drawing it as a dot misstates where the event was. `uncertainty_m: null` means unbounded, not unknown.",
+        "inputSchema": {
+            "type": "object",
+            "required": [
+                "signal_id"
+            ],
+            "properties": {
+                "signal_id": {
+                    "type": "integer",
+                    "description": "The signal (global_event_id) whose location should be researched further."
+                }
+            }
+        },
+        "outputSchema": {
+            "type": "object",
+            "properties": {
+                "summary": {
+                    "type": "string",
+                    "description": "One-line natural-language summary of the result, ready to relay to a user."
+                },
+                "result": {
+                    "type": "object"
+                },
+                "meta": {
+                    "type": "object",
+                    "description": "Query echo, token charge/balance (meta.tokens), and pagination where applicable."
+                }
+            }
+        },
+        "annotations": {
+            "readOnlyHint": false,
+            "openWorldHint": false,
+            "destructiveHint": true
+        }
+    },
+    {
+        "name": "measure_index_series",
+        "description": "Measure a spectral index over an area, scene by scene, back through the Sentinel-2 archive — the answer to \"how has this changed since <year>\". Give a polygon (or a bbox), an index (ndvi, evi, savi, ndmi, ndwi, mndwi, ndbi, ndsi, nbr, iron-oxide, clay, ferrous) and a date range; each scene is measured over the samples INSIDE the ring, and the result is the per-scene mean/median/min/max with a first-to-last change. Costs 0.5 tokens per scene actually measured; a scene that fails to read is reported in `skipped` and is not charged. **Call it once with `estimate_only: true` first** — that is free and returns how many scenes match, the real date span available, and what measuring them would cost, so the user can agree to the spend. Three things the result carries that any answer must respect: the Sentinel-2 archive begins 2015-06-27, so an earlier start is clamped and `clamped_to_archive` says so (those years are genuinely unavailable, not empty); at most 24 scenes are measured per call, so a longer period comes back as a SAMPLE and the rest appear in `skipped`; and `trend` compares the first and last measured scene only — it is not a fitted rate, so do not attach a slope or a confidence to it. `scenes_found` is what the catalog holds; `scenes_examined` is the newest page this call read, so `candidate_date_span` is the edge of that page and NOT how far the archive reaches — read `notes` before saying when coverage begins. For a SAR quantity, or to keep measuring as new imagery arrives, use create_monitored_area instead. Cite the returned `attribution`.",
+        "inputSchema": {
+            "type": "object",
+            "required": [
+                "index",
+                "start",
+                "end"
+            ],
+            "properties": {
+                "polygon": {
+                    "type": "array",
+                    "items": {
+                        "type": "array",
+                        "items": {
+                            "type": "number"
+                        }
+                    },
+                    "description": "WGS84 ring [[lon, lat], …] with at least 3 vertices. Statistics cover the samples inside it."
+                },
+                "bbox": {
+                    "type": "array",
+                    "items": {
+                        "type": "number"
+                    },
+                    "minItems": 4,
+                    "maxItems": 4,
+                    "description": "Alternative to polygon: [lon_min, lat_min, lon_max, lat_max] (WGS84)."
+                },
+                "index": {
+                    "type": "string",
+                    "enum": [
+                        "ndvi",
+                        "evi",
+                        "savi",
+                        "ndmi",
+                        "ndwi",
+                        "mndwi",
+                        "ndbi",
+                        "ndsi",
+                        "nbr",
+                        "iron-oxide",
+                        "clay",
+                        "ferrous"
+                    ],
+                    "description": "Which optical index to measure."
+                },
+                "start": {
+                    "type": "string",
+                    "description": "Start date YYYY-MM-DD (UTC). Clamped forward to 2015-06-27 if earlier."
+                },
+                "end": {
+                    "type": "string",
+                    "description": "End date YYYY-MM-DD (UTC)."
+                },
+                "max_scenes": {
+                    "type": "integer",
+                    "minimum": 1,
+                    "maximum": 24,
+                    "description": "Cap on scenes measured in this call. Server maximum 24."
+                },
+                "max_cloud_cover": {
+                    "type": "number",
+                    "minimum": 1,
+                    "maximum": 100,
+                    "description": "Scene cloud-cover ceiling in percent. Default 30."
+                },
+                "estimate_only": {
+                    "type": "boolean",
+                    "description": "True = free: return the scene count, date span and token cost WITHOUT measuring or charging."
+                }
+            }
+        },
+        "outputSchema": {
+            "type": "object",
+            "properties": {
+                "summary": {
+                    "type": "string",
+                    "description": "One-line natural-language summary of the result, ready to relay to a user."
+                },
+                "estimate": {
+                    "type": "object"
+                },
+                "series": {
+                    "type": "object"
+                },
+                "meta": {
+                    "type": "object",
+                    "description": "Query echo, token charge/balance (meta.tokens), and pagination where applicable."
+                },
+                "attribution": {
+                    "type": "string"
+                }
+            }
+        },
+        "annotations": {
+            "readOnlyHint": false,
+            "openWorldHint": false,
+            "destructiveHint": true
+        }
+    },
+    {
+        "name": "detect_ships",
+        "description": "Count vessel-like targets in ONE SAR scene over an area, using CFAR detection on Sentinel-1. Costs 5 tokens per detection; a scene the worker refuses (an unsupported combination, an area with no usable sea) is not charged. The natural sequence is search_imagery over the area, pick a scene, then this with its `collection` and `item_id` — radar sees through cloud and at night, so the count works when optical would not. Read `caveats` before reporting the number: it states when the land mask was unavailable (shoreline structures may be counted as vessels), how far from the coast detections were excluded (the default excludes vessels alongside a quay), and when the scene covers only part of the requested area — a partial-coverage count must never be compared with a full one as though the difference were vessels. This measures one scene at one time. To track a berth or an anchorage over time, create_monitored_area with metric `ships` measures every new acquisition.",
+        "inputSchema": {
+            "type": "object",
+            "required": [
+                "collection",
+                "item_id"
+            ],
+            "properties": {
+                "collection": {
+                    "type": "string",
+                    "enum": [
+                        "sentinel-1-grd",
+                        "sentinel-1-rtc"
+                    ],
+                    "description": "Catalog collection of the scene. NISAR detection is available in the app only (it needs a granule conversion first)."
+                },
+                "item_id": {
+                    "type": "string",
+                    "description": "STAC item id of the scene, as returned by search_imagery."
+                },
+                "bbox": {
+                    "type": "array",
+                    "items": {
+                        "type": "number"
+                    },
+                    "minItems": 4,
+                    "maxItems": 4,
+                    "description": "Area to search within the scene, [lon_min, lat_min, lon_max, lat_max] (WGS84)."
+                },
+                "geometry": {
+                    "type": "object"
+                },
+                "algorithm_version": {
+                    "type": "string",
+                    "enum": [
+                        "auto",
+                        "v2",
+                        "v3"
+                    ],
+                    "description": "Detector version. 'auto' (default) picks the recommended version for the sensor."
+                }
+            }
+        },
+        "outputSchema": {
+            "type": "object",
+            "properties": {
+                "summary": {
+                    "type": "string",
+                    "description": "One-line natural-language summary of the result, ready to relay to a user."
+                },
+                "count": {
+                    "type": "integer",
+                    "description": "Vessel-like targets detected. Read `caveats` before quoting it."
+                },
+                "ships": {
+                    "type": "object"
+                },
+                "caveats": {
+                    "type": "array",
+                    "items": {
+                        "type": "string"
+                    }
+                },
+                "scene": {
+                    "type": "object"
+                },
+                "processing": {
+                    "type": "object"
+                },
+                "meta": {
+                    "type": "object",
+                    "description": "Query echo, token charge/balance (meta.tokens), and pagination where applicable."
+                }
+            }
+        },
+        "annotations": {
+            "readOnlyHint": false,
+            "openWorldHint": false,
+            "destructiveHint": true
+        }
     }
 ];
 export const RESOURCES = [

package/dist/index.js

@@ -21,7 +21,7 @@ import { Client } from '@modelcontextprotocol/sdk/client/index.js';
 import { StreamableHTTPClientTransport } from '@modelcontextprotocol/sdk/client/streamableHttp.js';
 import { CallToolRequestSchema, GetPromptRequestSchema, ListPromptsRequestSchema, ListResourcesRequestSchema, ListResourceTemplatesRequestSchema, ListToolsRequestSchema, ReadResourceRequestSchema, } from '@modelcontextprotocol/sdk/types.js';
 import { PROMPTS, RESOURCES, RESOURCE_TEMPLATES, TOOLS } from './catalog.js';
-const VERSION = '1.8.3';
+const VERSION = '1.12.0';
 const REMOTE_URL = new URL(process.env.OFFNADIR_DELTA_MCP_URL ?? 'https://offnadir-delta.com/api/v1/mcp');
 /** Lazily-connected client to the hosted remote MCP server. */
 let remote = null;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "offnadir-delta-mcp",
-  "version": "1.8.3",
+  "version": "1.12.0",
   "description": "Local (stdio) MCP server for Off-Nadir Delta \u2014 live, geolocated world-event intelligence, a Daily World Brief, satellite-imagery search, and an OSINT/GEOINT analyst. Forwards to the hosted server with your API key.",
   "type": "module",
   "bin": {