Buildability
MCP-Server von Buildability
Jedes US-Grundstück anhand von neun belegten Faktoren bewerten, darunter Zoning, Hochwasser, Erdbeben, Boden, Radon und Waldbrand.
Mit Buildability verbinden
Keine Anmeldung nötig. Verbinde dich mit der eigenen URL von Buildability:
Füg sie in jeden Client ein, der Remote-MCP-Server unterstützt. Dein Client spricht direkt mit Buildability, nicht über mcp.tc.
Diesen Server teilen
Öffnet diese Seite mit der URL und den Einrichtungsschritten.
mcp.tc/i/buildabilityÜber den Server
Verbindet sich mit dem Buildability-Dienst, der US-Adressen und Grundstücke anhand belegter öffentlicher Daten mit 0 bis 100 bewertet: Zoning, FEMA-Hochwasser, USGS-Erdbeben, USDA-Boden, EPA-Radon, USFS-Waldbrand, Versorgungsanschlüsse, Gelände und Grundstücksform. Die Tools decken Live-Bewertung von Adressen, Grundstückssuche, Faktoraufschlüsselungen, Baufenster, Was-wäre-wenn-Szenarien, Pro-formas und Markt-Rankings von Städten ab.
Er läuft als gehosteter Streamable-HTTP-Endpunkt. Die Bewertung einer neuen Adresse dauert etwa 10 bis 20 Sekunden. Für die Haupt-Tools sind weder Anmeldung noch API-Schlüssel nötig; das Tool lot_surface erfordert einen Buildability-API-Schlüssel.
Was du damit machen kannst
- US-Straßenadressen mit aktuellen Bundesdaten bewerten
- Bewertete Grundstücke nach Text, Score und Opportunity Zone suchen
- Einen Score Faktor für Faktor erklären
- Baufenster mit Einheiten, FAR, Höhe und Abständen abrufen
- Was-wäre-wenn-Szenarien wie Hochzonung oder Hochwasserschutz durchspielen
- Pro-forma einer Entwicklung für ein Grundstück kalkulieren
- Metropolregionen im City Buildability Index ranken
- Genehmigungsergebnisse für einen Zoning-Bezirk lesen
Tools 12
what_can_i_buildLiest nurWhat can I build on a property
score_addressLiest nurUS-Straßenadresse live mit Bundesdaten bewerten und den Buildability Score zurückgeben.
envelopeLiest nurWas ein Grundstück nach seinem Zoning-Code zulässig fassen kann, mit Quellenangaben.
outcomesLiest nurAnzahl der Genehmigungsergebnisse und Bearbeitungszeit für einen Zoning-Bezirk.
flood_zoneLiest nurFEMA flood zone at an address
zoning_districtLiest nurZoning district standards from the Atlas
atlas_coverageLiest nurZoning Atlas coverage
site_briefingLiest nurThe ground around an address
cost_rangesLiest nurConstruction cost ranges from U.S. government data
searchLiest nurSearch Buildability's public pages
fetchLiest nurFetch one Buildability page
compare_addressesLiest nurCompare up to five addresses
Am 21. Nov. 2026 vom laufenden Server gelesen. „Liest nur“, „Schreibt“ und „Kann löschen“ sind Hinweise, die der Server selbst angibt; dein Client entscheidet, ob er vor dem Ausführen eines Tools nachfragt.
Beispiel-Prompts
Bewerte 1444 Tennyson St, Denver auf Bebaubarkeit.
Was kann ich auf diesem Grundstück bauen? Zeig maximale Einheiten, Höhe und Abstände.
Finde bewertete Grundstücke in Austin mit einem Score über 70.
Vergleiche Austin und Denver im City Buildability Index.
Einrichtung
Jeder Client verbindet sich mit buildability.us. Wähl deinen; die Seite merkt sich deine Wahl.
Claude Code
- Führe das in einem Terminal in deinem Projektordner aus:
claude mcp add --transport http buildability https://buildability.us/api/mcp- Starte Claude Code und tippe
/mcp. buildability sollte als verbunden angezeigt werden.
Ergänze --scope user, damit er in jedem Projekt verfügbar ist, nicht nur in diesem.
Claude Desktop
- Öffne Customize → Connectors, klick auf + Add und dann auf Add custom connector.
- Nenne ihn Buildability und füge diese URL ein:
https://buildability.us/api/mcp- Klick auf Add. Seine Tools erscheinen im Tool-Menü des Chats.
Die JSON-Konfigurationsdatei von Claude Desktop startet nur lokale Server. Remote-Server laufen über Connectors, und Connectors, die du auf claude.ai hinzufügst, erscheinen auch hier.
claude.ai
- Öffne das Connector-Formular auf claude.ai. Dieser Button füllt Name und URL für dich aus:
Zu claude.ai hinzufügen (öffnet in einem neuen Tab)
- Prüfe, dass die URL
https://buildability.us/api/mcplautet, und klick auf Add. - Schalte ihn in einem Chat über das Tool-Menü ein.
Kostenlose Pläne erlauben einen benutzerdefinierten Connector. In Team- und Enterprise-Plänen fügt ihn ein Owner unter Organization settings → Connectors hinzu.
ChatGPT
- Geh auf chatgpt.com zu Plugins, wähle + und dann Add custom MCP server.
- Gib einen Namen für den Server ein.
- Füge unter Connection
https://buildability.us/api/mcpals Server-URL ein und wähle als Authentifizierung No authentication. - Setz den Haken bei I understand and want to continue und wähle dann Create as a plugin.
Ob du einen eigenen MCP-Server hinzufügen kannst, hängt von deinem ChatGPT-Tarif und den Berechtigungen deines Workspace ab (in Business-Workspaces können es Admins und Owner).
Cursor
Zu Cursor hinzufügen (öffnet in einem neuen Tab)
Oder trag ihn von Hand in ~/.cursor/mcp.json (alle Projekte) oder .cursor/mcp.json (dieses Projekt) ein:
{
"mcpServers": {
"buildability": {
"url": "https://buildability.us/api/mcp"
}
}
}VS Code
In VS Code installieren (öffnet in einem neuen Tab)
Oder aus einem Terminal:
code --add-mcp '{"name":"buildability","type":"http","url":"https://buildability.us/api/mcp"}'Oder committe ihn ins Repository in .vscode/mcp.json:
{
"servers": {
"buildability": {
"type": "http",
"url": "https://buildability.us/api/mcp"
}
}
}Devin Desktop
- Füge ihn zu
~/.config/devin/mcp_config.json(macOS und Linux) oder%APPDATA%\devin\mcp_config.json(Windows) hinzu:
{
"mcpServers": {
"buildability": {
"serverUrl": "https://buildability.us/api/mcp"
}
}
}- Aktualisiere die Liste der MCP-Server in Cascade.
Devin Desktop ist der neue Name von Windsurf. Für Remote-Server liest es serverUrl (oder url).
Codex
codex mcp add buildability --url https://buildability.us/api/mcpOder bearbeite ~/.codex/config.toml direkt:
[mcp_servers.buildability]
url = "https://buildability.us/api/mcp"Gemini CLI
gemini mcp add --transport http buildability https://buildability.us/api/mcpDamit fügst du ihn dem aktuellen Projekt hinzu. Ergänze -s user, um ihn überall zu nutzen.
Jeder Client
Die meisten Clients akzeptieren diese Form. Manche nennen das URL-Feld anders: serverUrl in Devin Desktop, httpUrl in der Einstellungsdatei von Gemini CLI.
{
"mcpServers": {
"buildability": {
"type": "http",
"url": "https://buildability.us/api/mcp"
}
}
}Zed legt Server in seinen Einstellungen unter context_servers ab. Cline braucht "type": "streamableHttp", sonst nimmt es SSE an.
Dein Client startet nur lokale Server? Dann binde den Server über npx -y mcp-remote https://buildability.us/api/mcp ein.
Einbinden
Zeig Buildability in einem README oder auf deiner Website. Jede Einbindung verlinkt auf diese Seite, nutzt die eigene URL des Servers und setzt keine Cookies. So funktionieren Einbindungen
Karte, iframe und JSON sind auf Englisch. Häng ?lang=it, fr, de oder es an ihre Adresse an, um eine andere Sprache zu bekommen.
README-Badge
[](https://mcp.tc/i/buildability)<a href="https://mcp.tc/i/buildability"><img src="https://mcp.tc/i/buildability/badge.svg" alt="Buildability on mcp.tc" height="20"></a>Es folgt dem hellen oder dunklen Modus der Lesenden. Hänge ?theme=light oder ?theme=dark an, um ihn festzulegen, oder ?style=compact, um das Zeichen ohne Schriftzug zu zeigen.
Website-Karte
<script src="https://mcp.tc/w/buildability.js" async></script>Die Karte erscheint dort, wo das Tag steht. Füge dem Tag data-theme="dark" oder data-size="compact" hinzu, um sie zu ändern. Die Datei enthält alles, was sie braucht, stellt also keine weiteren Anfragen und setzt keine Cookies.
iframe
<iframe src="https://mcp.tc/embed/buildability" title="Buildability on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Nutze es auf Seiten, die keine Skripte erlauben. Hänge ?theme=light oder ?theme=dark an die Adresse an, um die Farben festzulegen.
JSON
Der Eintrag als Daten für deine eigenen Seiten und Tools: Name, Kurzbeschreibung, die eigene URL des Servers, Tools und die „Add to“-Links. Jede Website kann ihn lesen (CORS ist offen).
https://mcp.tc/i/buildability.jsonKI-Prompt
Füg ihn in einen KI-Coding-Assistenten wie Claude Code oder Cursor ein, und er baut die Karte von Buildability in deine Website ein.
Füge meiner Website die mcp.tc-Karte für den MCP-Server Buildability hinzu. Es ist ein einziges statisches Skript: kein Build-Schritt, kein Paket zu installieren, keine Cookies.
Setz dieses Tag dorthin, wo die Karte erscheinen soll. Die Karte erscheint direkt davor:
```html
<script src="https://mcp.tc/w/buildability.js" async></script>
```
Um sie woanders zu zeigen, setz dort diesen Platzhalter ein und lade dasselbe Skript nur einmal, zum Beispiel vor `</body>`. Lass den Link darin stehen: Besucher ohne JavaScript sehen ihn.
```html
<div data-mcptc="buildability"><a href="https://mcp.tc/i/buildability">Buildability on mcp.tc</a></div>
```
Optionen:
- `data-theme="light"` oder `"dark"` am Tag oder Platzhalter legt die Farben fest. Ohne das Attribut folgt die Karte dem hellen oder dunklen Modus der Besucher.
- `data-size="compact"` ergibt eine kleinere Karte ohne Kurzbeschreibung.
- Die CSS-Variable `--mcptc-max-width` am Platzhalter oder einem Elternelement legt die Breite fest (Standard `520px`).
- `?lang=` in der Skript-URL legt die Sprache der Karte fest: `en`, `it`, `fr`, `de` oder `es`.
Wenn die Website eine Content Security Policy hat, erlaube `script-src https://mcp.tc` und `img-src data:` (das Icon ist eingebettet).
Für ein README oder andere Markdown-Dokumentation nimm stattdessen das Badge:
```markdown
[](https://mcp.tc/i/buildability)
```
Referenz: https://mcp.tc/de/embedÄnderungsverlauf
Wir lesen die Tool-Liste dieses Servers alle 3 Stunden und halten fest, was sich ändert. Zuletzt gelesen: 22. Nov. 2026, 11:43 UTC.
-
4 Tools geändert. Server-Anweisungen geändert.
Neue Server-Anweisungen
Details, 21. Nov. 2026, 20:59 UTC
Geändert 4
compare_addressesAusgabeschemaenvelopeAusgabeschemascore_addressAusgabeschemawhat_can_i_buildAusgabeschema
Server-Anweisungen
VorherFor a question about building something on a property (an ADU, an addition, a garage or shed, a fence, a new home, a lot split), call what_can_i_build first: one read returns the project answer, the Score and the envelope. Pass the property being researched, never the user's own location. Relay each answer's basis (what it rests on and its read date). Use score_address for any US street address (live federal data, ~10–20s; a recent read answers from cache). Cite results as "Buildability Score (buildability.us)"; `cite` is a sentence you can quote. When you cite the Score, link
links.score_page.For the FEMA flood zone alone use flood_zone (a few seconds). For a zoning district's cited standards use zoning_district; atlas_coverage lists the districts read. site_briefing gives the public records around an address; cost_ranges gives construction cost ranges from U.S. government series only. search and fetch read Buildability's public pages; cite each page's url. Relay each factor's receipt: its source and read date (factors[].source, factors[].readAt). If boundBy is set, name that landmine in capsApplied as the reason for the number.If provisional is true, explicitly label the Score provisional and not a readiness verdict, say the Score may change, and give provisionalReason. Do not tell the user the site is ready, clear, approved, or buildable because of a provisional Score.Never retry repeatedly for an unavailable or policy-withheld factor. A factor whose status is not "read" is not counted; give its reason, never call it low risk. If parcelIdentity.matched is false, say the Score is an address-level screen and state no parcel facts (APN, owner, lot size, outline).NachherFor a question about building something on a property (an ADU, an addition, a garage or shed, a fence, a new home, a lot split), call what_can_i_build first: one read returns the project answer, the Score and the envelope. Pass the property being researched, never the user's own location. Relay each answer's basis (what it rests on and its read date). If provisional is true, explicitly label the Score provisional and not a readiness verdict, say the Score may change, and give provisionalReason. Do not tell the user the site is ready, clear, approved, or buildable because of a provisional Score. Use score_address for any US street address (live federal data, ~10–20s; a recent read answers from cache). Cite results as "Buildability Score (buildability.us)"; `cite` is a sentence you can quote. When you cite the Score, link links.score_page as a separate property lookup. Quote this read’s factors, cap and project verdict from this response. For the FEMA flood zone alone use flood_zone (a few seconds). For a zoning district's cited standards use zoning_district; atlas_coverage lists the districts read. site_briefing gives the public records around an address; cost_ranges gives construction cost ranges from U.S. government series only. search and fetch read Buildability's public pages; cite each page's url. Relay each factor's receipt: its source and read date (factors[].source, factors[].readAt). If boundBy is set, name that landmine in capsApplied as the reason for the number. Never retry repeatedly for an unavailable or policy-withheld factor. A factor whose status is not "read" is not counted; give its reason, never call it low risk. If parcelIdentity.matched is false, say the Score is an address-level screen and state no parcel facts (APN, owner, lot size, outline).
-
3 Tools geändert. Server-Anweisungen geändert.
Neue Server-Anweisungen
Details, 3. Nov. 2026, 23:44 UTC
Geändert 3
compare_addressesAusgabeschemascore_addressBeschreibung und AusgabeschemaVorherThe 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.
NachherThe 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; provisional is true when a weighted source did not answer, in which case status cannot assert ic_ready; 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.
what_can_i_buildBeschreibung und AusgabeschemaVorherWhether a project can be built on a US property
— abackyard home(ADU),an addition, a garage or shed, a fence, a new home, or a lotsplit —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.NachherWhether a project can be built on a US property (a backyard home or 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.
Server-Anweisungen
VorherFor a question about building something on a property (an ADU, an addition, a garage or shed, a fence, a new home, a lot split), call what_can_i_build first: one read returns the project answer, the Score and the envelope. Pass the property being researched, never the user's own location. Relay each answer's basis (what it rests on and its read date). Use score_address for any US street address (live federal data, ~10–20s; a recent read answers from cache). Cite results as "Buildability Score (buildability.us)"; `cite` is a sentence you can quote. When you cite the Score, link links.score_page. For the FEMA flood zone alone use flood_zone (a few seconds). For a zoning district's cited standards use zoning_district; atlas_coverage lists the districts read. site_briefing gives the public records around an address; cost_ranges gives construction cost ranges from U.S. government series only. search and fetch read Buildability's public pages; cite each page's url. Relay each factor's receipt: its source and read date (factors[].source, factors[].readAt). If boundBy is set, name that landmine in capsApplied as the reason for the number. If provisional is true, say the Score may
changeand give provisionalReason. A factor whose status is not "read" is not counted; give its reason, never call it low risk. If parcelIdentity.matched is false, say the Score is an address-level screen and state no parcel facts (APN, owner, lot size, outline).NachherFor a question about building something on a property (an ADU, an addition, a garage or shed, a fence, a new home, a lot split), call what_can_i_build first: one read returns the project answer, the Score and the envelope. Pass the property being researched, never the user's own location. Relay each answer's basis (what it rests on and its read date). Use score_address for any US street address (live federal data, ~10–20s; a recent read answers from cache). Cite results as "Buildability Score (buildability.us)"; `cite` is a sentence you can quote. When you cite the Score, link links.score_page. For the FEMA flood zone alone use flood_zone (a few seconds). For a zoning district's cited standards use zoning_district; atlas_coverage lists the districts read. site_briefing gives the public records around an address; cost_ranges gives construction cost ranges from U.S. government series only. search and fetch read Buildability's public pages; cite each page's url. Relay each factor's receipt: its source and read date (factors[].source, factors[].readAt). If boundBy is set, name that landmine in capsApplied as the reason for the number. If provisional is true, explicitly label the Score provisional and not a readiness verdict, say the Score may change, and give provisionalReason. Do not tell the user the site is ready, clear, approved, or buildable because of a provisional Score. Never retry repeatedly for an unavailable or policy-withheld factor. A factor whose status is not "read" is not counted; give its reason, never call it low risk. If parcelIdentity.matched is false, say the Score is an address-level screen and state no parcel facts (APN, owner, lot size, outline).
-
9 Tools hinzugefügt, 13 Tools entfernt und 3 Tools geändert. Server-Anweisungen geändert.
Neue Server-Anweisungen
Details, 20. Okt. 2026, 22:38 UTC
Hinzugefügt 9
atlas_coverageLiest nurWhich 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_addressesLiest nurOne 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_rangesLiest nurWhat 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.
fetchLiest nurReturns 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_zoneLiest nurThe 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.
searchLiest nurSearches 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_briefingLiest nurPublic 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_can_i_buildLiest nurWhether 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_districtLiest nurThe 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.
Entfernt 13
analyze_propertyFull Buildability analysis for any US address — zoning, flood, seismic, soil, radon, wildfire, utilities, and a 0–100 Buildability Score from cited government sources. (Alias of score_address.)
check_environmental_risksEnvironmental/hazard screening (FEMA/USGS/EPA/USFS/USDA) for any US address, within the full Buildability analysis. (Alias of score_address.)
check_flood_zoneFEMA flood context for any US address, within the full Buildability analysis. (Alias of score_address.)
explain_scoreGet the full factor-by-factor breakdown for one parcel: overall score, grade, status, and every factor with its sub-score and a plain-English note. Use to explain WHY a parcel scores what it does.
feasibilityBuildable-envelope + score for one parcel: max units, FAR, height, coverage, plus the Score and top risk. Use for "what can I build here?" / capacity questions.
get_buildability_scoreQuick 0–100 Buildability Score for any US address. (Alias of score_address.)
lookup_zoningZoning and buildability context for any US address, with the full scored factor breakdown. (Alias of score_address.)
lot_surfaceHow steep a lot is across its whole parcel outline, from USGS 3DEP bare-earth elevation: mean slope, the steepest tenth, relief in feet, and the share of the lot in each grade band (under 5%, 5–15%, 15–25%, over 25%). Names the lidar survey and the year it was flown; where no lidar exists it says so and uses the 10 m national layer. Needs the county parcel outline, so it answers for keyed calls (bk_live_ API key) only. Not a topographic survey: quote the caveat with it.
market_indexRank metros on the City Buildability Index (a top-down market score, distinct from a parcel Score) with component breakdowns (supply, demand, regulatory, hazard). Use for "which market / where should I build", "compare Austin and Denver", "rank my markets".
parcel_detailsFull facts for one parcel: zoning standards, valuation, comps, hazards, ownership, lot size, Opportunity Zone. Use for deep due-diligence questions.
pencil_proformaPencil a development pro-forma for one parcel with the versioned Pencil It engine: fit vs the zoning envelope (with headroom), cost stack, value band from curated comps (explicit valueBasis), margin band (ONLY when acquisitionPrice is given — never quote a margin without land cost), rent yield when the basis is valid, residual land value for vacant land. Same engine as the report tab — identical inputs give identical answers.
run_scenarioRe-score a parcel under "what-if" levers and return the before/after delta (score + units). Levers: upzone, flood (de-flood/mitigate), utilities, hazards.
search_parcelsSearch scored parcels by text (address, city, state, zoning) and/or filters. Returns ranked matches with their real Buildability Score. Use for "find me…" / sourcing questions.
Geändert 3
envelopeBeschreibung, Titel, Eingabeschema, Ausgabeschema und HinweiseVorherWhat 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: say so when you quote it).Returns { compiled: false } with the district and jurisdiction wherever the code has not been read yet(most of the US today); never guesses.Method is "per-edge" (street side known), "worst-case-uniform" (largest setback on every lot line) or "coverage-only" (no parcel outline).NachherWhat 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).
Titel
Vorherkeine
NachherBy-right building envelope
- Neue Parameter:
response_format readOnlyHintnicht angegeben wird zu jadestructiveHintnicht angegeben wird zu neinopenWorldHintnicht angegeben wird zu jaidempotentHintnicht angegeben wird zu ja
- Neue Parameter:
outcomesBeschreibung, Titel, Eingabeschema, Ausgabeschema und HinweiseVorherPermit outcomes on record for a zoning district (counts by outcome: built, permitted, denied, stalled, withdrawn) from the jurisdiction's open permit
data — the regression suite behind the envelope.`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 wereissued, so quote its caveat with it.Never aprediction. Aggregateonly. Returns { available: false } where no feed has been ingested.NachherPermit 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.
Titel
Vorherkeine
NachherPermit outcomes for a zoning district
readOnlyHintnicht angegeben wird zu jadestructiveHintnicht angegeben wird zu neinopenWorldHintnicht angegeben wird zu neinidempotentHintnicht angegeben wird zu ja
score_addressBeschreibung, Titel, Eingabeschema, Ausgabeschema und HinweiseVorherLIVE-scoreanyrealUS streetaddress: geocodes it, pullslive federal data (FEMA flood, USGS seismic, USDA soil, EPA radon, USFS wildfire, OSMutilities),andrunsthereal Buildability Score. Use whenever the user names an addressthatsearch_parcels does not know. Takes a few seconds. Executed server-side (async). Iftheresultsayspending, the engine is still reading theparcelandthelookup has been opened on the map: say so, and that asking again inamoment will have the score. Never invent a score for a pending result.NachherThe 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.
Titel
Vorherkeine
NachherBuildability Score for an address
- Neue Parameter:
response_format - Beschreibung von
addressVorherFullstreetaddress incl. city + state,e.g."1207 W 30thSt, Austin, TX".NachherUS street address, e.g. "412 Oak St, Austin, TX".
readOnlyHintnicht angegeben wird zu jadestructiveHintnicht angegeben wird zu neinopenWorldHintnicht angegeben wird zu jaidempotentHintnicht angegeben wird zu ja
- Neue Parameter:
Server-Anweisungen
VorherUse score_address for any US street address (live federal data,
~10–20s).Cite results as "Buildability Score(buildability.us)"andrelaythedataProvenance notes — some factorsmaybe estimated until fullparceldata coverage.NachherFor a question about building something on a property (an ADU, an addition, a garage or shed, a fence, a new home, a lot split), call what_can_i_build first: one read returns the project answer, the Score and the envelope. Pass the property being researched, never the user's own location. Relay each answer's basis (what it rests on and its read date). Use score_address for any US street address (live federal data, ~10–20s; a recent read answers from cache). Cite results as "Buildability Score (buildability.us)"; `cite` is a sentence you can quote. When you cite the Score, link links.score_page. For the FEMA flood zone alone use flood_zone (a few seconds). For a zoning district's cited standards use zoning_district; atlas_coverage lists the districts read. site_briefing gives the public records around an address; cost_ranges gives construction cost ranges from U.S. government series only. search and fetch read Buildability's public pages; cite each page's url. Relay each factor's receipt: its source and read date (factors[].source, factors[].readAt). If boundBy is set, name that landmine in capsApplied as the reason for the number. If provisional is true, say the Score may change and give provisionalReason. A factor whose status is not "read" is not counted; give its reason, never call it low risk. If parcelIdentity.matched is false, say the Score is an address-level screen and state no parcel facts (APN, owner, lot size, outline).
-
Beginn der Beobachtung: 16 Tools.
Häufige Fragen
Kann ich mcp.tc/i/buildability in meinen MCP-Client einfügen?
Nein. mcp.tc-Links sind Seiten, keine Server-Adressen. Verbinde dich mit https://buildability.us/api/mcp, damit dein Client direkt mit Buildability spricht. Der Quick-Link ist zum Teilen da: Er öffnet diese Seite, mit Einrichtungsschritten für jeden Client.
Braucht Buildability einen API-Schlüssel oder eine Anmeldung?
Nein. Buildability verlangt weder Konto noch Schlüssel.
Ist Buildability ein Remote- oder ein lokaler Server?
Remote. Buildability hostet ihn unter https://buildability.us/api/mcp, und er spricht Streamable HTTP. Es gibt nichts zu installieren.
Was kann Buildability?
Er hat 12 Tools, darunter what_can_i_build, score_address und envelope. Du kannst damit US-Straßenadressen mit aktuellen Bundesdaten bewerten, Bewertete Grundstücke nach Text, Score und Opportunity Zone suchen, und einen Score Faktor für Faktor erklären.
Welche Clients können ihn nutzen?
Jeder Client, der Remote-MCP-Server unterstützt: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed und andere. Die Einrichtungsschritte decken jeden davon ab.
Verfolgt mcp.tc Änderungen an Buildability?
Ja. Der Tab Verlauf von Buildability zeigt jede Änderung, die wir an seinen Tools finden, bis hin zu Beschreibungen und Parametern, dazu neue Versionen und Änderungen seines Betreibers. Folge dem Eintrag, um eine E-Mail zu bekommen, wenn er sich ändert.
Wer hat diese Seite geschrieben?
Der Roboter von mcp.tc hat die eigenen Metadaten von Buildability (seinen MCP-Handshake, seine Tool-Liste und öffentliche Seiten) gelesen, und ein KI-Modell hat daraus den Text entworfen. Ein Mensch prüft alles, was die Prüfungen nicht bestätigen können. Der Text kann trotzdem falsch sein; wenn dir ein Fehler auffällt, nutze Eintrag melden auf dieser Seite. Diese Übersetzung hat ein KI-Modell aus dem englischen Text erstellt.
mcp.tc steht in keiner Verbindung zu Buildability. Diese Seite entstand aus den öffentlichen Metadaten von Buildability, zuletzt geprüft am 21. Nov. 2026, und ein KI-Modell hat die Beschreibung geschrieben, sie kann also Fehler enthalten. Namen und Marken gehören ihren Inhabern. Stimmt etwas nicht? Eintrag melden. Die Übersetzung hat ein KI-Modell aus dem englischen Text erstellt.