Geolens vs Offnadir Delta MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Geolens vs Offnadir Delta MCP
In-depth architectural comparison of the Geolens and Offnadir Delta MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Geolens
Location Services · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Offnadir Delta MCP
Location Services · Local stdio
Quality: 63/100 (Good) | Auth: other
Verdict Summary: Choose Geolens if you need specialized Location Services tools running via a local process. Choose Offnadir Delta MCP if your workspace requires Location Services integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Geolens when:
You need dedicated capabilities in the Location Services domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Read-only access to a self-hosted GeoLens geospatial catalog: dataset search, schemas, GeoJSON features, saved maps, and sandboxed read-only SQL over PostGIS.
Live, geolocated world-event intelligence and a Daily World Brief for AI agents — query event signals (coordinates, severity, sources), hotspots, and satellite imagery (Sentinel-1/2 etc), plus an OSINT/GEOINT analyst. Streamable HTTP + OAuth; free tier, token-metered.
Category & Scope
Tools & Capabilities Breakdown
Geolens Tools (5)
Dataset catalog search
Schema inspection
GeoJSON feature retrieval
Saved-map access
Sandboxed read-only PostGIS SQL
Offnadir Delta MCP Tools (40)
query_signals
Geolocated world events from global news media, AI-enriched with severity/GEOINT scores and collection recommendations.
query_stats
Roll-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.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Geolens is categorized under Location Services and uses a local stdio subprocess. In contrast, Offnadir Delta MCP belongs to Location Services using local stdio subprocess. Select Geolens when you need capabilities focused on location services and Offnadir Delta MCP when you require tools for location services.
Where 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_brief
AI world brief: daily (prior UTC day, all plans) or weekly/monthly by plan. freshness.is_stale: no newer day, so relay as stale.
get_usage
The calling key's remaining token balance and plan capabilities. Pre-flight a metered call with it.
search_imagery
Search 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_imagery
The 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_priority
WHERE, 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_events
Which 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_passes
WHEN 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_signal
AI 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_analyst
Ask 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).