
Buildability MCP server
Which MCP servers are Buildability's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-31
- Registry nameus.buildability/mcpverified in the MCP registry
The registry name sits under buildability.us. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-31
- Tools12
- Server calls itselfbuildability
- Server version2.0.0
- Protocol version2025-06-18
On 2026-10-31 the server answered initialize and tools/list without a sign-in. First answer in 310 ms.
- Its tools do every use case we checked: check zoning, setbacks and height limits for a parcel; screen land deals for flood, seismic and wildfire risk.
- Checked on 5 of the 7 days it takes to judge reliability.
Once connected
- For "check zoning, setbacks and height limits for a parcel", the likely first call is envelope.
- For "screen land deals for flood, seismic and wildfire risk", the likely first call is score_address.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
- What an agent can do with it2 of 2 use cases
- Answeredmeasuring5 of the 7 daily checks it takes to print a share
- Median first answer564 ms
- Space in an agent's context≈ 2,619 tokensthe definitions of all its tools (12), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results12 of 12 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- can do · check zoning, setbacks and height limits for a parcel
- can do · screen land deals for flood, seismic and wildfire risk
- not sure · pull a cited parcel report for a lender or partner
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
what_can_i_buildWhether a project can be built on a US property — a backyard home (ADU), an addition, a garage or shed, a fence, a new home, or a lot split — from what the record says about its district: status (yes, yes with limits, no, depends, or…
score_addressThe Buildability Score for any US street address, from live federal data (FEMA flood, USGS seismic, USDA soil, EPA radon, USFS wildfire, OSM utilities): score, band, status and every factor the score reads, each with its status, sub-score…
envelopeWhat a lot can hold by right, from the letter of its zoning code applied to the real parcel outline: units, buildable floor area, height, floors, and setbacks. `sources` labels each number: "code" (its section, URL, read date and quote…
outcomesPermit outcomes on record for a zoning district (counts by outcome: built, permitted, denied, stalled, withdrawn) from the jurisdiction's open permit data. `time_to_issue` gives days from application to issue per kind of work, with the…
flood_zoneThe FEMA National Flood Hazard Layer zone at a US street address, read at the address point: zone, whether it is a Special Flood Hazard Area, zone subtype, floodway and base flood elevation where FEMA returns them, with the query URL and…
zoning_districtThe dimensional standards the Buildability Zoning Atlas has read for one zoning district (height, stories, dwelling units, lot size, width, depth and frontage, setbacks, floor-to-area ratio, coverage), each with its code section, source…
atlas_coverageWhich cities and zoning districts the Buildability Zoning Atlas has read and publishes, with each city's hub page, its districts and the newest read date. Pass `state` (two-letter code) to narrow it. Use zoning_district to read one…
site_briefingPublic records around a US street address: U.S. Drought Monitor status at the point; with a key, National Register of Historic Places listings on or within 150 m, and the nearest mapped power line, pipeline, rail line, motorway and…
cost_rangesWhat new construction costs, from U.S. government series only. With `state`: the middle half (25th to 75th percentile) of contract price per square foot for new contractor-built single-family houses in that Census division, lot excluded…
searchSearches Buildability's public pages: Zoning Atlas district pages (cited dimensional standards), city zoning source packs, the canonical product and methodology pages, and articles. Returns up to ten results, each with an `id` for fetch…
fetchReturns one page found by search, by its `id`, as text with its canonical URL and `read_date`: the date on its record (when the code or sources were read, or the page last changed). Cite the URL.
compare_addressesOne row per US street address, in the order given (never sorted by Score): Buildability Score, band, the landmine caps that bound it, FEMA flood zone at the address point, zoning district, and whether the district's dimensional standards…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"buildability": {
"type": "http",
"url": "https://buildability.us/api/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http buildability https://buildability.us/api/mcpclaude.ai, ChatGPT and other clients: add https://buildability.us/api/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.