Nous et des tiers sélectionnés utilisons des cookies ou des technologies similaires à des fins techniques et, avec votre consentement, pour analyser l’utilisation du site.

Vous pouvez librement donner, refuser ou retirer votre consentement à tout moment.

Buildability

Serveur MCP par Buildability

Évaluer n’importe quelle parcelle américaine selon neuf facteurs sourcés, dont zonage, inondation, sismicité, sol, radon et incendie, pour savoir ce qui peut y être construit.

Sans compte (Ni compte ni clé nécessaires)Streamable HTTP

Connecter Buildability

Aucun compte nécessaire. Connectez votre client à l’URL de Buildability :

https://buildability.us/api/mcp

Collez-la dans n’importe quel client compatible avec les serveurs MCP distants. Votre client parle directement à Buildability, sans passer par mcp.tc.

Partager ce serveur

Ouvre cette page, avec l’URL et les étapes de configuration.

mcp.tc/i/buildability

Présentation

Se connecte au service Buildability, qui note de 0 à 100 des adresses et parcelles américaines à partir de données publiques sourcées : zonage, inondation FEMA, sismicité USGS, sol USDA, radon EPA, incendie USFS, réseaux, relief et forme du terrain. Les outils couvrent l’évaluation d’adresse en direct, la recherche de parcelles, le détail par facteur, les enveloppes constructibles, les scénarios hypothétiques, les pro-formas et les classements de marchés urbains.

Il fonctionne comme un endpoint Streamable HTTP hébergé. L’évaluation d’une nouvelle adresse prend environ 10 à 20 secondes. Aucun compte ni clé API n’est nécessaire pour les principaux outils ; l’outil lot_surface requiert une clé API Buildability.

Ce que vous pouvez faire

  • Évaluer n’importe quelle adresse postale américaine avec des données fédérales en direct
  • Rechercher des parcelles évaluées par texte, note et Opportunity Zone
  • Expliquer une note facteur par facteur
  • Obtenir l’enveloppe constructible : logements, FAR, hauteur, retraits
  • Exécuter des scénarios hypothétiques comme le changement de zonage ou l’atténuation des inondations
  • Établir un pro-forma de développement pour une parcelle
  • Classer les métropoles selon le City Buildability Index
  • Consulter les résultats de permis d’un district de zonage

Outils 12

  • what_can_i_buildLecture seule

    What can I build on a property

  • score_addressLecture seule

    Évaluer en direct une adresse postale américaine avec des données fédérales et renvoyer le Buildability Score.

  • envelopeLecture seule

    Ce qu’un terrain peut accueillir de plein droit selon son code de zonage, avec citations.

  • outcomesLecture seule

    Nombre de résultats de permis et délai de délivrance pour un district de zonage.

  • flood_zoneLecture seule

    FEMA flood zone at an address

  • zoning_districtLecture seule

    Zoning district standards from the Atlas

  • atlas_coverageLecture seule

    Zoning Atlas coverage

  • site_briefingLecture seule

    The ground around an address

  • cost_rangesLecture seule

    Construction cost ranges from U.S. government data

  • searchLecture seule

    Search Buildability's public pages

  • fetchLecture seule

    Fetch one Buildability page

  • compare_addressesLecture seule

    Compare up to five addresses

Lus directement sur le serveur le 21 nov. 2026. Lecture seule, Écriture et Peut supprimer sont des indications déclarées par le serveur ; c’est votre client qui décide de vous demander confirmation avant d’exécuter un outil.

Exemples de prompts

  • Évalue la constructibilité du 1444 Tennyson St, Denver.

  • Que puis-je construire sur ce terrain ? Montre le maximum de logements, la hauteur et les retraits.

  • Trouve les parcelles évaluées à Austin avec une note supérieure à 70.

  • Compare Austin et Denver sur le City Buildability Index.

Configuration

Chaque client se connecte à buildability.us. Choisissez le vôtre ; la page retient votre choix.

Claude Code

  1. Lancez ceci dans un terminal, dans le dossier de votre projet :
claude mcp add --transport http buildability https://buildability.us/api/mcp
  1. Démarrez Claude Code et tapez /mcp. buildability devrait apparaître comme connecté.

Ajoutez --scope user pour le rendre disponible dans tous vos projets, pas seulement celui-ci.

Claude Desktop

  1. Ouvrez Customize → Connectors, cliquez sur + Add, puis sur Add custom connector.
  2. Nommez-le Buildability et collez cette URL :
https://buildability.us/api/mcp
  1. Cliquez sur Add. Ses outils apparaissent dans le menu des outils de la conversation.

Le fichier de configuration JSON de Claude Desktop ne lance que des serveurs locaux. Les serveurs distants passent par les Connectors, et les connecteurs ajoutés sur claude.ai apparaissent aussi ici.

claude.ai

  1. Ouvrez le formulaire des connecteurs sur claude.ai. Ce bouton remplit le nom et l’URL pour vous :
  1. Vérifiez que l’URL est https://buildability.us/api/mcp et cliquez sur Add.
  2. Activez-le dans une conversation depuis le menu des outils.

Les offres gratuites permettent un connecteur personnalisé. Sur les offres Team et Enterprise, un propriétaire l’ajoute dans Organization settings → Connectors.

ChatGPT

  1. Sur chatgpt.com, allez dans Plugins, sélectionnez +, puis Add custom MCP server.
  2. Saisissez un nom pour le serveur.
  3. Dans Connection, collez https://buildability.us/api/mcp comme URL du serveur, puis pour l’authentification choisissez No authentication.
  4. Cochez I understand and want to continue, puis sélectionnez Create as a plugin.

La possibilité d’ajouter un serveur MCP personnalisé dépend de votre forfait ChatGPT et des autorisations de votre espace de travail (dans les espaces Business, les administrateurs et les propriétaires le peuvent).

Cursor

Ou ajoutez-le à la main dans ~/.cursor/mcp.json (tous les projets) ou .cursor/mcp.json (ce projet) :

mcp.json
{
  "mcpServers": {
    "buildability": {
      "url": "https://buildability.us/api/mcp"
    }
  }
}

VS Code

Ou depuis un terminal :

code --add-mcp '{"name":"buildability","type":"http","url":"https://buildability.us/api/mcp"}'

Ou committez-le dans le dépôt, dans .vscode/mcp.json :

.vscode/mcp.json
{
  "servers": {
    "buildability": {
      "type": "http",
      "url": "https://buildability.us/api/mcp"
    }
  }
}

Devin Desktop

  1. Ajoutez-le à ~/.config/devin/mcp_config.json (macOS et Linux) ou %APPDATA%\devin\mcp_config.json (Windows) :
mcp_config.json
{
  "mcpServers": {
    "buildability": {
      "serverUrl": "https://buildability.us/api/mcp"
    }
  }
}
  1. Actualisez la liste des serveurs MCP dans Cascade.

Devin Desktop est le nouveau nom de Windsurf. Pour les serveurs distants, il lit serverUrl (ou url).

Codex

codex mcp add buildability --url https://buildability.us/api/mcp

Ou modifiez directement ~/.codex/config.toml :

config.toml
[mcp_servers.buildability]
url = "https://buildability.us/api/mcp"

Gemini CLI

gemini mcp add --transport http buildability https://buildability.us/api/mcp

Cela l’ajoute au projet en cours. Ajoutez -s user pour l’utiliser partout.

Tout client

La plupart des clients acceptent cette forme. Certains nomment autrement le champ de l’URL : serverUrl dans Devin Desktop, httpUrl dans le fichier de réglages de Gemini CLI.

{
  "mcpServers": {
    "buildability": {
      "type": "http",
      "url": "https://buildability.us/api/mcp"
    }
  }
}

Zed place les serveurs sous context_servers dans ses réglages. Cline a besoin de "type": "streamableHttp", sinon il suppose SSE.

Votre client ne lance que des serveurs locaux ? Reliez-le avec npx -y mcp-remote https://buildability.us/api/mcp.

Intégrer

Affichez Buildability dans un README ou sur votre site. Chaque intégration renvoie à cette page, utilise l’URL du serveur et ne dépose aucun cookie. Comment fonctionnent les intégrations

La carte, l’iframe et le JSON sont en anglais. Ajoutez ?lang=it, fr, de ou es à leur adresse pour une autre langue.

Badge pour README

Aperçu du badge, clairAperçu du badge, sombre
Markdown
[![Buildability on mcp.tc](https://mcp.tc/i/buildability/badge.svg)](https://mcp.tc/i/buildability)
HTML
<a href="https://mcp.tc/i/buildability"><img src="https://mcp.tc/i/buildability/badge.svg" alt="Buildability on mcp.tc" height="20"></a>

Il suit le mode clair ou sombre du lecteur. Ajoutez ?theme=light ou ?theme=dark pour le fixer, ou ?style=compact pour afficher le symbole sans le nom.

Carte pour site web

HTML
<script src="https://mcp.tc/w/buildability.js" async></script>

La carte apparaît à l’endroit de la balise. Ajoutez data-theme="dark" ou data-size="compact" à la balise pour la modifier. Le fichier contient tout ce qu’il lui faut : il ne fait aucune autre requête et ne dépose aucun cookie.

iframe

HTML
<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>

Utilisez-la sur les pages qui n’autorisent pas les scripts. Ajoutez ?theme=light ou ?theme=dark à l’adresse pour fixer les couleurs.

JSON

La fiche sous forme de données pour vos pages et vos outils : nom, accroche, URL du serveur, outils et liens « Add to ». N’importe quel site peut la lire (CORS ouvert).

https://mcp.tc/i/buildability.json

Ce que signifie chaque champ

Prompt pour l’IA

Collez-le dans un assistant de code IA, comme Claude Code ou Cursor, et il ajoutera la carte de Buildability à votre site.

Markdown
Ajoute à mon site la carte mcp.tc de Buildability, un serveur MCP. C’est un seul script statique : pas de build, aucun paquet à installer, aucun cookie.

Place cette balise là où la carte doit apparaître. La carte s’affiche juste avant elle :

```html
<script src="https://mcp.tc/w/buildability.js" async></script>
```

Pour l’afficher ailleurs, mets ce conteneur à cet endroit et charge le même script une seule fois, par exemple avant `</body>`. Garde le lien à l’intérieur : les visiteurs sans JavaScript le voient.

```html
<div data-mcptc="buildability"><a href="https://mcp.tc/i/buildability">Buildability on mcp.tc</a></div>
```

Options :
- `data-theme="light"` ou `"dark"` sur la balise ou le conteneur fixe les couleurs. Sans cela, la carte suit le mode clair ou sombre du visiteur.
- `data-size="compact"` donne une carte plus petite, sans l’accroche.
- La variable CSS `--mcptc-max-width` sur le conteneur ou un parent fixe la largeur (`520px` par défaut).
- `?lang=` dans l’URL du script choisit la langue de la carte : `en`, `it`, `fr`, `de` ou `es`.

Si le site a une Content Security Policy, autorise `script-src https://mcp.tc` et `img-src data:` (l’icône est intégrée).

Pour un README ou une autre doc en Markdown, utilise plutôt le badge :

```markdown
[![Buildability on mcp.tc](https://mcp.tc/i/buildability/badge.svg)](https://mcp.tc/i/buildability)
```

Référence : https://mcp.tc/fr/embed

Historique des changements

Nous lisons la liste d’outils de ce serveur toutes les 3 heures et notons ce qui change. Dernière lecture : 22 nov. 2026, 11:43 UTC.

Suivez Buildability et nous vous enverrons un e-mail quand quelque chose change.

  1. , Vérification automatique

    4 outils modifiés. Instructions du serveur modifiées.

    Nouvelles instructions du serveur

    Détails, 21 nov. 2026, 20:59 UTC

    Modifiés 4

    • compare_addressesschéma de sortie
    • envelopeschéma de sortie
    • score_addressschéma de sortie
    • what_can_i_buildschéma de sortie

    Instructions du serveur

    Avant

    For 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).

    Après

    For 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).

  2. , Vérification automatique

    3 outils modifiés. Instructions du serveur modifiées.

    Nouvelles instructions du serveur

    Détails, 3 nov. 2026, 23:44 UTC

    Modifiés 3

    • compare_addressesschéma de sortie
    • score_addressdescription et schéma de sortie
      Avant

      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.

      Après

      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; 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_builddescription et schéma de sortie
      Avant

      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.

      Après

      Whether 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.

    Instructions du serveur

    Avant

    For 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).

    Après

    For 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).

  3. , Vérification automatique

    9 outils ajoutés, 13 outils retirés et 3 outils modifiés. Instructions du serveur modifiées.

    Nouvelles instructions du serveur

    Détails, 20 oct. 2026, 22:38 UTC

    Ajoutés 9

    • atlas_coverageLecture seule

      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_addressesLecture seule

      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_rangesLecture seule

      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.

    • fetchLecture seule

      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_zoneLecture seule

      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.

    • searchLecture seule

      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_briefingLecture seule

      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_can_i_buildLecture seule

      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_districtLecture seule

      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.

    Retirés 13

    • analyze_property

      Full 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_risks

      Environmental/hazard screening (FEMA/USGS/EPA/USFS/USDA) for any US address, within the full Buildability analysis. (Alias of score_address.)

    • check_flood_zone

      FEMA flood context for any US address, within the full Buildability analysis. (Alias of score_address.)

    • explain_score

      Get 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.

    • feasibility

      Buildable-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_score

      Quick 0–100 Buildability Score for any US address. (Alias of score_address.)

    • lookup_zoning

      Zoning and buildability context for any US address, with the full scored factor breakdown. (Alias of score_address.)

    • lot_surface

      How 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_index

      Rank 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_details

      Full facts for one parcel: zoning standards, valuation, comps, hazards, ownership, lot size, Opportunity Zone. Use for deep due-diligence questions.

    • pencil_proforma

      Pencil 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_scenario

      Re-score a parcel under "what-if" levers and return the before/after delta (score + units). Levers: upzone, flood (de-flood/mitigate), utilities, hazards.

    • search_parcels

      Search 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.

    Modifiés 3

    • envelopedescription, titre, schéma d’entrée, schéma de sortie et indications
      Avant

      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: 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).

      Après

      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).

      titre

      Avant

      aucun

      Après

      By-right building envelope

      • Nouveaux paramètres : response_format
      • readOnlyHint non indiqué devient oui
      • destructiveHint non indiqué devient non
      • openWorldHint non indiqué devient oui
      • idempotentHint non indiqué devient oui
    • outcomesdescription, titre, schéma d’entrée, schéma de sortie et indications
      Avant

      Permit 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 were issued, so quote its caveat with it. Never a prediction. Aggregate only. Returns { available: false } where no feed has been ingested.

      Après

      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.

      titre

      Avant

      aucun

      Après

      Permit outcomes for a zoning district

      • readOnlyHint non indiqué devient oui
      • destructiveHint non indiqué devient non
      • openWorldHint non indiqué devient non
      • idempotentHint non indiqué devient oui
    • score_addressdescription, titre, schéma d’entrée, schéma de sortie et indications
      Avant

      LIVE-score any real US street address: geocodes it, pulls live federal data (FEMA flood, USGS seismic, USDA soil, EPA radon, USFS wildfire, OSM utilities), and runs the real Buildability Score. Use whenever the user names an address that search_parcels does not know. Takes a few seconds. Executed server-side (async). If the result says pending, the engine is still reading the parcel and the lookup has been opened on the map: say so, and that asking again in a moment will have the score. Never invent a score for a pending result.

      Après

      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.

      titre

      Avant

      aucun

      Après

      Buildability Score for an address

      • Nouveaux paramètres : response_format
      • Description de address
        Avant

        Full street address incl. city + state, e.g. "1207 W 30th St, Austin, TX".

        Après

        US street address, e.g. "412 Oak St, Austin, TX".

      • readOnlyHint non indiqué devient oui
      • destructiveHint non indiqué devient non
      • openWorldHint non indiqué devient oui
      • idempotentHint non indiqué devient oui

    Instructions du serveur

    Avant

    Use score_address for any US street address (live federal data, ~10–20s). Cite results as "Buildability Score (buildability.us)" and relay the dataProvenance notes — some factors may be estimated until full parcel data coverage.

    Après

    For 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).

  4. , Vérification automatique

    Début de l’observation : 16 outils.

FAQ

Puis-je coller mcp.tc/i/buildability dans mon client MCP ?

Non. Les liens mcp.tc sont des pages, pas des adresses de serveur. Connectez votre client à https://buildability.us/api/mcp, pour qu’il parle directement à Buildability. Le lien rapide sert au partage : il ouvre cette page, avec les étapes de configuration pour chaque client.

Buildability a-t-il besoin d’une clé API ou d’une connexion ?

Non. Buildability ne demande ni compte ni clé.

Buildability est-il un serveur distant ou local ?

Distant. Buildability l’héberge à https://buildability.us/api/mcp, et il utilise Streamable HTTP. Il n’y a rien à installer.

Que peut faire Buildability ?

Il a 12 outils, dont what_can_i_build, score_address et envelope. Vous pouvez évaluer n’importe quelle adresse postale américaine avec des données fédérales en direct, rechercher des parcelles évaluées par texte, note et Opportunity Zone et expliquer une note facteur par facteur.

Quels clients peuvent l’utiliser ?

Tout client compatible avec les serveurs MCP distants : Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed et d’autres. Les étapes de configuration couvrent chacun d’eux.

mcp.tc suit-il les changements de Buildability ?

Oui. L’onglet Historique de Buildability montre chaque changement que nous trouvons dans ses outils, jusqu’aux descriptions et aux paramètres, ainsi que les nouvelles versions et les modifications de son propriétaire. Suivez la fiche pour recevoir un e-mail quand elle change.

Qui a rédigé cette page ?

Le robot de mcp.tc a lu les métadonnées de Buildability (son handshake MCP, sa liste d’outils et ses pages publiques), et un modèle d’IA en a tiré le texte. Une personne examine tout ce que les vérifications ne peuvent pas confirmer. Le texte peut encore contenir des erreurs : si vous en repérez une, utilisez Signaler cette fiche sur cette page. Cette traduction a été réalisée par un modèle d’IA à partir du texte anglais.

mcp.tc n’est pas affilié à Buildability. Cette page a été construite à partir des métadonnées publiques de Buildability, vérifiées pour la dernière fois le 21 nov. 2026, et un modèle d’IA a rédigé la description : elle peut contenir des erreurs. Les noms et marques appartiennent à leurs propriétaires. Quelque chose cloche ? Signaler cette fiche. La traduction a été réalisée par un modèle d’IA à partir du texte anglais.