dcos-geoserver

dcos-geoserver appears to be a DC/OS (Marathon) package that deploys and configures a GeoServer instance. GeoServer is typically used to serve geospatial data (e.g., WMS/WFS) over standard OGC protocols.

Evaluated Apr 04, 2026 (19d ago)
Homepage ↗ Repo ↗ Infrastructure gis geoserver dcos marathon ogc wms wfs infrastructure-as-code
⚙ Agent Friendliness
12
/ 100
Can an agent use this?
🔒 Security
30
/ 100
Is it safe for agents?
⚡ Reliability
18
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
10
Error Messages
0
Auth Simplicity
20
Rate Limits
0

🔒 Security

TLS Enforcement
50
Auth Strength
20
Scope Granularity
20
Dep. Hygiene
30
Secret Handling
30

TLS/auth/secret-handling and dependency posture cannot be verified from the provided data. Assume additional review is needed in the repository/package manifests (container images, environment variables, TLS termination, network policies, and GeoServer config).

⚡ Reliability

Uptime/SLA
0
Version Stability
30
Breaking Changes
30
Error Recovery
10
AF Security Reliability

Use Cases

  • Self-hosting GeoServer for serving geospatial layers via OGC standards (WMS/WFS/WCS)
  • Publishing GIS datasets to web/mapping applications
  • Running geospatial services in a DC/OS environment with automated deployment

Not For

  • End-user geospatial analysis workflows without a server component
  • Cloud-managed GeoServer usage where infrastructure automation is not required
  • Lightweight local-only usage without container/orchestrated deployment needs

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

Methods: Not specified in provided data (likely uses GeoServer/DCOS container auth mechanisms if any).
OAuth: No Scopes: No

No authentication details were provided with the package information, so auth method strength and scope granularity cannot be confirmed.

Pricing

Free tier: No
Requires CC: No

Infrastructure software licensing/costs not provided; pricing cannot be determined from the given information.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • No API/MCP interface details were provided, so an agent cannot rely on structured endpoints or machine-readable error contracts.
  • No guidance on idempotency, pagination, or retries was available in the provided information.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for dcos-geoserver.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered