Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Buildability is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
12
tools declared
remote
at its publisher
—
calls last 7d
What it does
Source-cited, address-level answers on zoning, site constraints, permitting and what can be built.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http buildability-mcp https://buildability.us/api/mcp
# 2 — ask your agent for something these tools do
# what_can_i_build, score_address, envelope and 9 more
Buildability costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BUAll 1 server
buildability1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http buildability-mcp https://buildability.us/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 Bu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| property | string | yes | The property being researched, not the user's location: a US street address, e.g. "412 Oak St, Austin, TX". |
| project | string | no | The project to answer. Omit to answer every project. |
| response_format | string | no | "concise" (default) leaves out factor notes and verbatim code quotes; every number keeps its source and read date. "detailed" returns them. |
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 recor
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | US street address, e.g. "412 Oak St, Austin, TX". |
| response_format | string | no | "concise" (default) leaves out factor notes and verbatim code quotes; every number keeps its source and read date. "detailed" returns them. |
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 di
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | US street address, e.g. "412 Oak St, Austin, TX". |
| response_format | string | no | "concise" (default) leaves out factor notes and verbatim code quotes; every number keeps its source and read date. "detailed" returns them. |
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 ingeste
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jurisdiction | string | yes | City and state, e.g. "Austin, TX". |
| district | string | yes | Zoning district code, e.g. "SF-3". |
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 t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| property | string | yes | The property being researched: a US street address, e.g. "412 Oak St, Austin, TX". |
| response_format | string | no | "concise" (default) leaves out factor notes and verbatim code quotes; every number keeps its source and read date. "detailed" returns them. |
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 "p
| Parameter | Type | Required | Notes |
|---|---|---|---|
| city | string | yes | City name, e.g. "Austin". |
| state | string | yes | Two-letter state code, e.g. "TX". |
| district | string | yes | Zoning district code, e.g. "SF-3". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | no | Two-letter state code, e.g. "TX". Optional. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| property | string | yes | The property being researched: a US street address, e.g. "412 Oak St, Austin, TX". |
| response_format | string | no | "concise" (default) leaves out factor notes and verbatim code quotes; every number keeps its source and read date. "detailed" returns them. |
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, con
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | no | Two-letter USPS state code, e.g. "TX". Picks the Census division band. |
| sqFt | number | no | House size in square feet (200 to 50,000), for a total build range. |
| item | string | no | Narrow the answer, e.g. "lumber", "materials" or "build cost". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What to look for, e.g. "Austin SF-3 setbacks". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | An id from search, e.g. "district:austin-tx/sf-3". |
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 c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| properties | array | yes | One to five properties being researched: US street addresses, e.g. "412 Oak St, Austin, TX". |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Buildability or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 2.0.0 · scanned 1 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestac98a8dcc0a4165b040f83e2f8aeed96e949c22a647b15a436fdf0b073375b67
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| what_can_i_build | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| score_address | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| envelope | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| outcomes | no tags | |
| flood_zone | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| zoning_district | no tags | |
| atlas_coverage | no tags | |
| site_briefing | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| cost_ranges | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| search | no tags | |
| fetch | untrusted-input | untrusted-input: keyword "fetch" |
| compare_addresses | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestac98a8dcc0a4165b
Scanned2026-11-01
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.0.0.
2.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Buildability can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.