GeoEDGE MCP
PYPI · GEOEDGE-MCP
Geospatial analysis: vector and raster GIS operations, cartographic maps, spatial data access
Available components
Last scanned (1 day ago)
Scores higher than 17% of PyPI servers
Category Maps and Location
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. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 8 of 77 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Build provenance not yet verified. View diagnostics → Unverified
- License check failed: the license (LicenseRef-Proprietary) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 50 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 21 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 20 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 19 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 16 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Oct 26 −12
- Malware scan: pass → unverified ▼ security
- Known CVEs: partial → pass ▲ security
- Dependency health: partial → 0.95 functional
- 13 Oct 26 +8
- Known CVEs: unverified → partial ▲ security
- Dependency health: unverified → partial ▲ functional
- 12 Oct 26 −11
- Known CVEs: pass → unverified ▼ security
- Dependency health: 0.95 → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/geoedge-mcp@1.0.9
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | pypi |
| Reason | Unsupported forge |
| Discovered via | Registry attestation endpoint |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 77 packages
| Packages resolved | 77 |
|---|---|
| Stale | 8 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the GeoEDGE MCP server?
GeoEDGE MCP runs locally as a PyPI package, launched with uvx geoedge-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · geoedge-mcp
claude mcp add geoedge-git-geoedge-mcp -- uvx geoedge-mcp
What is the GeoEDGE MCP server?
GeoEDGE MCP is listed in the public MCP registry as io.github.GeoEDGE-git/geoedge-mcp. Geospatial analysis: vector and raster GIS operations, cartographic maps, spatial data access. This page covers its PyPI package (geoedge-mcp).
Is the GeoEDGE MCP server safe to use?
GeoEDGE MCP scores 31 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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.
Is the GeoEDGE MCP server still maintained?
GeoEDGE MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 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 GeoEDGE MCP server under?
GeoEDGE MCP declares the LicenseRef-Proprietary licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.