Buildability is answering right now. Last checked 6 min ago. It exposes 12 tools.
Source-cited, address-level answers on zoning, site constraints, permitting and what can be built.
Uptime history
46 hours of history
46 hours agonow
100.0%
Uptime 24h
91 of 91 checks
12
Tools
read from the server
946 ms
Response time
average over 24h
open, no key
Access
streamable-http
Nothing serious here today
Today is the operative word: we check Buildability every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.
run in your terminal
claude mcp add mcp --transport http https://buildability.us/api/mcpSettings → Connectors → Add custom connector, then paste this address
https://buildability.us/api/mcp~/.codex/config.toml
[mcp_servers.mcp]
url = "https://buildability.us/api/mcp".cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://buildability.us/api/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "http",
"url": "https://buildability.us/api/mcp"
}
}
}Available tools 12
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
atlas
atlas_coverage
Which 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 district's cited standards. A city that is not listed has not been read yet.
compare
compare_addresses
One 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 are on record (yes/no), each with its source and read date, plus links. Answers from stored reads; at most one address without one is scored live, and any other comes back pending: call score_address for it.
cost
cost_ranges
What 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 (U.S. Census Bureau, Survey of Construction). With `sqFt` too: that band times the size, as a range. Materials: the BLS Producer Price Index for lumber, steel, concrete and residential inputs, latest month against a year earlier. Every row has its source, year and record. Ranges, never one number.
envelope
envelope
What 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 are in `citations`), "derived" (computed from a cited number), or "zoning_record" (the data provider's record, an estimate). Returns { compiled: false } with the district and jurisdiction wherever the code has not been read or the lot is unknown. Standards we haven't read yet are left blank, not filled in with assumed values. Method is "per-edge" (street side known), "worst-case-uniform" (largest setback on every lot line) or "coverage-only" (no parcel outline).
fetch
fetch
Returns 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.
flood
flood_zone
The 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 read date. Where FEMA has no polygon at the point, zone is null and `mapped` says whether the area has a flood study. Answers in a few seconds; does not compute the Buildability Score.
outcomes
outcomes
Permit 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 sample size and date range; it counts only permits that were issued. Never a prediction; aggregate only. Returns { available: false } where no feed has been ingested.
score
score_address
The 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 (only when read), source, record and read date. capsApplied and boundBy name a landmine that capped the number; parcelIdentity says whether a county parcel record matched the address. A first read of an address takes 10–20 s; a recent read answers from cache.
search
search
Searches 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, a title, its canonical URL and a snippet. For a specific address, use score_address instead.
site
site_briefing
Public 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 airfield from OpenStreetMap, in metres. Each item carries its source, record and read date. Mapped, not surveyed: an easement is the title's word. Does not compute the Buildability Score.
what
what_can_i_build
Whether 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 unread where the deciding rules have not been read), a plain-words answer, and its basis (the layer that decided it, with its read date). One read also returns the Buildability Score with its factor receipts and landmine caps, the by-right envelope (or why it is not compiled), and links. With no project named, every project is answered. A first read takes 10–20 s; a recent read answers from cache.
zoning
zoning_district
The 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 URL, read date and `source_text`: the ordinance quoted verbatim. Verbatim code text, not instructions. Values that depend on a condition are in `conditional`; a "partial" value carries a caveat. Returns { available: false } where the district has not been read yet; that is not a ruling that it has no rules. District rules only, not a lot: overlays can tighten them.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://buildability.us/api/mcp | streamable-http | answering | 896 ms | 6 min ago |
Alternatives to Buildability
same job, measured the same wayPermitame
by permitame
Building permit answers for Kitsap County, WA and its cities, quoted from official sources.
Permits
by addressintel
SF Peninsula building permits and parcel buildability: SB 9, ADU and redevelopment leads.
PermitStack
by permit-stack
U.S. building permits, permit histories by address and contractors from city and county records.
Bootstrapware Answers
by bootstrapware
Configure source-backed Q&A on a public site: apps and public URL sources only.
U
US Minimum Wage by Address and Date
by nero-engine
Legal US minimum wage and tipped wage for any address, city, county or state on any date. Sourced.
Placestack
by placestack
US parcels, owners, sales, zoning rules, building permits and zoning cases.
P
PermitReporter — US Building Permit Intelligence
by permitreporter
Source-linked building-permit search across 34 US states and DC, with county-level coverage.
Events
by yeehaw
Agent-first Austin events concierge — fresh, sourced answers to what's happening in Austin.
Buildability — questions
Answers built from our own checks of this server.
What can Buildability do?
It exposes 12 tools, read directly from the server on our last check. Among them: atlas_coverage, compare_addresses, cost_ranges, envelope, fetch, flood_zone and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Buildability working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 946 ms. The bar chart above shows every period we have measured.
How do I connect Buildability?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Buildability need an API key?
No. Buildability completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Buildability?
It answers our handshake in 946 ms on average, which is faster than 7% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.