Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.ronitjadhav/geoservercloud-mcp

PYPI · GEOSERVERCLOUD-MCP

MCP server for managing GeoServer workspaces, datastores, layers, and styles

Available components

0 this week 77 Trust /100

Last scanned (21 hours ago)

Scores higher than 74% of PyPI servers

Category Maps and Location

Trust breakdown (7 categories)

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs poetry.core.masonry.api at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 3 of 37 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to ronitjadhav/geoservercloud-mcp). View diagnostics → Pass
  • Clear OSI-approved license (BSD-2-Clause).Pass
  • Actively maintained (last published 98 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 4473 tokens (~58/item across 76 items; 76 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 22 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_workspace" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 77 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 23 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 18 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 17 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
  • 15 Oct 26 −14
    • Malware scan: pass → unverified ▼ security
  • 13 Oct 26 +1

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

  • 4 Oct 26 −3
    • Stability: pass → 0.80 functional
  • 3 Oct 26 +1
    • Stability: 0.97 → pass security
  • 1 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
Diagnostics

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 23 Oct 2026 · Analysed pypi/geoservercloud-mcp@1.0.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo ronitjadhav/geoservercloud-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/ronitjadhav/geoservercloud-mcp/.github/workflows/publish.yaml@refs/tags/v1.0.0
Rekor log index 2047457542
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:5c964aee042a7bde510f605853c2a6228159ba5290d802e052d46115324c427a

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted poetry.core.masonry.api

Background: Why install scripts are a supply-chain risk →

Dependencies 37 packages
Packages resolved 37
Stale 2
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 76 exposed · ~4,244 tokens

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 →

Tool Tokens
assign_role_to_user ~36

Assign a role to a user.

NameTypeReqDescription
role_namestringyesRole to assign
usernamestringyesUsername

Structured output declared, but exposes no named fields.

No examples provided.

configure_geoserver_connection ~95

Configure the GeoServer connection at runtime. Use this to set the GeoServer URL and credentials when they are not pre-configured via environment variables.

NameTypeReqDescription
passwordstring–GeoServer password (default: geoserver)
urlstringyesGeoServer base URL (e.g., http://localhost:8080/geoserver)
userstring–GeoServer username (default: admin)

Structured output declared, but exposes no named fields.

No examples provided.

create_acl_admin_rule ~62

Create a GeoServer ACL admin rule.

NameTypeReqDescription
accessstring–Access level
priorityinteger–Rule priority
role––Role name (optional)
user––Username (optional)
workspace_name––Workspace (optional)

Structured output declared, but exposes no named fields.

No examples provided.

create_acl_rule ~90

Create a GeoServer ACL data rule.

NameTypeReqDescription
accessstring–ALLOW or DENY
priorityinteger–Rule priority (lower = higher priority)
request––Request type
role––Role name (optional)
service––Service (WMS, WFS, etc.)
user––Username (optional)
workspace_name––Workspace (optional)

Structured output declared, but exposes no named fields.

No examples provided.

create_acl_rules_for_requests ~106

Create one ACL data rule per request type in a single call.

NameTypeReqDescription
accessstring–ALLOW or DENY
priorityinteger–Rule priority (lower = higher priority)
requestsarrayyesRequest types to create rules for (e.g., ["GetMap", "GetFeature"])
role––Role name (optional)
service––Service (WMS, WFS, etc.)
workspace_name––Workspace (optional)

Structured output declared, but exposes no named fields.

No examples provided.

create_coverage ~66

Publish a coverage layer from a coverage store.

NameTypeReqDescription
coverage_namestringyesName for the coverage layer
coveragestore_namestringyesName of the coverage store
title––Human-readable title
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

create_coverage_store ~93

Create a coverage store for raster data.

NameTypeReqDescription
coveragestore_namestringyesName for the coverage store
enabledboolean–Enable the store (default: True)
store_typestring–Type (ImageMosaic, GeoTIFF, etc.)
urlstringyesPath to the raster data directory or file
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

create_datastore ~97

Create a generic datastore with custom connection parameters.

NameTypeReqDescription
connection_parametersobjectyesDict of connection parameters
datastore_namestringyesName for the new datastore
datastore_typestringyesType (e.g., "PostGIS", "Shapefile")
description––Optional description
enabledboolean–Enable the datastore (default: True)
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

create_feature_type ~107

Create a feature type (vector layer) from a database table.

NameTypeReqDescription
abstract––Layer description
datastore_namestringyesName of the datastore
epsginteger–EPSG code for the SRS (default: 4326)
keywords––List of keywords
layer_namestringyesName for the layer (must match table name)
title––Human-readable title
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

create_gridset ~50

Create a gridset for GeoWebCache. Supported EPSG codes: 2056, 21781, 3857.

NameTypeReqDescription
epsgintegeryesEPSG code for the gridset

Structured output declared, but exposes no named fields.

No examples provided.

create_imagemosaic_store_from_directory ~71

Create an ImageMosaic coverage store from a directory of raster files.

NameTypeReqDescription
coveragestore_namestringyesName for the coverage store
directory_pathstringyesPath to the directory containing raster files
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

create_jndi_datastore ~83

Create a PostGIS datastore from a JNDI resource.

NameTypeReqDescription
datastore_namestringyesName for the new datastore
description––Optional description
jndi_referencestringyesJNDI resource name
pg_schemastring–Schema name (default: public)
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

create_layer_group ~120

Create a layer group combining multiple layers.

NameTypeReqDescription
abstract––Layer group description
epsginteger–EPSG code (default: 4326)
group_namestringyesName for the layer group
layersarrayyesList of layer names to include
modestring–Mode (SINGLE, NAMED, CONTAINER, EO)
styles––List of style names (one per layer)
title––Human-readable title
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

create_pg_datastore ~115

Create a PostGIS datastore connection.

NameTypeReqDescription
datastore_namestringyesName for the new datastore
description––Optional description
pg_dbstringyesDatabase name
pg_hoststringyesPostgreSQL host
pg_passwordstringyesDatabase password
pg_portintegeryesPostgreSQL port
pg_schemastring–Schema name (default: public)
pg_userstringyesDatabase username
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

create_pmtiles_datastore ~66

Create a PMTiles datastore.

NameTypeReqDescription
datastore_namestringyesName for the new datastore
description––Optional description
pmtiles_urlstringyesURL or path to the PMTiles file
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

create_role ~27

Create a GeoServer role.

NameTypeReqDescription
role_namestringyesName for the new role

Structured output declared, but exposes no named fields.

No examples provided.

create_style_definition ~88

Create a style catalog entry pointing at an existing style file on the server.

NameTypeReqDescription
filenamestringyesName of the backing style file (e.g., 'my_style.sld')
style_formatstring–Style format (default: 'sld')
style_namestringyesName for the new style
workspace_name––Optional workspace (global if not provided)

Structured output declared, but exposes no named fields.

No examples provided.

create_style_from_file ~92

Create a style by uploading a local style file (SLD, or a ZIP bundling an SLD with its images). The path is read from the machine running the MCP server.

NameTypeReqDescription
filestringyesPath to the style file (.sld or .zip)
style_namestringyesName for the new style
workspace_name––Optional workspace (global if not provided)

Structured output declared, but exposes no named fields.

No examples provided.

create_style_from_string ~59

Create a style from an SLD string.

NameTypeReqDescription
style_contentstringyesSLD content as a string
style_namestringyesName for the new style
workspace_name––Optional workspace (global if not provided)

Structured output declared, but exposes no named fields.

No examples provided.

create_user ~52

Create a GeoServer user.

NameTypeReqDescription
enabledboolean–Enable the user (default: True)
passwordstringyesPassword for the new user
usernamestringyesUsername for the new user

Structured output declared, but exposes no named fields.

No examples provided.

create_wms_layer ~80

Publish a layer from a cascaded WMS store.

NameTypeReqDescription
native_layer_namestringyesLayer name in the remote WMS
published_layer_name––Published name (default: same as native)
wms_store_namestringyesName of the WMS store
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

create_wms_store ~70

Create a cascaded WMS store to proxy an external WMS service.

NameTypeReqDescription
capabilities_urlstringyesURL to the external WMS GetCapabilities
wms_store_namestringyesName for the new WMS store
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

create_wmts_layer ~100

Publish a layer from a cascaded WMTS store.

NameTypeReqDescription
epsginteger–EPSG code for the layer (default: 4326)
native_layer_namestringyesLayer name in the remote WMTS
published_layer_name––Published name (default: same as native)
wmts_store_namestringyesName of the WMTS store
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

create_wmts_store ~70

Create a cascaded WMTS store to proxy an external WMTS service.

NameTypeReqDescription
capabilities_urlstringyesURL to the external WMTS GetCapabilities
wmts_store_namestringyesName for the new WMTS store
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

create_workspace ~58

Create a new workspace in GeoServer. If the workspace already exists, it will be updated.

NameTypeReqDescription
isolatedboolean–If True, workspace will be isolated (default: False)
workspace_namestringyesName for the new workspace

Structured output declared, but exposes no named fields.

No examples provided.

delete_acl_admin_rule ~32

Delete an ACL admin rule by ID.

NameTypeReqDescription
rule_idintegeryesID of the rule to delete

Structured output declared, but exposes no named fields.

No examples provided.

delete_all_acl_admin_rules ~27

Delete all ACL admin rules. WARNING: This removes all admin access control rules.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

delete_all_acl_rules ~25

Delete all ACL data rules. WARNING: This removes all access control rules.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

delete_coverage_store ~49

Delete a coverage store and all its coverages.

NameTypeReqDescription
coveragestore_namestringyesName of the coverage store to delete
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

delete_datastore ~42

Delete a datastore from a workspace.

NameTypeReqDescription
datastore_namestringyesName of the datastore to delete
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

delete_feature_type ~57

Delete a feature type and its associated layer.

NameTypeReqDescription
datastore_namestringyesName of the datastore
layer_namestringyesName of the feature type to delete
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

delete_gwc_layer ~45

Remove tile caching for a layer from GeoWebCache.

NameTypeReqDescription
layer_namestringyesName of the layer
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

delete_layer_group ~42

Delete a layer group.

NameTypeReqDescription
layer_group_namestringyesName of the layer group to delete
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

delete_role ~28

Delete a GeoServer role.

NameTypeReqDescription
role_namestringyesName of the role to delete

Structured output declared, but exposes no named fields.

No examples provided.

delete_user ~24

Delete a GeoServer user.

NameTypeReqDescription
usernamestringyesUsername to delete

Structured output declared, but exposes no named fields.

No examples provided.

delete_wms_layer ~62

Delete a WMS layer.

NameTypeReqDescription
wms_layer_namestringyesName of the WMS layer to delete
wms_store_namestringyesName of the WMS store
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

delete_wms_store ~50

Delete a WMS store and all its layers.

NameTypeReqDescription
wms_store_namestringyesName of the WMS store to delete
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

delete_wmts_store ~50

Delete a WMTS store and all its layers.

NameTypeReqDescription
wmts_store_namestringyesName of the WMTS store to delete
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

delete_workspace ~49

Delete a workspace and all its contents recursively. WARNING: This will delete all datastores, layers, and styles in the workspace.

NameTypeReqDescription
workspace_namestringyesName of the workspace to delete

Structured output declared, but exposes no named fields.

No examples provided.

describe_feature_type ~39

WFS DescribeFeatureType request to get schema information.

NameTypeReqDescription
type_name––Optional feature type name
workspace_name––Optional workspace name

Structured output declared, but exposes no named fields.

No examples provided.

get_acl_rules ~17

Get all GeoServer ACL data rules.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_coverage ~55

Get details of a specific coverage.

NameTypeReqDescription
coverage_namestringyesName of the coverage
coveragestore_namestringyesName of the coverage store
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

get_coverage_store ~44

Get details of a coverage store.

NameTypeReqDescription
coveragestore_namestringyesName of the coverage store
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

get_coverages ~50

List all coverages (raster layers) in a coverage store.

NameTypeReqDescription
coveragestore_namestringyesName of the coverage store
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

get_datastore ~40

Get details of a specific datastore.

NameTypeReqDescription
datastore_namestringyesName of the datastore
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

get_datastores ~31

List all datastores in a workspace.

NameTypeReqDescription
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

get_feature ~68

WFS GetFeature request to retrieve features from a layer.

NameTypeReqDescription
feature_id––Optional specific feature ID
max_features––Maximum number of features to return
type_namestringyesFeature type (layer) name
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

get_feature_type ~55

Get details of a specific feature type.

NameTypeReqDescription
datastore_namestringyesName of the datastore
feature_type_namestringyesName of the feature type
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

get_feature_types ~45

List all feature types (vector layers) in a datastore.

NameTypeReqDescription
datastore_namestringyesName of the datastore
workspace_namestringyesName of the workspace

Structured output declared, but exposes no named fields.

No examples provided.

get_geoserver_connection_info ~68

Get current GeoServer connection information. Shows the configured URL and username (password is hidden). Check 'configured' field to see if connection was explicitly set. If configured is 'false', ask the user for connection details and use configure_geoserver_connection() to set them.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the io.github.ronitjadhav/geoservercloud-mcp server?

io.github.ronitjadhav/geoservercloud-mcp runs locally as a PyPI package, launched with uvx geoservercloud-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 · geoservercloud-mcp

# add to Claude Code
claude mcp add ronitjadhav-geoservercloud-mcp -- uvx geoservercloud-mcp
Common questions

What is the io.github.ronitjadhav/geoservercloud-mcp server?

io.github.ronitjadhav/geoservercloud-mcp is listed in the public MCP registry as io.github.ronitjadhav/geoservercloud-mcp. MCP server for managing GeoServer workspaces, datastores, layers, and styles. This page covers its PyPI package (geoservercloud-mcp).

Is the io.github.ronitjadhav/geoservercloud-mcp server safe to use?

io.github.ronitjadhav/geoservercloud-mcp scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. Its build provenance is signed and verified. 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 io.github.ronitjadhav/geoservercloud-mcp server expose?

io.github.ronitjadhav/geoservercloud-mcp exposes 76 tools: get_geoserver_connection_info, configure_geoserver_connection, get_version, get_workspaces, get_workspace, and 71 more. Their descriptions and schemas cost roughly 4,244 tokens of context every time the server is loaded.

Is the io.github.ronitjadhav/geoservercloud-mcp server still maintained?

io.github.ronitjadhav/geoservercloud-mcp is still listed as active in the MCP registry. We last reached this channel on 23 October 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 io.github.ronitjadhav/geoservercloud-mcp server under?

io.github.ronitjadhav/geoservercloud-mcp declares the BSD-2-Clause licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.