Nosotros y terceros seleccionados usamos cookies o tecnologías similares con fines técnicos y, con tu consentimiento, para analizar cómo se usa el sitio.

Puedes dar, negar o retirar libremente tu consentimiento en cualquier momento.

Buildability

Servidor MCP de Buildability

Puntúa cualquier parcela de EE. UU. con nueve factores citados, como zonificación, inundación, sismos, suelo, radón e incendios, para ver qué se puede construir.

Sin cuenta (No hace falta cuenta ni clave)Streamable HTTP

Conectar con Buildability

No hace falta iniciar sesión. Conéctate con la URL propia de Buildability:

https://buildability.us/api/mcp

Pégala en cualquier cliente compatible con servidores MCP remotos. Tu cliente habla directamente con Buildability, no a través de mcp.tc.

Compartir este servidor

El enlace abre esta página, con la URL y los pasos de configuración.

mcp.tc/i/buildability

Descripción

Se conecta al servicio Buildability, que puntúa de 0 a 100 direcciones y parcelas de EE. UU. con datos públicos citados: zonificación, inundación de FEMA, sismos de USGS, suelo de USDA, radón de EPA, incendios forestales de USFS, servicios, terreno y forma del lote. Las herramientas cubren puntuación de direcciones en vivo, búsqueda de parcelas, desglose por factores, envolventes edificables, escenarios hipotéticos, pro-formas y rankings de mercados urbanos.

Funciona como un endpoint Streamable HTTP alojado. Puntuar una dirección nueva tarda aproximadamente de 10 a 20 segundos. Las herramientas principales no requieren iniciar sesión ni clave de API; la herramienta lot_surface requiere una clave de API de Buildability.

Qué puedes hacer

  • Puntuar cualquier dirección postal de EE. UU. con datos federales en vivo
  • Buscar parcelas puntuadas por texto, puntuación y Opportunity Zone
  • Explicar una puntuación factor por factor
  • Obtener la envolvente edificable: unidades, FAR, altura, retranqueos
  • Ejecutar escenarios hipotéticos como cambio de zonificación o mitigación de inundaciones
  • Calcular una pro-forma de desarrollo para una parcela
  • Clasificar áreas metropolitanas en el City Buildability Index
  • Consultar resultados de permisos de un distrito de zonificación

Herramientas 12

  • what_can_i_buildSolo lectura

    What can I build on a property

  • score_addressSolo lectura

    Puntúa en vivo una dirección postal de EE. UU. con datos federales y devuelve la Buildability Score.

  • envelopeSolo lectura

    Lo que cabe en un lote por derecho según su código de zonificación, con citas.

  • outcomesSolo lectura

    Recuento de resultados de permisos y tiempo de emisión de un distrito de zonificación.

  • flood_zoneSolo lectura

    FEMA flood zone at an address

  • zoning_districtSolo lectura

    Zoning district standards from the Atlas

  • atlas_coverageSolo lectura

    Zoning Atlas coverage

  • site_briefingSolo lectura

    The ground around an address

  • cost_rangesSolo lectura

    Construction cost ranges from U.S. government data

  • searchSolo lectura

    Search Buildability's public pages

  • fetchSolo lectura

    Fetch one Buildability page

  • compare_addressesSolo lectura

    Compare up to five addresses

Leídas del servidor en funcionamiento el 21 nov 2026. Solo lectura, Escritura y Puede borrar son indicaciones que declara el servidor; tu cliente decide si te pregunta antes de ejecutar una herramienta.

Prompts de ejemplo

  • Puntúa la edificabilidad de 1444 Tennyson St, Denver.

  • ¿Qué puedo construir en este lote? Muestra unidades máximas, altura y retranqueos.

  • Busca parcelas puntuadas en Austin con una puntuación superior a 70.

  • Compara Austin y Denver en el City Buildability Index.

Configuración

Todos los clientes se conectan a buildability.us. Elige el tuyo; la página recuerda tu elección.

Claude Code

  1. Ejecútalo en un terminal, en la carpeta de tu proyecto:
claude mcp add --transport http buildability https://buildability.us/api/mcp
  1. Inicia Claude Code y escribe /mcp. buildability debería aparecer como conectado.

Añade --scope user para que esté disponible en todos los proyectos, no solo en este.

Claude Desktop

  1. Abre Customize → Connectors, haz clic en + Add y luego en Add custom connector.
  2. Llámalo Buildability y pega esta URL:
https://buildability.us/api/mcp
  1. Haz clic en Add. Sus herramientas aparecen en el menú de herramientas del chat.

El archivo de configuración JSON de Claude Desktop solo inicia servidores locales. Los servidores remotos van por Connectors, y los conectores que añades en claude.ai también aparecen aquí.

claude.ai

  1. Abre el formulario de conectores en claude.ai. Este botón rellena el nombre y la URL por ti:
  1. Comprueba que la URL es https://buildability.us/api/mcp y haz clic en Add.
  2. Actívalo en un chat desde el menú de herramientas.

Los planes gratuitos permiten un conector personalizado. En los planes Team y Enterprise lo añade un propietario en Organization settings → Connectors.

ChatGPT

  1. En chatgpt.com, ve a Plugins, selecciona + y luego Add custom MCP server.
  2. Escribe un nombre para el servidor.
  3. En Connection, pega https://buildability.us/api/mcp como URL del servidor y luego, como autenticación, elige No authentication.
  4. Marca I understand and want to continue y luego selecciona Create as a plugin.

Poder añadir un servidor MCP personalizado depende de tu plan de ChatGPT y de los permisos de tu espacio de trabajo (en los espacios Business pueden hacerlo los administradores y los propietarios).

Cursor

O añádelo a mano en ~/.cursor/mcp.json (todos los proyectos) o en .cursor/mcp.json (este proyecto):

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

VS Code

O desde un terminal:

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

O haz commit del archivo en el repositorio como .vscode/mcp.json:

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

Devin Desktop

  1. Añádelo a ~/.config/devin/mcp_config.json (macOS y Linux) o a %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "buildability": {
      "serverUrl": "https://buildability.us/api/mcp"
    }
  }
}
  1. Actualiza la lista de servidores MCP en Cascade.

Devin Desktop es el nuevo nombre de Windsurf. Para los servidores remotos lee serverUrl (o url).

Codex

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

O edita directamente ~/.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

Así lo añades al proyecto actual. Añade -s user para usarlo en todas partes.

Cualquier cliente

La mayoría de los clientes aceptan esta forma. Algunos llaman de otra manera al campo de la URL: serverUrl en Devin Desktop, httpUrl en el archivo de ajustes de Gemini CLI.

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

Zed pone los servidores bajo context_servers en sus ajustes. Cline necesita "type": "streamableHttp"; si no, supone SSE.

¿Tu cliente solo inicia servidores locales? Conéctalo con npx -y mcp-remote https://buildability.us/api/mcp.

Insertar

Muestra Buildability en un README o en tu web. Cada inserción enlaza a esta página, usa la URL propia del servidor y no instala cookies. Cómo funcionan las inserciones

La tarjeta, el iframe y el JSON están en inglés. Añade ?lang=it, fr, de o es a su dirección para otro idioma.

Insignia para README

Vista previa de la insignia, claraVista previa de la insignia, oscura
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>

Sigue el modo claro u oscuro de quien lee. Añade ?theme=light o ?theme=dark para fijarlo, o ?style=compact para mostrar el símbolo sin la palabra.

Tarjeta para web

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

La tarjeta aparece donde esté la etiqueta. Añade data-theme="dark" o data-size="compact" a la etiqueta para cambiarla. El archivo contiene todo lo que necesita, así que no hace otras solicitudes ni instala cookies.

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>

Úsalo en páginas que no permiten scripts. Añade ?theme=light o ?theme=dark a la dirección para fijar los colores.

JSON

La ficha como datos para tus propias páginas y herramientas: nombre, descripción corta, la URL propia del servidor, herramientas y los enlaces «Add to». Cualquier web puede leerla (CORS abierto).

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

Qué significa cada campo

Prompt para la IA

Pégalo en un asistente de programación con IA, como Claude Code o Cursor, y añadirá la tarjeta de Buildability a tu web.

Markdown
Añade a mi web la tarjeta de mcp.tc de Buildability, un servidor MCP. Es un solo script estático: sin paso de build, sin paquetes que instalar, sin cookies.

Pon esta etiqueta donde deba aparecer la tarjeta. La tarjeta se muestra justo antes de ella:

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

Para mostrarla en otro sitio, pon allí este marcador y carga el mismo script una sola vez, por ejemplo antes de `</body>`. Deja el enlace dentro: lo ven los visitantes sin JavaScript.

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

Opciones:
- `data-theme="light"` o `"dark"` en la etiqueta o el marcador fija los colores. Sin él, la tarjeta sigue el modo claro u oscuro del visitante.
- `data-size="compact"` da una tarjeta más pequeña, sin el eslogan.
- La variable CSS `--mcptc-max-width` en el marcador o en un elemento padre fija el ancho (por defecto `520px`).
- `?lang=` en la URL del script fija el idioma de la tarjeta: `en`, `it`, `fr`, `de` o `es`.

Si el sitio tiene una Content Security Policy, permite `script-src https://mcp.tc` e `img-src data:` (el icono va incrustado).

Para un README u otra documentación en Markdown, usa la insignia:

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

Referencia: https://mcp.tc/es/embed

Historial de cambios

Leemos la lista de herramientas de este servidor cada 3 horas y registramos lo que cambia. Última lectura: 22 nov 2026, 11:43 UTC.

Sigue Buildability y te enviaremos un correo cuando algo cambie.

  1. , Comprobación automática

    4 herramientas cambiadas. Instrucciones del servidor cambiadas.

    Nuevas instrucciones del servidor

    Detalles, 21 nov 2026, 20:59 UTC

    Cambiadas 4

    • compare_addressesesquema de salida
    • envelopeesquema de salida
    • score_addressesquema de salida
    • what_can_i_buildesquema de salida

    Instrucciones del servidor

    Antes

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

    Despué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. , Comprobación automática

    3 herramientas cambiadas. Instrucciones del servidor cambiadas.

    Nuevas instrucciones del servidor

    Detalles, 3 nov 2026, 23:44 UTC

    Cambiadas 3

    • compare_addressesesquema de salida
    • score_addressdescripción y esquema de salida
      Antes

      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.

      Despué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_builddescripción y esquema de salida
      Antes

      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.

      Despué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.

    Instrucciones del servidor

    Antes

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

    Despué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. , Comprobación automática

    9 herramientas añadidas, 13 herramientas eliminadas y 3 herramientas cambiadas. Instrucciones del servidor cambiadas.

    Nuevas instrucciones del servidor

    Detalles, 20 oct 2026, 22:38 UTC

    Añadidas 9

    • atlas_coverageSolo lectura

      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_addressesSolo lectura

      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_rangesSolo lectura

      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.

    • fetchSolo lectura

      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_zoneSolo lectura

      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.

    • searchSolo lectura

      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_briefingSolo lectura

      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_buildSolo lectura

      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_districtSolo lectura

      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.

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

    Cambiadas 3

    • envelopedescripción, título, esquema de entrada, esquema de salida y indicaciones
      Antes

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

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

      título

      Antes

      ninguno

      Después

      By-right building envelope

      • Parámetros nuevos: response_format
      • readOnlyHint sin indicar pasa a sí
      • destructiveHint sin indicar pasa a no
      • openWorldHint sin indicar pasa a sí
      • idempotentHint sin indicar pasa a sí
    • outcomesdescripción, título, esquema de entrada, esquema de salida y indicaciones
      Antes

      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.

      Despué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.

      título

      Antes

      ninguno

      Después

      Permit outcomes for a zoning district

      • readOnlyHint sin indicar pasa a sí
      • destructiveHint sin indicar pasa a no
      • openWorldHint sin indicar pasa a no
      • idempotentHint sin indicar pasa a sí
    • score_addressdescripción, título, esquema de entrada, esquema de salida y indicaciones
      Antes

      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.

      Despué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.

      título

      Antes

      ninguno

      Después

      Buildability Score for an address

      • Parámetros nuevos: response_format
      • Descripción de address
        Antes

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

        Después

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

      • readOnlyHint sin indicar pasa a sí
      • destructiveHint sin indicar pasa a no
      • openWorldHint sin indicar pasa a sí
      • idempotentHint sin indicar pasa a sí

    Instrucciones del servidor

    Antes

    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.

    Despué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. , Comprobación automática

    Inicio del seguimiento: 16 herramientas.

Preguntas frecuentes

¿Puedo pegar mcp.tc/i/buildability en mi cliente MCP?

No. Los enlaces de mcp.tc son páginas, no direcciones de servidores. Conéctate con https://buildability.us/api/mcp, para que tu cliente hable directamente con Buildability. El enlace rápido sirve para compartir: abre esta página, con los pasos de configuración para cada cliente.

¿Buildability necesita una clave de API o iniciar sesión?

No. Buildability no pide cuenta ni clave.

¿Buildability es un servidor remoto o local?

Remoto. Lo aloja Buildability en https://buildability.us/api/mcp, y usa Streamable HTTP. No hay nada que instalar.

¿Qué puede hacer Buildability?

Tiene 12 herramientas, entre ellas what_can_i_build, score_address y envelope. Puedes puntuar cualquier dirección postal de EE. UU. con datos federales en vivo, buscar parcelas puntuadas por texto, puntuación y Opportunity Zone y explicar una puntuación factor por factor.

¿Qué clientes pueden usarlo?

Cualquier cliente compatible con servidores MCP remotos: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed y otros. Los pasos de configuración cubren cada uno.

¿mcp.tc sigue los cambios de Buildability?

Sí. La pestaña Historial de Buildability muestra cada cambio que encontramos en sus herramientas, hasta las descripciones y los parámetros, además de las versiones nuevas y las ediciones de su responsable. Sigue la ficha para recibir un correo cuando cambie.

¿Quién escribió esta página?

El robot de mcp.tc leyó los metadatos propios de Buildability (su handshake MCP, su lista de herramientas y sus páginas públicas), y un modelo de IA redactó el texto a partir de ellos. Una persona revisa todo lo que las comprobaciones no pueden confirmar. Aun así, el texto puede contener errores, así que si encuentras uno, usa Reportar esta ficha en esta página. Esta traducción la hizo un modelo de IA a partir del texto en inglés.

mcp.tc no tiene relación con Buildability. Esta página se creó a partir de los metadatos públicos de Buildability, comprobados por última vez el 21 nov 2026, y un modelo de IA escribió la descripción, así que puede contener errores. Los nombres y marcas pertenecen a sus titulares. ¿Algo no cuadra? Reportar esta ficha. La traducción la hizo un modelo de IA a partir del texto en inglés.