RuralCheck MCP server
Related Servers
Alternatives to RuralCheck MCP server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceOfficial cadastral parcels from 29 European countries for AI agents: by reference in 27 and by coordinates in all 29, plus address search, outlines, neighbours, SIGPAC enclosures, terrain, ground motion, solar and agricultural potential and investment scores. Remote server at https://mcp.parcelgps.com/mcp (nothing to install) or npm catastro-gps-mcp. Free key: 250 calls/month.9358 npm1MIT
- AlicenseAqualityFmaintenanceEnables AI assistants to assess any parcel for micro-farm viability (climate, water, farmland context, access, flood risk) and dwelling feasibility, and to find real land for sale from free, keyless public data sources.51MIT
- AlicenseAqualityCmaintenanceEnables AI agents to perform due diligence on Irish properties by querying public datasets for planning applications, sold prices, flood risk, radon risk, and zoning.174 npm8MIT

Assetfy MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceEnables AI assistants to answer plain-language queries about official real estate data in Germany and Austria, covering cadastral parcels, zoning plans, land values, buildings, terrain, 3D models, aerial images, and property listings. Parcel and listing results link to map views with outlines, plans, buildings, and aerial imagery.MIT- AlicenseBqualityBmaintenanceAutonomous AI Agent compliance engine for EU Deforestation Regulation (EU 2023/1115). Verifies farm plot GIS polygons, Sentinel-2 satellite deforestation past 2020, VIES VAT, and generates official TRACES-NT DDS XML.41MIT
- AlicenseAqualityDmaintenanceAn MCP server that lets an AI agent run satellite land due-diligence through LandBenchmark. Its analyze_parcel tool takes a lat/lon or GeoJSON geometry and returns a green / caution / walk-away verdict with cited signals — flooding, slope, wildfire, road access, and more — for any parcel.121 npmMIT
TDQS
Scored across 20 tools
Most tools target distinct resources or lifecycle stages: plot management, folder management, uploads, checks/reports, and geography. The main potential overlap is find_place versus check_coverage, since find_place also returns `served`, but check_coverage is clearly framed as the analysis eligibility check. get_report, get_plot, and get_listing_upload are also separable by their resource names.
The set is predominantly consistent snake_case with a verb_noun pattern across CRUD and lifecycle tools: list_plots, get_plot, save_plot, update_plot, delete_plot, create_folder, etc. Minor deviations like sample_report and the plural-heavy list_listing_uploads are readable and do not undermine the overall convention.
At 20 tools, the surface is at the heavy end of the recommended range, partly because plot CRUD and folder CRUD are expanded into many individual operations. Each tool has a coherent role, but the count is borderline for the server's scope and could tempt consolidation.
Core workflows are well covered: place lookup, coverage checking, report analysis, report fetching, sample reports, upload progress, plot lifecycle including trash/restore, and folder CRUD. Minor gaps exist, such as no explicit upload cancellation or per-listing retry operation, but they are unlikely to block typical agent workflows.