Find your next source.

Useful for

Use cases llm-inferred

Flood zone, permit and code-case screening for a site due-diligence note · Zoning, lot dimensions and municipal code text lookup for a pre-application brief · Tree-permit and roadway work-zone check before site clearance or access planning · Special-district (MUD/PID) and appraisal context for a development or drainage-authority brief

Audience llm-inferred

flood consultants · planners · civils engineers · GIS analysts

Limitations

Constraints llm-inferred

Austin, Texas and Travis, Williamson and Hays counties only; no UK data, so relevance to a UK consultancy is low, although the catalogue lists regions as Global · Early-stage project run by a single maintainer, so expect gaps and possible breaking changes · MLS data covers active and under-contract listings only, with no sold comps · Listings, neighbourhood and blog content depend on neuhausre.com and the Neuhaus VOW API · Socrata rate limits apply unless an app token is set · Commute tool uses demo routing servers with no real-time traffic · Catalogue auth field says an API key is required, but docs say no key is needed · Catalogue tool list does not match docs: docs state 43 tools and list austin_utility_providers, austin_relocation, austin_local_voices and austin_health, which are absent from the metadata, while the metadata lists health_check

Useful for

Use cases llm-inferred

Flood-zone constraint screening for a project area using fema_nfhl · Soil and farmland siting indicators for drainage or SuDS options using nrcs_soils · Species and critical-habitat screening for early ecological constraints using ipac · Composite constraints map of a project area for early site appraisal using map_composer

Audience llm-inferred

GIS analysts · flood consultants · ecologists · planners · civils and BIM engineers

Limitations

Constraints docs-verified

Screening and research aid only; does not make legal or agency determinations or replace agency or Tribal consultation · Does not guarantee that upstream datasets are complete or current · map_composer queries public GIS services at request time, so results depend on those services being available · census and epa_aqs return no data until their credentials are set

Example tool calls docs-verified

{
  "tool": "ipac",
  "arguments": {
    "roi": "<project-area geometry; parameter name not stated in DOCS>"
  }
}

Useful for

Use cases llm-inferred

Pre-acquisition screening of a site for flood, radon and zoning constraints · Planning-context scoping: nearby planning applications and zoning for a site appraisal · Sold-price context for a residential property in a feasibility or due-diligence note · Recorded-crime and BER area context as background in a property due-diligence brief

Audience llm-inferred

environmental consultants · flood risk consultants · planning consultants · property due-diligence analysts · GIS analysts

Limitations

Constraints docs-verified

Returns records only; not a valuation engine · Eircode-only lookup is not supported; an address or rough location is needed · River and coastal flood models are not included (licence-restricted; check floodinfo.ie) · Zoning is generalised land-use zoning (Myplan), not a detailed parcel-level designation · Recorded crime is area-level CSO counts, not incidents at an address; homicide and sexual offences are not published at sub-district level · Early release (v0.2.0); post-launch reliability and upstream-drift detection are active priorities · Requires Node.js 20+; running npx alone waits for an MCP client and appears to hang

Useful for

Use cases llm-inferred

Elevation sampling at site or boundary points to screen drainage and overland flow gradients · Static satellite or terrain maps of a study area with marked monitoring or sampling points for reports · Weather and forecast context for scheduling fieldwork such as sampling or ground investigation · Geocoding site addresses and building a travel-time matrix between survey points for field logistics

Audience llm-inferred

flood consultants · drainage engineers · hydrologists · ecologists · planners · GIS analysts · geotechnical engineers

Limitations

Constraints llm-inferred

Requires a Google Maps API key and billing-enabled Google Cloud account · Each Google API must be enabled separately; REQUEST_DENIED if not · Quota limits apply; OVER_QUERY_LIMIT when exceeded · Environmental APIs (air quality, solar, pollen, weather) are optional and may have different pricing · Requires Node.js 18+ and a local build (npm install, npm run build) · No UK-specific or hydrological data (river gauges, rainfall, flood maps); general-purpose mapping and environmental context only · Google pricing and quotas can change, so they must be checked before use

Useful for

Use cases llm-inferred

Nearest-station air quality baseline for a dust or emissions screening near a Yerevan site · Parcel and zoning lookup at a site coordinate for a Yerevan feasibility baseline · Mapping construction sites and permits in a district for cumulative-impact screening · Nearby bus stop and route check for transport access context

Audience llm-inferred

urbanists · planners · GIS analysts · civic-tech developers · environmental consultants

Limitations

Constraints llm-inferred

Covers Yerevan, Armenia only; not applicable to UK projects · No address geocoding; supply lon/lat or an Armenian street name · No routing or travel-time data · Live transit tools scrape Yandex via headless Chromium: fragile and subject to Yandex terms of use · Local stdio only; does not work in claude.ai, Cowork or mobile · Needs outbound access to gis.yerevan.am; depends on upstream portal availability and layer stability

Useful for

Use cases llm-inferred

Swiss site access and route appraisal using named hiking routes and elevation profiles · Public transport access check for Swiss field survey visits · Weather window forecasting at Swiss field survey sites for scheduling fieldwork

Audience llm-inferred

GIS analysts · planners · ecologists · field survey coordinators

Limitations

Constraints llm-inferred

Switzerland only; not applicable to UK sites · geo.admin.ch fair use is 20 requests/min on average · transport.opendata.ch has a soft, undocumented rate limit · Open-Meteo data requires CC BY 4.0 attribution · Commons Clause licence restricts selling the software; licence metadata reads Other · Windows binary is unsigned and may trigger SmartScreen; macOS needs a Gatekeeper workaround · Test suite stubs fetch with no committed fixtures; some behaviour was verified only with live probes during initial development · Hiking and weather data are not UK-relevant; not suited to the core UK water and civils workflows

Example tool calls docs-verified

{
  "tool": "forecast",
  "arguments": {
    "lat": 47.2494,
    "lon": 9.3434
  }
}

Useful for

Use cases llm-inferred

Geocode site and property addresses to coordinates for desk-based site assessments · Find nearby schools, hospitals and other receptors around a development site for sensitivity screening · Estimate driving and walking routes and times from a site to access points or facilities for transport appraisal

Audience llm-inferred

GIS analysts · planners · transport and highways consultants · civils engineers

Limitations

Constraints llm-inferred

Requires a Huawei Map Kit API key (authentication needed) · Coverage area and data quality are not documented; UK coverage is unverified · Rate limits and API quotas are not documented · Map Kit is a Huawei service, so its data sources and licensing terms for commercial use are not described in the docs · No spatial or temporal resolution or update frequency documented · Examples in the docs are Chinese-location focused

Example tool calls docs-verified

{
  "tool": "geocode",
  "arguments": {
    "address": "10 Downing Street, London"
  }
}