# GeoLens (pypi · geolens-mcp)

Read-only access to a self-hosted GeoLens spatial catalog: datasets, features, maps, sandboxed SQL.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `geolens-mcp`: 79/100 (this document), [markdown](https://verifymcp.io/servers/geolens-io-geolens/geolens-mcp.md), [page](https://verifymcp.io/servers/geolens-io-geolens/geolens-mcp)

## Channel facts

- Registry: `pypi`
- Package: `geolens-mcp`
- Version: `1.20.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 1 of 35 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1067 tokens (~177/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the GeoLens MCP server?

GeoLens runs locally as a PyPI package, launched with uvx geolens-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add geolens-io-geolens -- uvx geolens-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "geolens-io-geolens": {
      "command": "uvx",
      "args": [
        "geolens-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "geolens-io-geolens": {
      "command": "uvx",
      "args": [
        "geolens-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add geolens-io-geolens -- uvx geolens-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "geolens-io-geolens": {
      "type": "local",
      "command": [
        "uvx",
        "geolens-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add geolens-io-geolens --command uvx --arg geolens-mcp
```

### Hermes

```yaml
mcp_servers:
  geolens-io-geolens:
    command: "uvx"
    args: ["geolens-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "geolens-io-geolens": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "geolens-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add geolens-io-geolens -t stdio -c uvx -a geolens-mcp
```

### Other

```json
{
  "mcpServers": {
    "geolens-io-geolens": {
      "command": "uvx",
      "args": [
        "geolens-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 79, +39)

- [security improvement] Injection markers: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.90

### 2026-09-18 (score 40, −38)

- [security regression] Stability: 0.83 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] Package version: 1.19.1 → 1.20.0

### 2026-09-16 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 77, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 62, −14)

- [security regression] Malware scan: pass → unverified

### 2026-09-13 (score 76, +36)

- [security improvement] Injection markers: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.70

### 2026-09-12 (score 40, −35)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.63 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] Package version: 1.19.0 → 1.19.1

### 2026-09-10 (score 75, +1)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.57 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] Package version: 1.18.1 → 1.19.0

## MCP tools (6)

### `search_datasets` (~278 tokens)

Search the GeoLens catalog for datasets by free text.

Matches title, description, and keywords (semantic ranking is used
automatically when the instance has it enabled). Returns a GeoJSON
FeatureCollection where each feature is a dataset record; use the feature
\`id` as the dataset_id for the other tools. Each feature's properties include
\`source_origin` (upload, postgis, service, stac, created, or null) and
\`source_freshness` (fresh, due, overdue, or unknown). Freshness is advisory:
\`due` means one declared update interval has elapsed, while `overdue` means
two have elapsed; neither proves that the content is wrong.

Search does not make a detail request per result. When the catalog summary
has no health/check/refresh value, `source_health`, `source_health_detail`,
\`last_checked_at`, and `last_refreshed_at` are null. Call
\`get_dataset_schema` for populated trust metadata. Raw provider URLs and
credentials are never included in these source-state fields.

Args:
    query: Search text.
    limit: Max results (1-200, default 10).
    offset: Result offset for paging.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `query` (string, required)

### `get_dataset_schema` (~217 tokens)

Get a dataset's schema and source trust metadata.

Returns columns (name/type/role), geometry type, CRS/SRID, feature count,
spatial extent, and the safe `source_origin`. `source_health` is healthy,
missing, inaccessible, or unknown: inaccessible means GeoLens could not
determine whether the source still exists, while unknown means it was never
probed or cannot be probed. `source_health_detail` is a fixed GeoLens reason
code, not provider text. `last_checked_at` records the latest probe attempt;
\`last_refreshed_at` records only the latest successful committed refresh.
\`source_freshness` is advisory; overdue means two declared update intervals
elapsed without a successful refresh. Raw provider URLs, origin pointers,
and credentials are excluded. Call this before writing spatial questions so
you know both the available columns and whether the source may be stale.

Args:
    dataset_id: Dataset id (e.g. from search_datasets).

Input parameters:

- `dataset_id` (string, required)

### `get_features` (~129 tokens)

Get GeoJSON features for a dataset (bounded).

Returns an OGC-API FeatureCollection. Raster datasets have no features and
will error. Results are capped by `limit`; page with `offset`.

Args:
    dataset_id: Dataset id.
    limit: Max features (1-200, default 10).
    offset: Feature offset for paging.
    bbox: Optional bounding box filter "minx,miny,maxx,maxy" (WGS84).

Input parameters:

- `bbox`
- `dataset_id` (string, required)
- `limit` (integer)
- `offset` (integer)

### `list_maps` (~80 tokens)

List saved maps (read-only metadata: id, name, visibility, layer count).

Args:
    search: Optional text filter on map name/description.
    limit: Max results (1-200, default 50).
    offset: Result offset for paging.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `search`

### `get_map` (~54 tokens)

Get one saved map's full metadata, including its layers, view state,
basemap, and terrain configuration.

Args:
    map_id: Map id (e.g. from list_maps).

Input parameters:

- `map_id` (string, required)

### `query` (~309 tokens)

Run one read-only SQL SELECT against accessible datasets.

Executes through the server's hardened SQL sandbox: a single SELECT over
\`data.*` tables, an allowlisted function set (aggregates, math, string,
date, JSON, common PostGIS like ST_Area/ST_DWithin/ST_Intersects), and a
strict server-side budget (a few seconds of runtime, a repetition cap on
self-joins, and `row_limit` rows). Returns `{columns, rows, row_count,
truncated}` with rows as lists in column order.

Requires credentials with AI-chat permission — anonymous configurations
cannot use this tool. Workflow: `search_datasets` to find a dataset, then
\`get_dataset_schema` for its `table_name` and columns, then reference it
as `data.<table_name>` in the SQL and list the same `table_name` in
\`restrict_tables`. Every table the query touches must be listed there;
the scope can only narrow what your credentials already see. Writes,
other schemas, and unlisted functions are rejected with a short reason.

Args:
    sql: A single SELECT statement over `data.*` tables.
    restrict_tables: Table names (no `data.` prefix) the query may touch.
        Required and non-empty.
    row_limit: Max rows to return (1-1000, default 100).

Input parameters:

- `restrict_tables` (array, required)
- `row_limit` (integer)
- `sql` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/geolens-io-geolens/geolens-mcp#diagnostics

## Score history

- 2026-09-20: 79
- 2026-09-19: 79
- 2026-09-18: 40
- 2026-09-17: 78
- 2026-09-16: 78
- 2026-09-15: 77
- 2026-09-14: 62
- 2026-09-13: 76
- 2026-09-12: 40
- 2026-09-11: 75
- 2026-09-10: 75
- 2026-09-09: 74
- 2026-09-08: 74
- 2026-09-07: 73
- 2026-09-06: 73
- 2026-09-05: 72
- 2026-09-04: 72
- 2026-09-03: 71
- 2026-09-02: 71
- 2026-09-01: 71
- 2026-08-31: 70
- 2026-08-30: 70
- 2026-08-29: 69
- 2026-08-28: 40
- 2026-08-27: 53
- 2026-08-26: 68
- 2026-08-25: 65
- 2026-08-24: 64
- 2026-08-23: 49

## Common questions

### What is the GeoLens MCP server?

GeoLens is an MCP server listed in the public MCP registry as io.github.geolens-io/geolens. Read-only access to a self-hosted GeoLens spatial catalog: datasets, features, maps, sandboxed SQL. This page covers its PyPI package (geolens-mcp).

### Is the GeoLens MCP server safe to use?

GeoLens scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the GeoLens MCP server expose?

GeoLens exposes 6 tools: search_datasets, get_dataset_schema, get_features, list_maps, get_map, query. Their descriptions and schemas cost roughly 1,067 tokens of context every time the server is loaded.

### Is the GeoLens MCP server still maintained?

GeoLens is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the GeoLens MCP server under?

GeoLens declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/geolens-mcp/
- Socket report: https://socket.dev/pypi/package/geolens-mcp
- Repository: https://github.com/geolens-io/geolens
- Website: https://docs.getgeolens.com/
- Changelog RSS feed: https://verifymcp.io/servers/geolens-io-geolens/geolens-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/geolens-io-geolens/geolens-mcp.json
- HTML version of this page: https://verifymcp.io/servers/geolens-io-geolens/geolens-mcp