stac-mcp-server

An MCP (Model Context Protocol) server that exposes STAC (SpatioTemporal Asset Catalog) capabilities to agent tools, enabling LLM agents to search and retrieve STAC catalog/resource information via MCP.

Evaluated Apr 04, 2026 (21d ago)
Homepage ↗ Infrastructure stac mcp geospatial metadata agent-tools
⚙ Agent Friendliness
53
/ 100
Can an agent use this?
🔒 Security
40
/ 100
Is it safe for agents?
⚡ Reliability
30
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
65
Documentation
55
Error Messages
0
Auth Simplicity
50
Rate Limits
35

🔒 Security

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

No security configuration details (TLS requirements, auth method, secrets handling, or dependency posture) were provided in the supplied input, so scores reflect uncertainty rather than confirmed safety.

⚡ Reliability

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

Best When

You want an agent to interact with STAC catalogs and perform search/lookup operations through MCP in a standardized way.

Avoid When

You cannot provide network access or are unable to configure MCP runtime/tooling; you require robust documented authentication and operational guarantees.

Use Cases

  • Agent-driven discovery of geospatial assets using STAC search queries
  • Context gathering for geospatial workflows (e.g., selecting imagery/assets)
  • Integrating STAC catalog data into agent toolchains via MCP tool calls

Not For

  • High-volume transactional workloads not suited to metadata search
  • Use cases requiring a first-class REST/SDK integration rather than agent-tool access
  • Scenarios where you need strict compliance/data residency guarantees without vendor documentation

Interface

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

Authentication

OAuth: No Scopes: No

No authentication details were provided in the supplied input, so auth requirements cannot be confirmed.

Pricing

Free tier: No
Requires CC: No

No pricing information provided.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • STAC APIs commonly involve pagination/limits; ensure the MCP server exposes or handles them consistently (not verifiable from provided input).
  • STAC search filters (bbox/time/cloud cover, etc.) are easy for agents to mis-specify; guardrails/validation may be needed (not verifiable from provided input).
  • Catalogs can be large; agents may generate overly broad queries leading to timeouts or large result sets (not verifiable from provided input).

Alternatives

Full Evaluation Report

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

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