Use in your browser
Walk a hosted STAC catalog's live link tree within caps and validate reached documents against core and extension schemas, or compare two bounded snapshots. API search and pagination are skipped; the comparison does not verify revision lineage or equivalent coverage.
Guest includes 50 lifetime app requests. Create a free account for 100 app requests each calendar month. One allowance across every app, in your browser and your agent.One allowance across every app, in your browser and your agent. Manage usage
Guest access is available after setup. Full account linking verified by PowMCP: Claude only.
Connect this app on its own. Add other PowMCP apps whenever your agent needs another job done.
Open the apps workspace
Choose your agent. Each button opens a new tab with only this app's endpoint ready to add.
ClaudeOpen Claude setup Guest access + account linking verified by PowMCP
VS CodeOpen VS Code setup Guest access available · Account linking not yet verified
KiroOpen Kiro setup Guest access available · Account linking not yet verified
LM StudioOpen LM Studio setup Guest access available · Account linking not yet verified
Visual StudioOpen Visual Studio setup (Windows) Guest access available · Account linking not yet verifiedCopy one ready-to-send prompt for any agent that supports remote MCP connections.
For clients that require manual configuration, use this app-only endpoint, its JSON entry, or one terminal command.
ChatGPT: enable Developer mode in Settings → Security and login, then add this MCP endpoint from the Plugins page. Availability depends on your account and workspace policy. PowMCP has not yet verified ChatGPT account linking. OpenAI setup guide
https://powmcp.com/geo-catalog-check/mcp {
"mcpServers": {
"powmcp-geo-catalog-check": {
"type": "http",
"url": "https://powmcp.com/geo-catalog-check/mcp"
}
}
}Terminal agents add this app with one command:
claude mcp add --transport http powmcp-geo-catalog-check https://powmcp.com/geo-catalog-check/mcpcodex mcp add powmcp-geo-catalog-check --url https://powmcp.com/geo-catalog-check/mcpgemini mcp add --transport http powmcp-geo-catalog-check https://powmcp.com/geo-catalog-check/mcpManage, disable, or remove this connection in your agent's own MCP settings. PowMCP does not label an external connection as installed without confirmation from that client.
Proof
Traverse and validate a hosted STAC catalog's linked metadata tree as far as the traversal caps reach, before you publish it
Recursively fetch and traverse a hosted STAC catalog, collection, or item link tree under document, depth, and byte caps (100 documents and 5 levels by default; search and pagination links are never followed) and validate every JSON document the traversal reaches against the pinned STAC core and extension schemas for its detected version, with link and bounded asset-href integrity findings located per document, or compare two user-provided catalog roots, validating machine-checkable structure only, never the truth of the underlying geospatial data, and never claiming coverage beyond the traversal bound it reports.
Request cost1 completed result
Guests get 50 lifetime app requests. Free accounts get 100 each calendar month.
stac_catalog_check
Preflight one public STAC catalog, collection, or item by recursively traversing its live child and item link tree under strict document, depth, and byte caps, validating every fetched document against the app-bundled STAC core and extension schemas for its detected version (STAC 1.0.0 or 1.1.0), and checking link and bounded asset-href reachability. Distinguishes not-a-stac-document from invalid, version-not-detected from unsupported, link-unreachable from link-not-declared, asset-unreachable from asset-not-declared, and no-violations from traversal-truncated. It does NOT follow search or pagination links (a live STAC API root is bounded, never crawled to exhaustion), and it validates machine-checkable structure only, never whether the imagery, geometry, datetimes, band metadata, or asset contents are correct or usable. It never validates a local or pasted catalog; the value is the live traversal of the hosted link graph. Each call fetches many live documents and can take up to 110 seconds.
stac_catalog_compare
Compare exactly two user-provided public STAC roots under identical bounded traversal and validation, and report finding signatures observed only in each bounded snapshot. The comparable field means technical root-type and STAC-version compatibility only; provider lineage and equivalent traversal coverage are not verified. The introduced/resolved fields retain observed-only differences, not proof of regressions or fixes, and no cleaner-root winner is established. Use stac_catalog_check for a single root. Like stac_catalog_check it never follows search or pagination links, validates machine-checkable structure only, and never judges the underlying geospatial data. Each comparison fetches many live documents across both roots and can take up to 110 seconds.
Other apps for the jobs next to Geospatial Catalog Check.
Scope and boundaries for Geospatial Catalog Check.
Start at the public Earth Search STAC root with maxDocs 10, maxDepth 2, and maxAssetProbes 5 to validate a small live slice of its catalog, or apply identical caps to two same-lineage catalog revisions.
PASS covers only the observed traversal. Read docsTraversed, docsInvalid, apiPagingSkipped, assetProbes, and truncation: skipped API search/paging prevents exhaustive coverage, and zero asset probes means reachability was not tested. Best-practice advisories do not change the verdict. In comparisons, comparable means matching root type and STAC version only; lineage and equivalent coverage remain unverified. introduced/resolved list finding signatures observed only in one returned snapshot, not proven regressions or fixes, and no cleaner catalog is established.
Only hosted STAC catalogs, collections, or items are traversed. Search and pagination links are never followed, and document, depth, byte, and asset-probe caps bound coverage; validation does not establish that imagery, geometry, timestamps, band metadata, or asset contents are correct.