GeoRescue MCP Server
Related Servers
Alternatives to GeoRescue MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to inspect schemas, walk Delta table history, run read-only DuckDB queries, and check data-quality and job-run status safely.MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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.MIT
- AlicenseAqualityCmaintenanceEnables 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.6MIT
- AlicenseNot gradedqualityCmaintenanceExposes 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
- AlicenseNot gradedqualityBmaintenanceExposes local data profiling, PII classification, and plan-based cleansing against DuckDB, Postgres, or SQLMesh tables through four tools (list_tables, profile, propose_cleansing_plan, apply_cleansing_plan). All reasoning stays aggregate-only — format signatures, counts, and match rates rather than raw cell values — and cleaning plans execute only after validation against a fixed operation vocabulary and explicit confirmation.92 PyPIMIT
- AlicenseAqualityBmaintenanceEnables coding agents to query and modify a SQLite database through twelve SQL-based tools, with safety enforced server-side via statement policies, protected tables, result caps, and snapshots. It also provides an append-only, hash-chained memory log with checkpoints so agents can record events and resume context across sessions.12MIT
TDQS
Scored across 11 tools
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.
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.
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.
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.