Geoserver MCP Server

geoserver-mcp PyPI v0.4.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

A GeoServer MCP server implementation that enhances LLM capabilities with geospatial data and mapping services via GeoServer REST API

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/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
Moderate
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 = 95/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 − 5 = 95. 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
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 56

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

  • get_versioningests untrusted input
  • add_layer_to_layergroupno sensitive capability
  • create_catagorized_featurestyleno sensitive capability
  • create_classified_featurestyleno sensitive capability
  • create_coveragestoreno sensitive capability
  • create_coveragestyleno sensitive capability
  • create_datastoreno sensitive capability
  • create_featurestoreno sensitive capability
  • create_gpkg_datastoreno sensitive capability
  • create_layerno sensitive capability
Show 46 more tools ↓
  • create_layergroupno sensitive capability
  • create_outline_featurestyleno sensitive capability
  • create_shp_datastoreno sensitive capability
  • create_styleno sensitive capability
  • create_userno sensitive capability
  • create_usergroupno sensitive capability
  • create_workspaceno sensitive capability
  • delete_coveragestoreno sensitive capability
  • delete_layergroupno sensitive capability
  • delete_resourceno sensitive capability
  • delete_userno sensitive capability
  • delete_usergroupno sensitive capability
  • edit_featuretypeno sensitive capability
  • generate_mapno sensitive capability
  • get_all_usergroupsno sensitive capability
  • get_all_usersno sensitive capability
  • get_coveragestoreno sensitive capability
  • get_coveragestoresno sensitive capability
  • get_datastoreno sensitive capability
  • get_datastoresno sensitive capability
  • get_feature_attributeno sensitive capability
  • get_featuretypesno sensitive capability
  • get_layer_infono sensitive capability
  • get_layergroupno sensitive capability
  • get_layergroupsno sensitive capability
  • get_manifestno sensitive capability
  • get_statusno sensitive capability
  • get_system_statusno sensitive capability
  • list_layersno sensitive capability
  • list_workspacesno sensitive capability
  • modify_userno sensitive capability
  • publish_featurestoreno sensitive capability
  • publish_featurestore_sqlviewno sensitive capability
  • publish_styleno sensitive capability
  • publish_time_dimension_to_coveragestoreno sensitive capability
  • query_featuresno sensitive capability
  • reload_geoserverno sensitive capability
  • remove_layer_from_layergroupno sensitive capability
  • reset_geoserverno sensitive capability
  • style_catagorize_xmlno sensitive capability
  • style_classified_xmlno sensitive capability
  • style_coverage_style_colormapentryno sensitive capability
  • style_coverage_style_xmlno sensitive capability
  • style_outline_only_xmlno sensitive capability
  • update_layergroupno sensitive capability
  • update_serviceno 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
v0.4.0 latest A 95/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 · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/geoserver-mcp/badge.svg)](https://mcptrustchecker.com/registry/geoserver-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/geoserver-mcp"><img src="https://mcptrustchecker.com/registry/geoserver-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/geoserver-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 geoserver-mcp --online --registry pypi

Use the free API → How scoring works

More in Data Science & ML