ToolsMCP
GeoLens
Listed in the official MCP Registry with an installable pypi package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- geolens-io (GitHub)
- Prerequisites
- Install geolens-mcp from pypi (stdio transport). Declares 2 secret inputs. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 1.31.0 · updated
- Official links
Publisher’s description
Read-only access to a self-hosted GeoLens spatial catalog: datasets, features, maps, sandboxed SQL.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 1.31.0, registry status active. 1 package (pypi)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- geolens-io (GitHub)
- Version observed
- 1.31.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.geolens-io%2Fgeolens/versions/1.31.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Query a database in plain language | Publisher description mentions “sql”, “read-only”. | No connection check or task run. Capability is as described by the publisher. | Rule database-query matched: “sql”, “read-only”. Rule database-query. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
geolens-mcp(pypi, stdio, 2 secret inputs)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.geolens-io/geolens
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.