{"id":"terrestris-geoserver","name":"geoserver","homepage":"https://hub.docker.com/r/terrestris/geoserver","repo_url":"https://hub.docker.com/r/terrestris/geoserver","category":"infrastructure","subcategories":[],"tags":["geospatial","gis","ogc","wms","wfs","wcs","map-server","spatial-data-infrastructure"],"what_it_does":"GeoServer is an open-source server for publishing and sharing geospatial data. It exposes geospatial services (notably OGC standards such as WMS/WFS/WCS) and enables configuring data stores and styling to serve maps and geodata over HTTP.","use_cases":["Publishing geospatial layers and maps from common data sources (e.g., PostGIS, files)","Serving OGC-compliant map and feature services (WMS/WFS/WCS) for GIS clients","Building interoperable geospatial web services for internal and external stakeholders","Geospatial data integration for applications requiring standards-based access"],"not_for":["General-purpose application API (it is specialized for geospatial publishing)","Real-time OLTP-style querying workloads without careful architecture tuning","Use cases requiring a fully managed SaaS experience with vendor-managed uptime/SLA"],"best_when":"You need standards-based geospatial services over HTTP (OGC/ISO-like usage) and you can operate/configure the server (including security and scaling).","avoid_when":"You cannot operate infrastructure or you require a turnkey, documented API with simple SaaS authentication and rate limiting guarantees.","alternatives":["MapServer (OGC-focused geospatial map server)","QGIS Server (OGC services via QGIS ecosystem)","ArcGIS Server (commercial managed geospatial services)","Tiled/XYZ tile services paired with a tile backend (for map tiling workflows)","Commercial OGC server stacks (various vendors)"],"af_score":41.2,"security_score":47.2,"reliability_score":40.0,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:42:56.094189+00:00","interface":{"has_rest_api":true,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["HTTP Basic Auth (commonly used when configured with a security filter)","Session-based auth (when using web security integration)","IP/network-based access control (via reverse proxy/firewall)","Integration with external auth providers (via commonly used deployment patterns)"],"oauth":false,"scopes":false,"notes":"GeoServer authentication is typically handled by server deployment configuration (web app security) and/or by placing it behind a reverse proxy that enforces auth; fine-grained OAuth scopes are not inherent to the core service interface."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Open-source; costs come from hosting, operations, and any enterprise/support subscriptions rather than per-request API pricing."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":41.2,"security_score":47.2,"reliability_score":40.0,"mcp_server_quality":0.0,"documentation_accuracy":55.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":45.0,"rate_limit_clarity":10.0,"tls_enforcement":70.0,"auth_strength":50.0,"scope_granularity":20.0,"dependency_hygiene":45.0,"secret_handling":50.0,"security_notes":"Security primarily depends on deployment choices (TLS termination, auth configuration, reverse proxy/WAF, and network restrictions). OAuth-style scoped authorization is not inherent. Agents should assume they will need to rely on standard web/security hardening practices around the GeoServer instance.","uptime_documented":0.0,"version_stability":65.0,"breaking_changes_history":60.0,"error_recovery":35.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["GeoServer is commonly deployed with configuration/state in the server, so automation that changes configuration should be careful about concurrency and repeatability.","OGC endpoints may return service-specific error formats; clients should not assume JSON-only error responses.","Without a clear API contract (e.g., OpenAPI), agents may need domain knowledge of WMS/WFS/WCS request parameters and response structures."]}}