Buildability™ — Property Zoning & Buildability™ Intelligence
REMOTE · RNFONKWTHEFKTFVFWYPR.SUPABASE.CO · SCANNED AUG 3
Zoning, ADU eligibility, flood zone, setbacks, and buildability intelligence for U.S. parcels.
Available components
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. How we score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · rnfonkwthefktfvfwypr.supabase.co
claude mcp add --transport http ai-readypermit-geo https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server
[mcp_servers.ai-readypermit-geo] url = "https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-readypermit-geo": {
"type": "remote",
"url": "https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server",
"enabled": true
}
}
} openclaw mcp add ai-readypermit-geo --url https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server --transport streamable-http
mcp_servers:
ai-readypermit-geo:
url: "https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +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.
- 1 Aug 26 +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.
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 26 +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.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supabase.co | CN=WE1,O=Google Trust Services,C=US | 28 Jun 2026 | 26 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 1d2d53f65d874dfb0eead7aab0301afd |
| SANs: supabase.co, *.supabase.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of rnfonkwthefktfvfwypr.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| supabase.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server | Verified | 200 | |
| http (plaintext) | http://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server | HTTPS enforced | 301 | https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
analyze_property ~256
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 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. |
No output schema declared.
No examples provided.
calculate_buildable_envelope ~275
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.
| Name | Type | Req | Description |
|---|---|---|---|
| front_setback_ft | number | — | Front setback in feet (distance from front property line) |
| lot_area_sqft | number | yes | 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) |
No output schema declared.
No examples provided.
check_environmental_risks ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
check_flood_zone ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Full U.S. property address |
No output schema declared.
No examples provided.
get_buildability_score ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Full U.S. property address |
No output schema declared.
No examples provided.
lookup_zoning ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Full U.S. property address |
No output schema declared.
No examples provided.
search_comparable_sales ~201
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
submit_correction ~286
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.
| Name | Type | Req | Description |
|---|---|---|---|
| issue | string | yes | What is incorrect or outdated. Be specific — mention the exact fact, rule, or data point. |
| pageUrl | string | yes | 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. |
No output schema declared.
No examples provided.