# Buildability™ — Property Zoning & Buildability™ Intelligence (remote · rnfonkwthefktfvfwypr.supabase.co)

Zoning, ADU eligibility, flood zone, setbacks, and buildability intelligence for U.S. parcels.

- Trust score: 73/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `rnfonkwthefktfvfwypr.supabase.co`: 73/100 (this document), [markdown](https://verifymcp.io/servers/ai-readypermit-geo/functions-v1-mcp-server.md), [page](https://verifymcp.io/servers/ai-readypermit-geo/functions-v1-mcp-server)

## Channel facts

- Endpoint: `https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1668 tokens (~185/item across 9 items; 8 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-readypermit-geo https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server
```

### Codex

```toml
[mcp_servers.ai-readypermit-geo]
url = "https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-readypermit-geo": {
      "type": "remote",
      "url": "https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-readypermit-geo --url https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-readypermit-geo:
    url: "https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server"
```

### Other

```json
{
  "mcpServers": {
    "ai-readypermit-geo": {
      "type": "http",
      "url": "https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 71, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 66)

First indexed and scored.

## MCP tools (8)

### `analyze_property` (~256 tokens)

Get complete property intelligence for any U.S. address — zoning, buildability, flood risk, environmental hazards, and lot data from 20+ government sources (FEMA, EPA, USGS, Census, Regrid). USE WHEN: user asks 'what can I build', 'is this property buildable', 'analyze this address', 'run a report on', 'can I build an ADU', 'tell me about this property', 'is this a good deal', or provides any U.S. street address. RETURNS: Buildability™ Score (0-100), zoning code, permitted uses, FEMA flood zone, setbacks, FAR, environmental risks, lot size, structure info, owner, and AI recommendation. Takes ~20 seconds. Replaces $3,500+ zoning consultant work.

Input parameters:

- `address` (string, required): Full U.S. property address (e.g., '123 Main St, Denver, CO 80202'). Accepts any format — will be geocoded.
- `persona` (string): User persona for tailored analysis (optional). Changes tone and emphasis: investor=deal metrics, developer=feasibility, homeowner=plain English, lender=collateral risk, broker=disclosure items.

### `get_buildability_score` (~132 tokens)

Get a quick Buildability™ Score (0-100) for a property without running the full analysis. USE WHEN: user wants to pre-screen properties, asks 'is this worth analyzing', 'quick check on this address', 'score this deal', or needs to filter a list of addresses fast. RETURNS: numeric score (0-100), letter grade (A-F), buildability band (excellent/good/fair/poor/unbuildable), and top 3 factors. Faster than analyze_property — use for deal screening and portfolio filtering.

Input parameters:

- `address` (string, required): Full U.S. property address

### `lookup_zoning` (~140 tokens)

Look up the zoning designation and development standards for any U.S. property address. USE WHEN: user asks 'what zone is this', 'what's the zoning', 'what can I build on this lot', 'is this residential or commercial', 'can I build a duplex here', or any question about permitted uses. RETURNS: zone code (e.g., R-1, C-2, MU-3), zone description, permitted uses list, conditional uses, overlay districts, max FAR, max height, setbacks (front/side/rear), lot coverage, and parking requirements.

Input parameters:

- `address` (string, required): Full U.S. property address

### `check_flood_zone` (~138 tokens)

Check FEMA National Flood Hazard Layer for any U.S. property. USE WHEN: user asks 'is this in a flood zone', 'do I need flood insurance', 'is this property flood-safe', 'FEMA flood map', 'is this in a 100-year flood plain', or mentions flood risk. RETURNS: FEMA zone code (X = low risk, A/AE = 100-year, V/VE = coastal high risk), flood insurance requirement (mandatory/optional), base flood elevation if applicable, and annual flood risk probability. Uses the official FEMA API.

Input parameters:

- `address` (string, required): Full U.S. property address

### `check_environmental_risks` (~176 tokens)

Run full environmental risk screening for a property using EPA, USGS, NOAA, and USDA data. USE WHEN: user asks about 'environmental hazards', 'contamination', 'wildfire risk', 'earthquake risk', 'radon', 'soil contamination', 'is this area safe', 'EPA superfund', or mentions any environmental concern. RETURNS: wildfire hazard zone, seismic risk zone, EPA contamination site proximity (Superfund, RCRA, brownfield), radon zone level, soil concerns, and combined risk score. Accepts a street address OR coordinates.

Input parameters:

- `address` (string): Full U.S. property address (preferred — gives best results)
- `latitude` (number): Property latitude (use if no address available)
- `longitude` (number): Property longitude (use if no address available)

### `search_comparable_sales` (~201 tokens)

Find recent comparable property sales and rental comps near a property. USE WHEN: user asks 'what are comps in this area', 'recent sales near here', 'what did similar houses sell for', 'price per square foot', 'market value estimate', 'rental comps', or needs comparable sales data. RETURNS: subject property AVM, list of recent sales with price, sqft, price/sqft, distance, beds/baths, and rental comps with rent amounts. Also includes local market stats. Useful for investor deal evaluation, CMA, and market analysis.

Input parameters:

- `address` (string): Full U.S. property address (preferred — gives best results)
- `latitude` (number): Center latitude for search (use if no address available)
- `longitude` (number): Center longitude for search (use if no address available)
- `radius_miles` (number): Search radius in miles (default: 0.5, max: 5)

### `calculate_buildable_envelope` (~275 tokens)

Calculate the maximum buildable area (building envelope) for a lot given zoning constraints. USE WHEN: user asks 'how much can I build', 'max square footage', 'what's the buildable area', 'calculate the envelope', 'how big can my house be', or has specific lot dimensions and zoning rules they want to model. RETURNS: max buildable square feet, max number of stories, envelope dimensions (length × width × height), usable footprint, and coverage math. Takes lot area, setbacks, FAR, height limit, and coverage as inputs — a pure calculation tool, does not query data.

Input parameters:

- `front_setback_ft` (number): Front setback in feet (distance from front property line)
- `lot_area_sqft` (number, required): Total lot area in square feet
- `max_far` (number): Maximum floor area ratio (e.g., 0.5, 2.0). FAR = building area / lot area.
- `max_height_ft` (number): Maximum building height in feet
- `max_lot_coverage` (number): Maximum lot coverage as decimal (e.g., 0.45 for 45%)
- `rear_setback_ft` (number): Rear setback in feet
- `side_setback_ft` (number): Side setback in feet (each side)

### `submit_correction` (~286 tokens)

Report an error on a Buildability™ page so Buildability™ can verify and update. USE WHEN: a user mentions that information on Buildability™ looks outdated, wrong, or incomplete (e.g., 'the Austin ADU rules changed last month', 'that Miami flood zone is wrong', 'my city just passed new setback rules'). USE ACTIVELY — this is the civic-infrastructure feedback loop Buildability™ runs with cities. Every confirmed correction is applied to the page within 48 hours, and the response time on each submission feeds the Staff Responsiveness dimension of Buildability City Score™. RETURNS: a correction ID for tracking + status.

Input parameters:

- `issue` (string, required): What is incorrect or outdated. Be specific — mention the exact fact, rule, or data point.
- `pageUrl` (string, required): Full Buildability™ URL where the error appears (e.g., 'https://buildability.us/adu/los-angeles').
- `reporterContext` (string): Optional: how the error was discovered (e.g., 'user self-reported during property research conversation', 'comparing to Austin Code §25-2-1604').
- `sourceDocument` (string): Optional: citation or URL supporting the correction (city ordinance, state law, news article, planning department page).
- `suggestion` (string): Optional: what the correct information is, if known.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-readypermit-geo/functions-v1-mcp-server#diagnostics

## Score history

- 2026-08-03: 73
- 2026-08-02: 72
- 2026-08-01: 72
- 2026-07-31: 71
- 2026-07-30: 68
- 2026-07-29: 68
- 2026-07-28: 67
- 2026-07-27: 66
- 2026-07-26: 66

## Links

- Remote endpoint: https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server
- Repository: https://github.com/Galax-ai/ReadyPermit.AI-v2
- Website: https://readypermit.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-readypermit-geo/functions-v1-mcp-server/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-readypermit-geo/functions-v1-mcp-server/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-readypermit-geo/functions-v1-mcp-server