GeoRescue MCP Server
GeoRescue MCP is a read-only analysis and proposal server for parcel data quality, repair, and case evidence.
Inspect parcel datasets (SHP/GPKG/GeoJSON) for issues, filtered by check, severity, paging, and optional WKT geometry.
Propose repairs by writing a repaired copy and changelog into a new output folder, never modifying the source.
Explore the redacted DuckDB results store by listing tables and describing columns/types.
Run guarded, single read-only SELECT/WITH SQL queries with row caps and a timeout.
List and compute governed metrics, with optional grouping, SQL used, and caveats.
Look up case files by case ID or parcel ID, including verdict, confidence, ORB refs, deed checks, and parcel issues.
Find issues by bounding box, check, severity, or parcel ID, and explain issue types or glossary terms.
Compare issue counts by check between runs.
Keep agent access redacted and logged, with no owner names and no write access to source data.
Provides tools for working with GeoRescue's redacted DuckDB results store: listing and describing tables, running guarded read-only queries, retrieving metrics, cases, issues, and comparing runs.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GeoRescue MCP Server repair data.gpkg and save a corrected copy with a changelog"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Status: early prototype, work in progress.
Test demo — not authoritative. Not a survey, title opinion, or legal determination; for testing and demonstration only. Results are automated, experimental data quality test results computed from public data. Verdicts are proposals, not findings; placements of deed descriptions are best-fit, not measured in the field. Consult a licensed surveyor and mapper or an attorney and the official records. GeoRescue is not affiliated with the City of Jacksonville, the Duval County Clerk of Courts or the Duval County Property Appraiser. See TERMS.md. Questions, corrections or removal requests: open an issue at https://github.com/knightchrism/georescue/issues
What it does
Inspects parcel layers (SHP / GPKG / GeoJSON) for invalid or empty geometry, duplicate IDs and geometries, CRS problems, out-of-bounds features, overlaps, slivers, gaps and attribute-rule violations (YAML rules, Pydantic-validated).
Proposes repairs on a copy — the source file is never modified; every proposed change is written to
changelog.csvwith before/after, reason and whether it was applied (an audit trail for review).Checks overlaps against the record: appraiser legal descriptions, deed OCR, metes-and-bounds / COGO traverses and closure, compared back to the GIS fabric (
verify/).Publishes a static dashboard with per-case evidence pages, owner names redacted by default.
Talks to agents through an MCP server backed by a redacted DuckDB results store.
Related MCP server: Tickets and Warehouse MCP Servers
Architecture
flowchart LR
A[Parcel layer<br/>SHP · GPKG · GeoJSON · ArcGIS REST] --> B[inspect<br/>checks.py + YAML rules]
B --> C[repair on a copy<br/>repair.py]
C --> D[(out/<br/>corrected.gpkg · changelog.csv<br/>issues.csv · diff.csv · report.html)]
B --> V[verify/<br/>PAO legal desc · deed OCR · COGO · PLSS]
D --> P[publish<br/>redact owners]
V --> P
P --> S[Static site<br/>GitHub Pages]
D --> L[load-db<br/>redacted DuckDB]
L --> M[georescue-mcp<br/>read-only tools · logs/mcp.log]
M --> AG[AI agent<br/>Claude · Cursor · ...]Quickstart
git clone https://github.com/knightchrism/georescue.git && cd georescue
uv sync --extra verify
PYTHONPATH=. uv run --extra verify pytest -q # test suite
uv run georescue inspect data.gpkg -c configs/columbia_fl.yaml
uv run georescue repair data.gpkg -c configs/columbia_fl.yaml -o out/On Windows, clone to a local folder such as C:\dev\georescue (keep projects out of OneDrive-synced folders).
AI / agent angle
georescue-mcpexposes inspection, repair-to-a-new-folder, guarded read-only SQL, governed metrics and case lookups to any MCP client (details below).scripts/mcp_demo.pyrecords real agent sessions;agent_demo/drives a visualization loop and saves before/after snapshots.Agents get the redacted store only — never owner names, never write access to source data.
Tech stack
Python 3.13 · uv · GeoPandas · Shapely · pyogrio · PyProj · DuckDB · Pydantic · Typer · Jinja2 · Streamlit + Folium · MCP Python SDK · MapLibre GL JS · GitHub Actions + Pages
Core (V1)
GIS data-quality & repair for parcel datasets. Load (SHP/GPKG/GeoJSON) → inspect → classify issues → propose repairs on a copy (every change logged) → export corrected.gpkg, changelog.csv, issues.csv, diff.csv, summary.json, report.html.
Checks
missing/empty/invalid geometry · duplicate IDs · duplicate geometries · required attributes & types (YAML rules, Pydantic-validated) · CRS missing/unexpected · out-of-bounds · overlaps · slivers · small gaps · original-vs-corrected diff.
Repairs (all logged: feature_id, check, action, before, after, reason, post_valid, applied)
make_valid (polygonal parts kept) · numeric text→number coercion · assign CRS if missing · optional: drop empty geoms, drop exact duplicates, trim overlaps below an area. Everything else is flag_only. The source file is never modified.
Usage
uv sync
uv run georescue inspect data.gpkg -c configs/columbia_fl.yaml
uv run georescue repair data.gpkg -c configs/columbia_fl.yaml -o out/
uv run georescue report data.gpkg -c configs/columbia_fl.yaml -o out/
uv run streamlit run app.py # demo UI (docs/demo.png)
uv run georescue-mcp # MCP stdio server: inspect_dataset, repair_dataset
PYTHONPATH=. uv run --extra verify pytest -qReal data: uv run python scripts/fetch_columbia.py (Columbia County FL LCParcels FeatureServer).
Known gaps
Gap detection uses holes in the unioned fabric (misses gaps open to the outside edge); overlap trimming is greedy (higher row loses); DuckDB batch mode not implemented; no map of issue geometries in the UI (points only); type rules don't parse unit-suffixed text (e.g. "3 Ac").
Automated vs. manual steps
Step | Status |
Inspect, classify, repair, change log, QA report | Automated ( |
RustGIS visualization loop | Automated ( |
Appraiser legal descriptions, PLSS corner tie (BLM CadNSDI) | Automated ( |
Fetching recorded deed images (myfloridacounty.com ORI) | Manual today: portal sits behind a human-verification check |
Deed OCR, metes-and-bounds + curve parsing, COGO traverse, closure and GIS comparison | Automated ( |
Final boundary position within ~3 ft | Needs a licensed surveyor |
Deed PDFs, page images, and raw county data are excluded from the repo.
Credits
See THIRD_PARTY_NOTICES.md for open-source licenses and data sources, and Data sources below. Brand font: Exo 2 (SIL Open Font License, brand/fonts/OFL.txt).
Live demo
Static dashboard (GitHub Pages): https://knightchrism.github.io/georescue/
KPIs per check, filterable issues table, Leaflet map of flagged parcels only (small GeoJSON, not the 584 MB county layer), per-overlap case files (verdict, confidence, ORB refs, deed closure/acreage, overlay PNGs) and run history.
Basemap: OpenStreetMap tiles. The COJ Duval orthoimagery has no published licence, so imagery-backed figures are not published; case pages use the plain (no-imagery) overlay PNGs.
PYTHONPATH=. uv run --extra verify georescue run --config configs/duval_fl.yaml # -> out/runs/<ts>/, out/latest/
PYTHONPATH=. uv run --extra verify georescue publish # -> site/
python -m http.server -d site 8765 # preview locallyAutomation: .github/workflows/pipeline.yml (weekly cron + manual dispatch) runs the pipeline on a bbox extract
(configs/duval_fl_ci.yaml), fetching parcels at runtime, and deploys site/ to Pages.
To enable: push the repo to GitHub, then Settings → Pages → Source: GitHub Actions, and allow Actions under Settings → Actions.
Only invalid-geometry repair is ever auto-applied; every other fix is a proposal recorded in changelog.csv.
Data sources
GeoRescue does not own the data below and is not affiliated with, or endorsed by, any of these sources. Their records are maintained for their own purposes (for example, assessment) and, as the Property Appraiser states for its data, are not intended for legal use such as conveyances or boundary determinations.
City of Jacksonville GIS — parcels (CityBiz/Parcels service): https://maps.coj.net/coj/rest/services/CityBiz/Parcels/MapServer/0 · home/disclaimer: https://maps.coj.net/
Duval County Property Appraiser: https://paopropertysearch.coj.net/Basic/Search.aspx (disclaimer shown on the search site)
Duval County Clerk of Courts — Official Records: https://or.duvalclerk.com · disclaimer: https://www.duvalclerk.com/disclaimer
Owner and person names are removed from the public site (georescue publish redacts by default; --no-redact-owners is for private local builds only).
Ask GeoRescue (MCP server)
georescue load-db loads the latest run into a redacted DuckDB results store, out/georescue.duckdb. It holds the tables issues, cases, verdicts, deed_traverses, runs and glossary, and it never contains owner names. georescue run refreshes it automatically. The MCP server (uv run --extra verify georescue-mcp, stdio) exposes these tools:
inspect_dataset, repair_dataset (writes a repaired copy into a new folder only), list_tables, describe_table, run_query (single SELECT/WITH, guard + row cap + 10 s timeout), list_metrics/get_metric (governed metrics in semantic/metrics.yml), get_case, find_issues, explain_issue and compare_runs. All calls are logged to logs/mcp.log.
scripts/mcp_demo.py drives the server over stdio through realistic questions and records the real calls and outputs to examples/agent_sessions.{json,md}. The site's Ask GeoRescue page renders those sessions. Each answer is filled in by a fixed template from the tool outputs. The page also has Claude Desktop / Cursor config snippets for running it yourself. These are recorded sessions and test results, not authoritative.
The server structure, SQL guard, metrics layer, logging and demo are adapted from the author's own census-pipeline. GeoRescue keeps its existing MCP SDK (mcp>=2.3, MCPServer).
Glossary
The site's glossary (generated by georescue publish from src/georescue/glossary.py and the config thresholds) explains every issue type the checks emit — what it means, why it matters, how it is detected, what (if anything) is done automatically — plus terms like verdict, confidence, deed traverse/COGO, misclosure, POB, ORB, IoU and PAO. All results are proposed test results, not authoritative.
Terms
See TERMS.md. Questions, corrections or removal requests: open an issue at https://github.com/knightchrism/georescue/issues
License
Copyright (c) 2026 GeoKnight GIS. All rights reserved. No copying or reuse without written permission; see LICENSE. Third-party libraries and data keep their own licenses and terms (listed in LICENSE and THIRD_PARTY_NOTICES.md).
Available Tools
11 toolscompare_runsB
Compare issue counts by check between two runs (default: the two most recent in the runs table).
Inputs: run_a, run_b.
describe_tableC
Columns and types of a results-store table, e.g. 'issues' or 'cases'.
Inputs: table (required).
explain_issueA
Plain-English explanation of an issue type or site term (e.g. 'sliver_polygon', 'closure', 'iou'), with the detection thresholds used, the automatic action and typical causes.
Inputs: check (required).
find_issuesB
Filter issues in the latest run. bbox = [min_lon, min_lat, max_lon, max_lat] (EPSG:4326). Returns the total
match count and up to limit rows (max 500).
Inputs: bbox, check, limit, severity, +1 more.
get_caseA
One case file by case_id (e.g. '0015420010__0015315300') or by a parcel ID (e.g. '001542 0010'): the proposed verdict, confidence, ORB refs, deed check (closure, IoU) and the parcel's issues.
Inputs: case_id, parcel_id.
get_metricB
Compute a governed metric from semantic/metrics.yml. Returns rows, the SQL used and caveats.
Inputs: name (required), group_by.
inspect_datasetB
Inspect a parcel dataset (read-only). Filter issues by check name(s) and severity(ies), page with limit/offset, and set include_wkt to get each issue's geometry (working CRS WKT).
Inputs: path (required), check, limit, offset, +3 more.
list_metricsA
List governed metrics (name, label, unit, description, allowed group_by).
Inputs: no named parameters. Returns: result
list_tablesA
List tables in the GeoRescue results store (latest run, owner names redacted).
Inputs: no named parameters. Returns: result
repair_datasetA
Write a repaired COPY of the dataset plus changelog into a NEW folder (a proposal output). Never modifies the input; refuses an out_dir that is the input's folder or already contains files.
Inputs: path (required), out_dir (required), config_path.
run_queryA
Run ONE read-only SELECT/WITH query on the results store. Capped (default 100, max 500 rows), 10 s timeout. Quote the column "check" (a keyword).
Inputs: sql (required), max_rows.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
A read-only verified record of agent-operable GTM tools: search, fetch, compare, track changes.
Astra DB tools for agents: schema, find, vector search, guarded writes, and interactive views.
Runtime permission, approval, and audit layer for AI agent tool execution.
Bounded tools for rendering, extraction, RAG, enrichment, local discovery and review analysis.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables 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 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
- AlicenseAqualityCmaintenanceEnables 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.4MIT