Skip to main content
Glama
GeoRescue MCP Server

GeoRescue MCP Server

by knightchrism

Related Servers

Alternatives to GeoRescue MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to inspect schemas, walk Delta table history, run read-only DuckDB queries, and check data-quality and job-run status safely.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables an AI agent to explore and understand a SQLite database file read-only, inspecting schema relationships, foreign-key gaps, data-quality issues, query plans and generated schema docs. Every tool is guarded so the database file cannot be modified.
      8
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables any LLM client to safely inspect and query an analytical DuckDB database with read-only tools for listing tables, describing schemas, running capped SELECT statements, and retrieving named KPIs.
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to inspect geospatial vector and raster metadata and run bounded analysis on administrator-registered datasets, including planar buffering, clipping, spatial joins, and PNG map rendering delivered as checksummed artifacts. All data access is read-only and controlled through a curated dataset catalog.
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to discover and execute analytical queries on a DuckDB dataset through typed MCP tools, with guarded read-only SQL support for complex calculations without direct database access.
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes a synthetic issue tracker and pipeline warehouse as callable tools so an agent can answer operational questions about tickets, pipeline health, runs, incidents, and governed metrics with every claim cited to the exact tool call it came from. All writes are proposal-only, requiring human approval through a gated apply path that logs each step for audit.
      MIT

    TDQS

    A3.7/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools target distinct resources or actions, and descriptions clarify boundaries such as inspect_dataset for parcel datasets versus find_issues for latest-run issues. Minor overlap remains between inspect_dataset and find_issues, and between run_query and governed metric tools, but the intended use cases are separable.

    Naming Consistency5/5

    All tools use snake_case verb_noun names with clear, predictable verbs such as list_, get_, find_, inspect_, repair_, and compare_. Singular/plural noun choices are appropriate to each operation and remain consistent throughout.

    Tool Count5/5

    Eleven tools is well scoped for a dataset inspection, repair-proposal, results-querying, metrics, and case-review server. Each tool covers a meaningful operation without obvious redundancy.

    Completeness4/5

    The surface covers inspection, repair proposal generation, results-store discovery/querying, governed metrics, case lookup, issue filtering/explanation, and run comparison. Minor gaps exist around listing cases or runs directly and applying a repair, but core workflows are supported.