GeoLens vs Offnadir Delta MCP
A side-by-side look at the GeoLens and Offnadir Delta MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose GeoLens for location services work; choose Offnadir Delta MCP for location services as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Offnadir Delta MCP when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
OFFNADIR_DELTA_API_KEY. - You want tools like
query_signals, query_stats, query_hotspots.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Location Services | Location Services |
| Quality signal | 37/100 · Fair | 64/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Free | Freemium |
| Required env vars | None listed | OFFNADIR_DELTA_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 278 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 40 |
| Full listing | View GeoLens | View Offnadir Delta MCP |
Tools & capabilities
GeoLens tools
No tool names declared yet. Check the project README from the listing page.
Offnadir Delta MCP tools 40
query_signalsGeolocated world events from global news media, AI-enriched with severity/GEOINT scores and collection recommendations.query_statsRoll-ups over the corpus: totals plus per-category and per-day breakdown. `total` counts the same events query_signals returns, so it matches its meta.total_count for the same query.query_hotspotsWhere activity concentrates: density grid-binned into ranked cells with peak severity, categories and representative event_ids. Events too coarse to place are counted in meta.dropped_by_plottable_count, not spread over the grid.get_world_briefAI world brief: daily (prior UTC day, all plans) or weekly/monthly by plan. freshness.is_stale: no newer day, so relay as stale.get_usageThe calling key's remaining token balance and plan capabilities. Pre-flight a metered call with it.search_imagerySearch the imagery catalog over an area and window. Metadata only, no pixels. eventDate tags each scene pre/post — **a same-day scene is same_day_unknown, never post** — and eventPoint/eventAoi add target_relation, so a scene that only clips the bbox is not read as covering the event.plan_event_imageryThe deterministic imagery plan for ONE event: checks BOTH sensors exactly once — sentinel-1-grd (SAR, the only look that survives cloud and night) and sentinel-2-l2a — against the event footprint and a pre/post window. **A VHR recommendation never invalidates what the free catalog showed.**rank_imaging_priorityWHERE, and with what class of satellite, observation is most worthwhile now: composite IMPORTANCE crossed with the SPEC CLASS the required resolution demands — coarse, hr (free Sentinel-class) or vhr. Deterministic.survey_observable_eventsWhich events a sensor can actually RESOLVE, over the FULL set. **The population is ungated by tasking readiness**, so its total sits above rank_imaging_priority and counts a different unit from query_signals clusters.predict_satellite_passesWHEN a place can next be imaged and by WHAT: 13 free-systematic and commercial-taskable families. **Every pass is a GEOMETRIC access opportunity** — no operator plan is consulted. retrieval_ok:false means timing is UNAVAILABLE, never "no passes".assess_signalAI remote-sensing deep-dive for one signal: what to observe, sensors, a collection window. Also returns a deterministic `context` whose `imagery_handoff.parameters` are the exact search_imagery inputs. Cached per signal; not-observable signals are rejected before any charge.ask_analystAsk the Delta Analyst an OSINT/GEOINT question; returns a structured brief. **Durable async**: {status:"processing", job_id} comes back immediately and the run finishes in a background worker. Fetch with get_analyst_job, or re-send the SAME idempotencyKey (no second charge).- +28 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
GeoLens
No confirmed install command for GeoLens yet — follow the setup steps linked from its listing page rather than a guessed package name.
Offnadir Delta MCP
{
"mcpServers": {
"off-nadir-lab-offnadir-delta-mcp": {
"command": "npx",
"args": [
"-y",
"offnadir-delta-mcp"
],
"env": {
"OFFNADIR_DELTA_API_KEY": "YOUR_OFFNADIR_DELTA_API_KEY_HERE"
}
}
}
}
Frequently asked questions
GeoLens is categorized under Location Services and uses an install path we have not confirmed yet. Offnadir Delta MCP belongs to Location Services and uses a local stdio subprocess. Pick GeoLens for location services work and Offnadir Delta MCP for location services.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. GeoLens has no confirmed install command yet — follow its own setup instructions.
GeoLens is listed as free. Offnadir Delta MCP is listed as freemium — a free tier with paid plans. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add geolens and off-nadir-lab-offnadir-delta-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, GeoLens has a quality signal of 37/100 (Fair) with 2 views, 0 installs and 278 GitHub stars. Offnadir Delta MCP has 64/100 (Good) with 4 views, 0 installs and 0 GitHub stars.