geo-osiris-mcp
Related Servers
Alternatives to geo-osiris-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to perform geospatial analysis, spatial data processing, vector and raster operations, coordinate transformations, spatial statistics, mapping, and access to climate, satellite, and other geospatial data through MCP-compatible clients.MIT

MapSmithofficial
AlicenseAqualityAmaintenanceEnables AI agents to perform professional-grade geoprocessing tasks such as buffers, overlays, reprojections, and terrain analysis with deterministic tools and verifiable provenance.28AGPL 3.0- AlicenseAqualityCmaintenanceEnables AI agents to discover and access 800TB+ of public geospatial data from Source Cooperative, with tools for listing organizations, products, files, and fuzzy search.62MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to securely query VAST Data databases for schema, metadata, and sample data via read-only SQL and MCP resources.MIT
- FlicenseAqualityBmaintenanceEnables AI agents to query Earth observation data, satellite imagery, active fires, and weather via natural language, returning interactive maps and briefs.12-
- AlicenseBqualityBmaintenanceProvides sovereign geospatial awareness by wrapping open, non-US-dependent geospatial APIs for AI-agent situational awareness, environmental compliance, and disaster response.5MIT
TDQS
Scored across 14 tools
Most tools are clearly separated by resource and action (list_*, get_*, infer_*, compare_*). A few operational summaries like inspect_layer and summarize_import overlap somewhat with their get_* counterparts, but the descriptions provide enough distinction to avoid serious misselection.
Tool names overwhelmingly follow a consistent verb_noun snake_case pattern such as list_layers, get_feature, and list_import_rows. The only minor deviation is health, which is a single noun rather than a verb_noun form, but it is a conventional health-check name and does not create confusion.
Fourteen tools is well within the ideal range for a domain-specific server. Each tool covers a distinct resource or operation in the Geo Hub/import workflow, and none feel redundant or excessive.
The tool surface is strong for read-only inspection, listing, CSV inference, and advisory comparison. However, there are notable gaps around the import lifecycle: no tool commits, publishes, or archives an import, and there is no create/update/delete coverage for layers or sources, leaving the workflow incomplete for agents that need to act rather than only inspect.