nyrezone-mcp
Related Servers
Alternatives to nyrezone-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI agents and developers to look up zoning, land-use, and development records for Gwinnett County, Georgia through five public read-only tools: resolving an address to its actual governing jurisdiction, searching and retrieving county zoning cases, fetching ordinance code sections, and listing jurisdictions. It exposes the same operations over a REST API so questions about setbacks, permits, and case histories can be answered from indexed source records rather than guesses.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access public NYC renter guides and neighborhood asking-rent data, and with scoped OAuth consent, read and manage a renter's apartment alerts, saved searches, tracked listings, and Housing Lottery application statuses. Public tools are read-only, while personal tools act only on the connected renter's account with write confirmations.MIT
- AlicenseAqualityCmaintenanceProvides AI access to Korea's land use planning, urban regulations, and permit information through natural language queries. It integrates tools for land analysis, regulation verification, and public notice scraping to prevent hallucinations in property-related AI applications.819MIT
- AlicenseAqualityDmaintenanceProvides Claude with access to NYC public property data including property details, sales history, comparable sales, tax benefits, and rent stabilization analysis using natural language.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to look up US and Canadian parcel records either by full address string or by lat/lon point, returning parcel number, owner, mailing address, land use, zoning, acreage, and boundary geometry. It can be run as a local stdio server or reached through a hosted gateway endpoint.201 npmMIT
- AlicenseAqualityDmaintenanceOpen-source MCP server providing real estate regulatory intelligence (zoning, permits, entitlements, deal scoring) for US properties, enabling AI agents to access 10 callable tools.128 npmMIT
TDQS
Scored across 3 tools
Each tool targets a distinct resource+action: enumerate district codes, fetch one district's detail, or resolve a single tax lot by address/BBL. The list_zoning_districts vs get_zoning_district pair is the classic list/detail split, and the descriptions explicitly contrast the one-line summary with the full HTML summary so misselection is unlikely.
All names are snake_case verb_noun (list_zoning_districts, lookup_lot, get_zoning_district), which is readable and predictable. The only minor deviation is mixing 'lookup' with 'get' for the two single-record fetches, though the different verbs usefully signal lookup-by-identifier vs fetch-by-code.
Three tools is lean but fits a narrow, read-only zoning reference service where each tool covers a clearly different lookup. It is slightly under what one might expect (e.g. no borough/neighborhood browse), but nothing feels redundant or padded.
The surface covers the core lifecycle for a reference server: list district codes, inspect a district's parameters, and resolve a parcel's recorded zoning. Gaps are minor-to-moderate — no spatial/coordinate lookup, no listing lots within a district, and no bulk queries — but agents can work around these by chaining the existing tools.