Remote MCP · Endpoint

Buildability™ — Property Zoning & Buildability™ Intelligence MCP server

Yes, as of 1 hour ago: the server rejected the MCP handshake.

DownLast checked 1 hour ago

Server URL

https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server

The last check failed: the server rejected the MCP handshake.

Registry name
ai.readypermit/geo
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
8 tools
Uptime, last 30 days
84.2% from 19 checks
Described by its publisher as
Zoning, ADU eligibility, flood zone, setbacks, and buildability intelligence for U.S. parcels.
Website
https://readypermit.ai/
Repository
https://github.com/Galax-ai/ReadyPermit.AI-v2
Listing
From the official MCP registry (deprecated).
Recent checks of Buildability™ — Property Zoning & Buildability™ Intelligence
CheckedResultHandshake
1 hour agoFailed - the server rejected the MCP handshake—
12 hours agoFailed - the server rejected the MCP handshake—
1 day agoFailed - the server rejected the MCP handshake—
2 days agoHandshake completed122 ms
4 days agoHandshake completed199 ms
4 days agoHandshake completed186 ms
5 days agoHandshake completed218 ms
7 days agoHandshake completed333 ms
8 days agoHandshake completed279 ms
11 days agoHandshake completed169 ms
13 days agoHandshake completed237 ms
16 days agoHandshake completed279 ms
18 days agoHandshake completed230 ms
20 days agoHandshake completed210 ms
22 days agoHandshake completed252 ms
24 days agoHandshake completed413 ms
26 days agoHandshake completed216 ms
28 days agoHandshake completed257 ms
29 days agoHandshake completed172 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 31.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Buildability™ — Property Zoning & Buildability™ Intelligence and makes no claim about it beyond what these checks measured.