Geoservercloud MCP Server

geoservercloud-mcp PyPI v1.0.0

Published by ronitjadhav — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP (Model Context Protocol) server for GeoServer - enables AI assistants to manage GeoServer workspaces, datastores, layers, and styles through natural language

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 76

Each tool and what it can reach — statically extracted from the published source.

  • assign_role_to_userno sensitive capability
  • configure_geoserver_connectionno sensitive capability
  • create_acl_admin_ruleno sensitive capability
  • create_acl_ruleno sensitive capability
  • create_acl_rules_for_requestsno sensitive capability
  • create_coverageno sensitive capability
  • create_coverage_storeno sensitive capability
  • create_datastoreno sensitive capability
  • create_feature_typeno sensitive capability
  • create_gridsetno sensitive capability
Show 66 more tools ↓
  • create_imagemosaic_store_from_directoryno sensitive capability
  • create_jndi_datastoreno sensitive capability
  • create_layer_groupno sensitive capability
  • create_pg_datastoreno sensitive capability
  • create_pmtiles_datastoreno sensitive capability
  • create_roleno sensitive capability
  • create_style_definitionno sensitive capability
  • create_style_from_fileno sensitive capability
  • create_style_from_stringno sensitive capability
  • create_userno sensitive capability
  • create_wms_layerno sensitive capability
  • create_wms_storeno sensitive capability
  • create_wmts_layerno sensitive capability
  • create_wmts_storeno sensitive capability
  • create_workspaceno sensitive capability
  • delete_acl_admin_ruleno sensitive capability
  • delete_all_acl_admin_rulesno sensitive capability
  • delete_all_acl_rulesno sensitive capability
  • delete_coverage_storeno sensitive capability
  • delete_datastoreno sensitive capability
  • delete_feature_typeno sensitive capability
  • delete_gwc_layerno sensitive capability
  • delete_layer_groupno sensitive capability
  • delete_roleno sensitive capability
  • delete_userno sensitive capability
  • delete_wms_layerno sensitive capability
  • delete_wms_storeno sensitive capability
  • delete_wmts_storeno sensitive capability
  • delete_workspaceno sensitive capability
  • describe_feature_typeno sensitive capability
  • get_acl_rulesno sensitive capability
  • get_coverageno sensitive capability
  • get_coverage_storeno sensitive capability
  • get_coveragesno sensitive capability
  • get_datastoreno sensitive capability
  • get_datastoresno sensitive capability
  • get_featureno sensitive capability
  • get_feature_typeno sensitive capability
  • get_feature_typesno sensitive capability
  • get_geoserver_connection_infono sensitive capability
  • get_gwc_layerno sensitive capability
  • get_layer_groupno sensitive capability
  • get_layer_groupsno sensitive capability
  • get_pg_datastoreno sensitive capability
  • get_property_valueno sensitive capability
  • get_style_definitionno sensitive capability
  • get_stylesno sensitive capability
  • get_user_rolesno sensitive capability
  • get_versionno sensitive capability
  • get_wfs_layersno sensitive capability
  • get_wms_layerno sensitive capability
  • get_wms_layersno sensitive capability
  • get_wms_storeno sensitive capability
  • get_workspaceno sensitive capability
  • get_workspace_wms_settingsno sensitive capability
  • get_workspacesno sensitive capability
  • harvest_granules_to_coverage_storeno sensitive capability
  • publish_granule_to_coverage_storeno sensitive capability
  • publish_gwc_layerno sensitive capability
  • publish_workspaceno sensitive capability
  • recreate_workspaceno sensitive capability
  • remove_role_from_userno sensitive capability
  • set_default_layer_styleno sensitive capability
  • set_default_locale_for_serviceno sensitive capability
  • unset_default_locale_for_serviceno sensitive capability
  • update_userno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.0 latest A 99/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/geoservercloud-mcp/badge.svg)](https://mcptrustchecker.com/registry/geoservercloud-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/geoservercloud-mcp"><img src="https://mcptrustchecker.com/registry/geoservercloud-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/geoservercloud-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan geoservercloud-mcp --online --registry pypi

Use the free API → How scoring works

More in Databases