MCP servers observed by Lowdown
ai.readypermit/geo MCP server: daily status and tool changes
No Lowdown daily check since 2026-10-31 (18 days ago), so no current connectivity is stated. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-06; no tool definition change in 12 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.readypermit/geo
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.readypermit/geo?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-10-31: the server answered initialize and tools/list. That check is 18 days old, so it is not a current status.
- Observed days in the last 30: 12
- Answered initialize and tools/list: 12
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 12 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 12 compared days.
What tools does it list?
8 tools on 2026-10-31:
analyze_propertycalculate_buildable_envelopecheck_environmental_riskscheck_flood_zoneget_buildability_scorelookup_zoningsearch_comparable_salessubmit_correction
MCP Registry declaration
- Registry name:
ai.readypermit/geo - Declared version: 1.2.3
- Status: deprecated
- Declared hosts:
rnfonkwthefktfvfwypr.supabase.co
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:ai.readypermit/geo", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.readypermit/geo?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).