{"id":"terrestris-geoserver","name":"geoserver","af_score":41.2,"security_score":47.2,"reliability_score":40.0,"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.","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.","last_evaluated":"2026-04-04T19:42:56.094189+00:00","has_mcp":false,"has_api":true,"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)"],"has_free_tier":false,"known_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."],"error_quality":0.0}