← Back to search
ai.readypermit/geo

Buildability™ — Property Zoning & Buildability™ Intelligence

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

EXECUTIVE VERDICT

Executive verdict

Production trust decision: Allow with approval
Reason: write/exec approval gaps + high-risk tools need review
Next action: export policy, configure alerts, require approval for writes
Status
Healthy
Score
74.7
Transport
streamable-http
Tools
8

Current trust snapshot

Snapshot ID
trustsnap_163b47ec131e85e0
Use this ID to compare server page, report, policy, MCP, homepage, ranking, and shortlist surfaces.
Snapshot generated
May 13, 2026 06:02:38 PM UTC
All page, report, policy, and MCP surfaces use this same server-detail snapshot shape.
Last validated
May 13, 2026 02:35:10 PM UTC
Age: 3.46h • freshness band: Verified in last 24h • display score: 74.74
Production trust decision
Allow with approval
write/exec approval gaps + high-risk tools need review
Readiness class
Safe for evaluation
The server is suitable for evaluation, but remaining gaps should be resolved before broad production use.
SERVER OWNER FUNNEL

Own this MCP?

Claim ownership, prove control with a GitHub, DNS, or HTTP token challenge, revalidate now, publish a badge, and configure monitoring.

1. Claim
unclaimed
Start owner claim with GitHub, DNS, or HTTP challenge instructions.
2. Revalidate
POST /v1/servers/ai.readypermit/geo/revalidate
Verified owners get priority queueing after proof succeeds.
3. Badge
Verified by MCP Verify badge
Verified by MCP Verify - score 74.7 - last checked May 13, 2026
4. Monitor
Continuous Verify plan is self-serve: choose a tier, configure watches, add authenticated validation, trigger revalidation, and use the badge.
Badge embed
[![Verified by MCP Verify](https://verify.sentinelsignal.io/badge/ai.readypermit/geo.svg)](https://verify.sentinelsignal.io/servers/ai.readypermit/geo)

MCP TrustOps

TrustOps turns this report into operational controls: freshness SLAs, authenticated validation, semantic benchmarks, policy exports, alert subscriptions, badges, cost/compliance metadata, and runtime routing. Fresh trusted index decisions stay separate from long-tail inventory so stale scores do not masquerade as current evidence.

Freshness band
Verified in last 24h
Policy SLA: 168.0h • confidence-weighted score: 59.8 • stale score suppressed:
Policy exports
Formats: json, rego, yaml, github_action, gateway_config, client_report
Runtime routing
/v1/route
Returns allowed tools, blocked tools, approval requirement, and reason.
Authenticated validation
Premium publisher feature: paid authenticated runs verify scopes, write-action safeguards, and authorized tool execution.
Active trust badges
Freshly Validated Claude Remote MCP Ready No Critical Risk
Semantic benchmarks
available
Templates cover GitHub, database, healthcare, web search, and CRM least-privilege jobs.
Supply chain
metadata signal
Deep scan checks are marked separately from public metadata signals.
Compliance metadata
Terms, privacy, SOC 2, HIPAA, GDPR, retention, deletion, and audit-log fields are tracked as enterprise metadata.
Alert subscription types
Status changes Score drops or recovers Freshness SLA breach Validation schema drift OAuth or auth behavior changes Tool surface changes New or changed write tool Supply-chain signal changes Legal or compliance metadata changes

Production readiness class

Production readiness class
Safe for evaluation
The server is suitable for evaluation, but remaining gaps should be resolved before broad production use.
Critical alerts
0
Production verdicts degrade quickly when critical alerts are active.

Evidence confidence

Confidence score
80.0
Based on 4 recent validations, 26 captured checks, and validation age of 3.5 hours.
Live checks captured
26
More direct checks increase trust in the current verdict.
Validation age
3.5h
Lower age means fresher evidence.

Recommended for

Claude Desktop
Claude Desktop is marked compatible with score 83.
Smithery
Smithery is marked compatible with score 80.
Generic Streamable HTTP
Generic Streamable HTTP is marked compatible with score 100.

Client compatibility verdicts

Client compatibility only means the server shape can work with a client. Production trust decision and write-action publishing are evaluated separately so a client-compatible server can still be blocked for production.

Client compatibility: ChatGPT
Partially client-compatible
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance should be in good shape.
Confidence: high (80.0)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listOK
  • transport_compliance_probeError
  • step_up_auth_probeMissing
  • connector_replay_probeOK — Frozen tool snapshots must survive refresh.
  • request_association_probeMissing — Roots, sampling, and elicitation should stay request-scoped.
Client compatibility: Claude
Client-compatible
Transport behavior should match Claude-compatible HTTP expectations.
Confidence: high (80.0)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listOK
  • transport_compliance_probeError
Write-action publishing
Publishing blocked
Blocked until safeguards and confirmation semantics are verified for write, exec, or destructive tools.
Confidence: high (80.0)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history
Disagreements: none
  • action_safety_probeError
Snapshot churn risk
Low
No material tool-surface churn detected in the latest comparison.
Confidence: high (80.0)
Evidence provenance
Winner: history
Supporting sources: history, live_validation
Disagreements: none
  • tool_snapshot_probeOK
  • connector_replay_probeOK

Why compatibility is limited by client

ChatGPT custom connector
Partial
Remediation checklist
  • No explicit blockers recorded.
Claude remote MCP
Ready
Remediation checklist
  • No explicit blockers recorded.
Write-safe publishing
Blocked
Remediation checklist
  • No explicit blockers recorded.

Verdict traces

Production verdict
Safe for evaluation
The server is suitable for evaluation, but remaining gaps should be resolved before broad production use.
Confidence: high (80.0)
Winning source: live_validation
Triggering alerts
  • No active alert triggers.
Client verdict trace table
VerdictStatusChecksWinning sourceConflicts
openai_connectors Partially client-compatible initialize, tools_list, transport_compliance_probe, step_up_auth_probe, connector_replay_probe, request_association_probe live_validation none
claude_desktop Client-compatible initialize, tools_list, transport_compliance_probe live_validation none
unsafe_for_write_actions Publishing blocked action_safety_probe live_validation none
snapshot_churn_risk Low tool_snapshot_probe, connector_replay_probe history none

Publishability policy profiles

ChatGPT custom connector compatibility
Compatible with review
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance should be in good shape. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: Yes
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Claude remote MCP compatibility
Connector-compatible
Transport behavior should match Claude-compatible HTTP expectations. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: Yes
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No

Compatibility fixtures

ChatGPT custom connector fixture
Degraded
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance should be in good shape.
  • remote_http_endpoint: Passes
  • oauth_discovery: Degraded
  • frozen_tool_snapshot_refresh: Passes
  • request_association: Passes
Anthropic remote MCP fixture
Degraded
Transport behavior should match Claude-compatible HTTP expectations.
  • remote_transport: Passes
  • tool_discovery: Passes
  • auth_connect: Passes
  • safe_write_review: Degraded

Authenticated validation sessions

Public validation is free. Authenticated validation is paid and proves scoped behavior, write-action safeguards, and authenticated tool execution.

Latest profile
remote_mcp
Authenticated session used
Public score isolation
Preview endpoint
/v1/verify
CI preview endpoint
/v1/ci/preview

Public server reputation

Validation success 7d
1.0
Validation success 30d
1.0
Mean time to recover
n/a
Breaking diffs 30d
0
Registry drift frequency 30d
0
Snapshot changes 30d
0

Incident & change feed

TimestampEventDetails
May 13, 2026 02:35:10 PM UTC Latest validation: healthy Score 74.7 with status healthy.
May 13, 2026 02:35:10 PM UTC Score changed Score delta -0.4 versus the previous run.
May 13, 2026 02:34:03 AM UTC Score changed Score delta +0.5 versus the previous run.
May 12, 2026 02:27:35 PM UTC Score changed Score delta +3.1 versus the previous run.

Capabilities

Use-case taxonomy
development database search web

Security posture

Tools analyzed
8
High-risk tools
2
Destructive tools
0
Exec tools
4
Egress tools
1
Secret tools
0
Bulk-access tools
1
Risk distribution
medium:6, high:1, critical:1

Tool capability & risk inventory

ToolCapabilitiesRiskFindingsNotes
analyze_property read write exec admin High command execution admin mutation No explicit safeguard hints detected.
get_buildability_score read exec admin Medium command execution No explicit safeguard hints detected.
lookup_zoning read write admin Medium admin mutation No explicit safeguard hints detected.
check_flood_zone admin Medium none No explicit safeguard hints detected.
check_environmental_risks exec admin Medium command execution No explicit safeguard hints detected.
search_comparable_sales read admin Medium none No explicit safeguard hints detected.
calculate_buildable_envelope read write admin Medium admin mutation No explicit safeguard hints detected.
submit_correction read write exec network admin export Critical command execution arbitrary network egress bulk data access freeform input surface admin mutation Safeguards hinted in metadata.

Write-action governance

Governance status
Error
Safe to publish
Auth boundary
public_or_unclear
Blast radius
High
High-risk tools
2
Confirmation signals
submit_correction
Safeguard count
1

Status detail: 2 high-risk tool(s), 4 exec-capable tool(s) are exposed without a clear auth boundary; 1 safeguard(s) and 1 confirmation signal(s) detected.

ToolRiskFlagsSafeguards
analyze_property High command execution admin mutation no
submit_correction Critical command execution arbitrary network egress bulk data access freeform input surface admin mutation yes

Action-controls diff

Snapshot changed
no
Disabled-by-default candidates
none
Manual review candidates
none
New actions
ActionRiskFlags
No newly added actions.
Changed actions
ActionChange typesRisk
No materially changed actions.

Why this score?

Access & Protocol
36.5/44
Connectivity, auth, and transport expectations for common clients.
Interface Quality
39/56
How well the tool/resource interface communicates and behaves under automation.
Security Posture
22.5/36
How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs.
Reliability & Trust
21/24
Operational stability, consistency, and trustworthiness over time.
Discovery & Governance
21.5/28
How well the server is documented, listed, and governed in public registries.
Adoption & Market
6/8
Adoption clues and public evidence that the server is intended for external use.

Algorithmic score breakdown

Auth Operability
2/4
Measures whether auth discovery and protected access behave predictably for clients.
Error Contract Quality
0/4
Grades machine-readable error structure, status alignment, and remediation hints.
Rate-Limit Semantics
2/4
Checks whether quota/throttle responses are deterministic and automation-friendly.
Schema Completeness
3/4
Completeness of tool descriptions, parameter docs, examples, and schema shape.
Backward Compatibility
4/4
Stability score across tool schema/name drift relative to prior validations.
SLO Health
3/4
Availability, latency, and burst-failure profile across recent validation history.
Security Hygiene
4/4
HTTPS posture, endpoint hygiene, and response-surface hardening checks.
Task Success
4/4
Can an agent reliably initialize, enumerate tools, and execute core MCP flows?
Trust Confidence
2/4
Confidence-adjusted reliability score that penalizes low evidence volume.
Abuse/Noise Resilience
4/4
How well the server preserves core behavior in the presence of noisy traffic patterns.
Prompt Contract
3/4
Quality of prompt metadata, argument shape, and prompt discoverability for clients.
Resource Contract
4/4
How completely resources and resource templates describe URIs, types, and usage shape.
Discovery Metadata
4/4
Homepage, docs, icon, repository, support, and license coverage for directory consumers.
Registry Consistency
2/4
Agreement between stored registry metadata, live server-card data, and current validation output.
Installability
4/4
How cleanly a real client can connect, initialize, enumerate tools, and proceed through auth.
Session Semantics
4/4
Determinism and state behavior across repeated MCP calls, including sticky-session surprises.
Tool Surface Design
3/4
Naming clarity, schema ergonomics, and parameter complexity across the tool surface.
Result Shape Stability
3/4
Stability of declared output schemas across validations, with penalties for drift or missing shapes.
OAuth Interop
3/4
Depth and client compatibility of OAuth/OIDC metadata beyond the minimal protected-resource check.
Recovery Semantics
0/4
Whether failures include actionable machine-readable next steps such as retry or upgrade guidance.
Maintenance Signal
3/4
Versioning, update recency, and historical validation cadence that indicate active stewardship.
Adoption Signal
3/4
Directory presence and distribution clues that suggest the server is intended for external use.
Freshness Confidence
4/4
Confidence that recent validations are current enough and dense enough to trust operationally.
Transport Fidelity
4/4
Whether declared transport metadata matches the observed endpoint behavior and response formats.
Spec Recency
4/4
How close the server’s claimed MCP protocol version is to the latest known public revision.
Session Resume
4/4
Whether Streamable HTTP session identifiers and resumed requests behave cleanly for real clients.
Step-Up Auth
3/4
Whether OAuth metadata and WWW-Authenticate challenges support granular, incremental consent instead of broad upfront scopes.
Transport Compliance
3.5/4
Checks session headers, protocol-version enforcement, session teardown, and expired-session behavior.
Utility Coverage
2/4
Signals support for completions, pagination, and task-oriented utility surfaces that larger clients increasingly expect.
Advanced Capability Coverage
3/4
Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.
Connector Publishability
3/4
How ready the server looks for client catalogs and managed connector programs.
Tool Snapshot Churn
4/4
Stability of the tool surface across recent validations, including add/remove and output-shape drift.
Connector Replay
4/4
Whether a previously published frozen connector snapshot would remain backward compatible after the latest tool refresh.
Request Association
3/4
Whether roots, sampling, and elicitation appear tied to active client requests instead of arriving unsolicited on idle sessions.
Interactive Flow Safety
3/4
Whether prompts and docs steer users toward safe auth flows instead of pasting secrets directly.
Action Safety
2/4
Risk-weighted view of destructive, exec, egress, and confirmation semantics across the tool surface.
Official Registry Presence
4/4
Whether the server appears directly or indirectly in the official MCP registry.
Provenance Divergence
4/4
How closely official registry metadata, the live server card, and public repo/package signals agree with each other.
Safety Transparency
2/4
Clarity of docs, auth disclosure, support links, and other trust signals visible to integrators.
Tool Capability Clarity
4/4
How clearly the tool surface communicates whether each action reads, writes, deletes, executes, or exports data.
Destructive Operation Safety
3/4
Penalizes delete/revoke/destroy style tools unless auth and safeguards reduce blast radius.
Egress / SSRF Resilience
2/4
Assesses arbitrary URL fetch, crawl, webhook, and remote-request exposure on the tool surface.
Execution / Sandbox Safety
0.5/4
Evaluates shell, code, script, and command-execution exposure and whether that surface appears contained.
Data Exfiltration Resilience
2/4
Assesses export, dump, backup, and bulk-read behavior against the surrounding auth and safeguard signals.
Least Privilege Scope
2/4
Rewards scoped auth metadata and penalizes broad or missing scopes around privileged tools.
Secret Handling Hygiene
3/4
Assesses secret-bearing tools, token leakage risk, and whether the public surface avoids obvious secret exposure.
Supply Chain Signal
2.5/4
Public metadata signal for repository, changelog, license, versioning, and recency that supports supply-chain trust.
Input Sanitization Safety
3/4
Penalizes risky freeform string inputs when schemas do not constrain URLs, code, paths, queries, or templates.
Tool Namespace Clarity
4/4
Measures naming uniqueness and ambiguity across the tool namespace to reduce collision and confusion risk.

Compatibility profiles

OpenAI Connectors
66.7
partial
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance should be in good shape.
Connector URL: https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server
# No OAuth metadata detected.
# Server: ai.readypermit/geo
Claude Desktop
83.3
compatible
Transport behavior should match Claude-compatible HTTP expectations.
{
  "mcpServers": {
    "geo": {
      "command": "npx",
      "args": ["mcp-remote", "https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server"]
    }
  }
}
Smithery
80.0
compatible
Machine-readable failure semantics should be present.
smithery mcp add "https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server"
Generic Streamable HTTP
100.0
compatible
No major blockers detected.
curl -sS https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Actionable remediation

SeverityRemediationWhy it mattersRecommended action
High Add confirmation and dry-run semantics for risky actions High-risk write, delete, exec, or egress tools should communicate safeguards clearly. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Align session and protocol behavior with Streamable HTTP expectations Clients increasingly rely on MCP-Protocol-Version, session teardown, and expired-session semantics. Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec.
Playbook
  • Return `Mcp-Session-Id` and `Mcp-Protocol-Version` headers consistently on streamable HTTP responses.
  • Honor `DELETE` session teardown and return `404` when a deleted session is reused.
  • Reject invalid protocol-version headers with `400 Bad Request`.
High Associate roots, sampling, and elicitation with active client requests Modern MCP guidance expects roots, sampling, and elicitation traffic to be tied to an active client request instead of arriving unsolicited on idle sessions. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Expose /.well-known/oauth-protected-resource Without a protected-resource document, OAuth clients cannot discover auth requirements reliably. Serve /.well-known/oauth-protected-resource and point it at your authorization server metadata.
Playbook
  • Serve `/.well-known/oauth-protected-resource` from the same host as the MCP endpoint.
  • Point it at the authorization server metadata URL.
  • Confirm clients receive consistent auth hints before tool execution.
High Publish OAuth authorization-server metadata Clients need authorization-server metadata to discover issuer, endpoints, and DCR support. Publish /.well-known/oauth-authorization-server from your issuer and include registration_endpoint when supported.
Playbook
  • Publish `/.well-known/oauth-authorization-server` from the issuer.
  • Add `registration_endpoint` if DCR is supported.
  • Verify issuer, authorization, token, and jwks metadata are all reachable.
High Publish a complete server card Missing or incomplete server-card metadata weakens discovery, documentation, and trust signals. Serve /.well-known/mcp/server-card.json and include tools, prompts/resources, homepage, and support links.
Playbook
  • Publish `/.well-known/mcp/server-card.json`.
  • Include homepage, repository, support, tools, prompts/resources, and auth metadata.
  • Revalidate the server after publishing the card.
High Stop asking users to paste secrets directly Public MCP servers should prefer OAuth or browser-based auth guidance over in-band secret collection. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Adopt a current MCP protocol revision Older protocol revisions reduce compatibility with newer clients and registry programs. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Close connector-publishing gaps Connector catalogs care about protocol recency, session behavior, auth clarity, and tool-surface stability. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Document minimal scopes and return cleaner auth challenges Modern clients expect granular scopes and step-up auth signals such as WWW-Authenticate scope hints. Return granular scopes and WWW-Authenticate challenge hints instead of forcing overly broad auth upfront.
Playbook
  • Advertise the narrowest viable scopes in OAuth metadata.
  • Return `WWW-Authenticate` challenges with scope or insufficient-scope hints when additional consent is needed.
  • Revalidate with both public discovery and auth-required flows.
Medium Publish OpenID configuration OIDC metadata improves token validation and client compatibility. Expose /.well-known/openid-configuration with issuer, jwks_uri, and supported grants.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Low Expose modern utility surfaces like completions, pagination, or tasks Utility coverage improves interoperability with larger clients and long-lived agent workflows. Expose completions, pagination, and task metadata where supported so larger clients can plan and resume work safely.
Playbook
  • Advertise `completions`, pagination cursors, and `tasks` only when they are actually supported.
  • Return `nextCursor` on large list operations when pagination is available.
  • Document task support and whether it requires step-up auth.
Low Publish newer MCP capability signals Roots, sampling, elicitation, structured outputs, and related metadata improve client understanding and ranking. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.

Point loss breakdown

ComponentCurrentPoints missing
Recovery Semantics 0/4 -4.0
Error Contract 0/4 -4.0
Execution Sandbox Safety 0.5/4 -3.5
Utility Coverage 2/4 -2.0
Trust Confidence 2/4 -2.0
Safety Transparency 2/4 -2.0
Registry Consistency 2/4 -2.0
Rate Limit Semantics 2/4 -2.0
Least Privilege Scope 2/4 -2.0
Egress SSRF Resilience 2/4 -2.0
Data Exfiltration Resilience 2/4 -2.0
Auth Operability 2/4 -2.0

Validation diff

Score delta
-0.42
Summary changed
no
Tool delta
0
Prompt delta
0
Auth mode changed
no
Write surface expanded
no
Protocol regressed
no
Registry drift changed
no

Regressed checks: none

Improved checks: none

ComponentPreviousLatestDelta
trust_confidence_score3.812.0-1.81
freshness_confidence_score3.04.01.0

Tool snapshot diff & changelog

Snapshot changed
no
Added tools
none
Removed tools
none
Required-argument changes
ToolAdded required argsRemoved required args
No required-argument changes detected.
Output-schema drift
ToolPrevious propertiesLatest properties
No output-schema drift detected.

Connector replay

Status
OK
Backward compatible
Would break after refresh
Added tools
none
Removed tools
none
Additive output changes
none
Required-argument replay breaks
ToolAdded required argsRemoved required args
No required-argument replay breaks detected.
Output-schema replay breaks
ToolRemoved propertiesAdded properties
No output-schema replay breaks detected.

Transport compliance drilldown

Probe status
Error
Transport
streamable-http
Session header
yes
Protocol header
no
Bad protocol response
200
DELETE teardown
200
Expired session retry
200
Last-Event-ID visible
no

Issues: missing_protocol_header, bad_protocol_not_rejected, expired_session_not_404

Request association

Status
Missing
Advertised capabilities
none
Observed idle methods
none
Violating methods
none
Probe HTTP status
n/a
Issues
none

Utility coverage

Probe status
Missing
Completions
not detected
Completion probe target: { "argument_name": "address", "name": "investor_analysis", "type": "prompt" }
Pagination
not detected
No nextCursor evidence.
Tasks
Missing
Advertised: no

Benchmark tasks

Benchmark taskStatusEvidence
Discover tools Passes
  • initializeOK
  • tools_listOK
Read-only fetch flow Passes
  • resource_readOK
  • read_only_tool_surfaceMissing
OAuth-required connect Degraded
  • oauth_protected_resourceError
  • step_up_auth_probeMissing
Safe write flow with confirmation Likely to fail
  • action_safety_probeError

Registry & provenance divergence

Probe status
OK
Direct official match
yes
Drift fields
none
FieldRegistryLive server card
Titlen/an/a
Versionn/an/a
Homepagen/an/a

Active alerts

No active alerts for the current server state.

Aliases & registry graph

IdentifierSourceCanonicalScore
ai.readypermit/geo official_registry yes 74.74

Alias consolidation

Canonical identifier
ai.readypermit/geo
Duplicate aliases
0
Registry sources
official_registry
Source disagreements
FieldWhat differsObserved values
No source disagreements detected.

Install snippets

Openai Connectors
Connector URL: https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server
# No OAuth metadata detected.
# Server: ai.readypermit/geo
Claude Desktop
{
  "mcpServers": {
    "geo": {
      "command": "npx",
      "args": ["mcp-remote", "https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server"]
    }
  }
}
Smithery
smithery mcp add "https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server"
Generic Http
curl -sS https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Agent access & tool surface

Live server tools
analyze_property get_buildability_score lookup_zoning check_flood_zone check_environmental_risks search_comparable_sales calculate_buildable_envelope submit_correction
Observed from the latest live validation against https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server. This is the target server surface, not Verify's own inspection tools.
Live capability counts
8 tools • 7 prompts • 1 resources
Counts come from the latest tools/list, prompts/list, and resources/list checks.
Inspect with Verify
search fetch search_servers recommend_servers get_server_report compare_servers
Use Verify itself to search, recommend, compare, and fetch the full report for ai.readypermit/geo.
Direct machine links

Claims & monitoring

Server ownership

No verified maintainer claim recorded.

Watch subscriptions
0
Teams: none

Alert routing

Active watches
0
Generic webhooks
0
Slack routes
0
Teams routes
0
Email routes
0
WatchTeamChannelsMinimum severity
No active watch destinations.

Maintainer analytics

Validation Run Count
4
Average Latency Ms
3368.98
Healthy Run Ratio Recent
1.0
Registry Presence Count
1
Active Alert Count
0
Watcher Count
0
Verified Claim
False
Taxonomy Tags
development, database, search, web
Score Trend
74.74, 75.16, 74.71, 71.56
Remediation Count
13
High Risk Tool Count
2
Destructive Tool Count
0
Exec Tool Count
4

Maintainer response quality

Score
16.67
Verified claim
Support contact
Changelog present
Incident notes present
Tool changes documented
Annotation history
Annotation count
0

Maintainer annotations

No maintainer annotations have been recorded yet.

Maintainer rebuttals & expected behavior

No maintainer rebuttals or expected-behavior overrides are recorded yet.

Latest validation evidence

Latest summary
Healthy
Validation profile
remote_mcp
Started
May 13, 2026 02:35:07 PM UTC
Latency
3379.0 ms

Failures

Checks

CheckStatusLatencyEvidence
action_safety_probe Error n/a 2 high-risk, 4 exec-capable tool(s); no clear auth boundary; safeguards=1; confirmation=submit correction.
advanced_capabilities_probe Warning n/a Only 3 capability signal(s): prompts, resource links, resources.
connector_publishability_probe Warning n/a Publishability blockers: transport compliance, action safety, server card.
connector_replay_probe OK n/a Backward compatible with no breaking tool-surface changes.
determinism_probe OK 181.8 ms Check completed
initialize OK 291.3 ms Protocol 2024-11-05
interactive_flow_probe Missing n/a Check completed
oauth_authorization_server Missing n/a no authorization server
oauth_protected_resource Error 15.2 ms Client error '404 Not Found' for url 'https://rnfonkwthefktfvfwypr.supabase.co/.well-known/oauth-protected-resource' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
official_registry_probe OK n/a Check completed
openid_configuration Missing n/a no authorization server
probe_noise_resilience OK 9.0 ms Fetched https://rnfonkwthefktfvfwypr.supabase.co/robots.txt
prompt_get OK 583.8 ms 1 prompt message(s) returned
prompts_list OK 173.3 ms 7 prompt(s) exposed
protocol_version_probe Warning n/a Claims 2024-11-05; 3 release(s) behind 2025-11-25.
provenance_divergence_probe OK n/a Check completed
request_association_probe Missing n/a No request-association capabilities were advertised.
resource_read OK 545.0 ms 1 resource content item(s) returned
resources_list OK 167.4 ms 1 resource item(s) exposed
server_card Error 47.6 ms Client error '404 Not Found' for url 'https://rnfonkwthefktfvfwypr.supabase.co/.well-known/mcp/server-card.json' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
session_resume_probe OK 222.4 ms 8 tool(s) exposed
step_up_auth_probe Missing n/a No OAuth or incremental-scope signals detected.
tool_snapshot_probe OK n/a Check completed
tools_list OK 217.7 ms 8 tool(s) exposed
transport_compliance_probe Error 270.9 ms Issues: missing protocol header, bad protocol not rejected, expired session not 404 (bad protocol=200, DELETE=200, expired session=200).
utility_coverage_probe Missing 188.5 ms No completions evidence; no pagination evidence; tasks missing.

Raw evidence view

Show raw JSON evidence
{
  "checks": {
    "action_safety_probe": {
      "details": {
        "auth_present": false,
        "confirmation_signals": [
          "submit_correction"
        ],
        "safeguard_count": 1,
        "summary": {
          "bulk_access_tools": 1,
          "capability_distribution": {
            "admin": 8,
            "exec": 4,
            "export": 1,
            "network": 1,
            "read": 6,
            "write": 4
          },
          "destructive_tools": 0,
          "egress_tools": 1,
          "exec_tools": 4,
          "high_risk_tools": 2,
          "risk_distribution": {
            "critical": 1,
            "high": 1,
            "low": 0,
            "medium": 6
          },
          "secret_tools": 0,
          "tool_count": 8
        }
      },
      "latency_ms": null,
      "status": "error"
    },
    "advanced_capabilities_probe": {
      "details": {
        "capabilities": {
          "completions": false,
          "elicitation": false,
          "prompts": true,
          "resource_links": true,
          "resources": true,
          "roots": false,
          "sampling": false,
          "structured_outputs": false
        },
        "enabled": [
          "prompts",
          "resource_links",
          "resources"
        ],
        "enabled_count": 3,
        "initialize_capability_keys": [
          "prompts",
          "resources",
          "tools"
        ]
      },
      "latency_ms": null,
      "status": "warning"
    },
    "connector_publishability_probe": {
      "details": {
        "blockers": [
          "transport_compliance",
          "action_safety",
          "server_card"
        ],
        "criteria": {
          "action_safety": false,
          "auth_flow": true,
          "connector_replay": true,
          "initialize": true,
          "protocol_version": true,
          "remote_transport": true,
          "request_association": true,
          "server_card": false,
          "session_resume": true,
          "step_up_auth": true,
          "tool_surface": true,
          "tools_list": true,
          "transport_compliance": false
        },
        "high_risk_tools": 2,
        "tool_count": 8,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "connector_replay_probe": {
      "details": {
        "added_tools": [],
        "additive_output_changes": [],
        "backward_compatible": true,
        "output_breaks": [],
        "removed_tools": [],
        "required_arg_breaks": [],
        "would_break_after_refresh": false
      },
      "latency_ms": null,
      "status": "ok"
    },
    "determinism_probe": {
      "details": {
        "attempts": 2,
        "baseline_signature": "44ea97ce880beebbb85cc8f0c9c2ece57163d197938270f805dc54f04ee1cc4b",
        "errors": [],
        "matches": 2,
        "stable_ratio": 1.0,
        "successful": 2
      },
      "latency_ms": 181.77,
      "status": "ok"
    },
    "initialize": {
      "details": {
        "headers": {
          "content-type": "application/json",
          "mcp-session-id": "1267abe1-2908-44f0-ac1f-baf89e0e965d",
          "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
        },
        "http_status": 200,
        "payload": {
          "id": 1,
          "jsonrpc": "2.0",
          "result": {
            "capabilities": {
              "prompts": {
                "listChanged": false
              },
              "resources": {
                "listChanged": false,
                "subscribe": false
              },
              "tools": {
                "listChanged": false
              }
            },
            "protocolVersion": "2024-11-05",
            "serverInfo": {
              "name": "readypermit",
              "version": "1.2.3"
            }
          }
        },
        "url": "https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server"
      },
      "latency_ms": 291.31,
      "status": "ok"
    },
    "interactive_flow_probe": {
      "details": {
        "oauth_supported": false,
        "prompt_available": true,
        "risk_hits": [],
        "safe_hits": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_authorization_server": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_protected_resource": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://rnfonkwthefktfvfwypr.supabase.co/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://rnfonkwthefktfvfwypr.supabase.co/.well-known/oauth-protected-resource"
      },
      "latency_ms": 15.19,
      "status": "error"
    },
    "official_registry_probe": {
      "details": {
        "direct_match": true,
        "official_peer_count": 1,
        "registry_identifier": "ai.readypermit/geo",
        "registry_source": "official_registry"
      },
      "latency_ms": null,
      "status": "ok"
    },
    "openid_configuration": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "probe_noise_resilience": {
      "details": {
        "headers": {
          "content-type": "application/json",
          "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
        },
        "http_status": 404,
        "url": "https://rnfonkwthefktfvfwypr.supabase.co/robots.txt"
      },
      "latency_ms": 9.04,
      "status": "ok"
    },
    "prompt_get": {
      "details": {
        "headers": {
          "content-type": "application/json",
          "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
        },
        "http_status": 200,
        "payload": {
          "id": 4,
          "jsonrpc": "2.0",
          "result": {
            "messages": [
              {
                "content": {
                  "text": "Analyze the property as a real estate investment. Use the analyze_property tool with persona \"investor\" to pull the data, then provide:\n1. GO / NO-GO / CONDITIONAL verdict (lead with this)\n2. Buildability Score and what it means for this deal\n3. Cap rate estimate based on comparable sales and rental data\n4. Value-add opportunities (ADU, subdivision, density increase)\n5. Risk flags that could kill or delay the deal \u2014 be specific about WHICH risks\n6. What you'd do next if pursuing this deal (first 3 concrete steps with costs)",
                  "type": "text"
                },
                "role": "user"
              }
            ]
          }
        },
        "prompt_arguments": [
          {
            "description": "Property address to analyze",
            "name": "address",
            "required": true
          }
        ],
        "prompt_name": "investor_analysis",
        "url": "https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server"
      },
      "latency_ms": 583.78,
      "status": "ok"
    },
    "prompts_list": {
      "details": {
        "headers": {
          "content-type": "application/json",
          "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
        },
        "http_status": 200,
        "payload": {
          "id": 3,
          "jsonrpc": "2.0",
          "result": {
            "prompts": [
              {
                "arguments": [
                  {
                    "description": "Property address to analyze",
                    "name": "address",
                    "required": true
                  }
                ],
                "description": "Analyze a property as a real estate investment. Includes cap rate estimate, comparable deals, risk flags, value-add potential, and a go/no-go recommendation. USE FOR: deal evaluation, portfolio screening, value-add identification.",
                "name": "investor_analysis"
              },
              {
                "arguments": [
                  {
                    "description": "Site address to evaluate",
                    "name": "address",
                    "required": true
                  }
                ],
                "description": "Run a feasibility study on a development site. Covers FAR, setbacks, height limits, environmental clearances, entitlement path, permit timeline, and estimated costs. USE FOR: site selection, entitlement planning, pro forma inputs.",
                "name": "developer_feasibility"
              },
              {
                "arguments": [
                  {
                    "description": "Property address to check",
                    "name": "address",
                    "required": true
                  }
                ],
                "description": "Explain what a homeowner can build on their property in plain English. ADU eligibility, addition potential, setback requirements, permit steps, and estimated costs. USE FOR: ADU questions, renovation planning, permit guidance.",
                "name": "homeowner_guide"
              },
              {
                "arguments": [
                  {
                    "description": "Property address to assess",
                    "name": "address",
                    "required": true
                  }
                ],
                "description": "Assess a property for collateral, insurance, or compliance risk. Covers zoning conformance, environmental liability (Phase I triggers), flood insurance requirements, wildfire/seismic exposure, and a risk grade. USE FOR: loan underwriting, insurance underwriting, due diligence, title review.",
                "name": "risk_assessment"
              },
              {
                "arguments": [
                  {
                    "description": "Property address (or comma-separated list of addresses) to screen",
                    "name": "address",
                    "required": true
                  }
                ],
                "description": "Quick screen one or more properties for investment viability. Returns buildability score, fatal flaws, and a rank recommendation. USE FOR: wholesaler deal flow, portfolio filtering, batch pre-screening, 'is this worth a deeper look' questions.",
                "name": "deal_screening"
              },
              {
                "arguments": [
                  {
                    "description": "Property address the client is asking about",
                    "name": "address",
                    "required": true
                  }
                ],
                "description": "Generate a client-ready property brief a broker can share immediately. Covers buildability, zoning, risks, and next steps in professional but accessible language. USE FOR: client meetings, listing presentations, buyer consultations, 'can I build on this?' questions from clients.",
                "name": "broker_intel"
              },
              {
                "arguments": [
                  {
                    "description": "Property address to pull data for",
                    "name": "address",
                    "required": true
                  }
                ],
                "description": "Return structured property data as clean JSON without narrative or persona framing. USE FOR: API integrations, data pipelines, proptech product feeds, programmatic analysis where you need machine-readable output rather than human-readable summaries.",
                "name": "raw_data"
              }
            ]
          }
        },
        "url": "https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server"
      },
      "latency_ms": 173.29,
      "status": "ok"
    },
    "protocol_version_probe": {
      "details": {
        "claimed_version": "2024-11-05",
        "lag_days": 385,
        "latest_known_version": "2025-11-25",
        "releases_behind": 3,
        "validator_protocol_version": "2025-03-26"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "provenance_divergence_probe": {
      "details": {
        "direct_official_match": true,
        "drift_fields": [],
        "metadata_document_count": 2,
        "registry_homepage": null,
        "registry_repository": null,
        "registry_title": null,
        "registry_version": null,
        "server_card_homepage": null,
        "server_card_repository": null,
        "server_card_title": null,
        "server_card_version": null
      },
      "latency_ms": null,
      "status": "ok"
    },
    "request_association_probe": {
      "details": {
        "reason": "no_request_association_capabilities_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resource_read": {
      "details": {
        "headers": {
          "content-type": "application/json",
          "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
        },
        "http_status": 200,
        "payload": {
          "id": 6,
          "jsonrpc": "2.0",
          "result": {
            "contents": [
              {
                "mimeType": "application/json",
                "text": "{\n  \"generatedAt\": \"2026-05-13T14:35:09.096Z\",\n  \"schema\": \"readypermit/corrections-feed/v1\",\n  \"description\": \"Verified/applied corrections to ReadyPermit pages. This is the civic-feedback flywheel that backs the 48-hour SLA promised by the submit_correction tool. Sorted by most-recent update.\",\n  \"count\": 0,\n  \"corrections\": []\n}",
                "uri": "readypermit://corrections/recent"
              }
            ]
          }
        },
        "resource_uri": "readypermit://corrections/recent",
        "url": "https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server"
      },
      "latency_ms": 544.96,
      "status": "ok"
    },
    "resources_list": {
      "details": {
        "headers": {
          "content-type": "application/json",
          "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
        },
        "http_status": 200,
        "payload": {
          "id": 5,
          "jsonrpc": "2.0",
          "result": {
            "resources": [
              {
                "description": "Last 100 corrections to ReadyPermit pages that have been verified or applied. Each entry is a real edit that improved the dataset, with city, topic, source, and timestamps. Surfaces the civic-feedback flywheel that drives the Staff Responsiveness dimension of Buildability City Score\u2122.",
                "mimeType": "application/json",
                "name": "Recent confirmed corrections",
                "uri": "readypermit://corrections/recent"
              }
            ]
          }
        },
        "url": "https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server"
      },
      "latency_ms": 167.43,
      "status": "ok"
    },
    "server_card": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://rnfonkwthefktfvfwypr.supabase.co/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://rnfonkwthefktfvfwypr.supabase.co/.well-known/mcp/server-card.json"
      },
      "latency_ms": 47.62,
      "status": "error"
    },
    "session_resume_probe": {
      "details": {
        "headers": {
          "content-type": "application/json",
          "mcp-session-id": "1267abe1-2908-44f0-ac1f-baf89e0e965d",
          "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
        },
        "http_status": 200,
        "payload": {
          "id": 301,
          "jsonrpc": "2.0",
          "result": {
            "tools": [
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": true,
                  "readOnlyHint": true,
                  "title": "Analyze Property (Full Buildability Report)"
                },
                "description": "Get complete property intelligence for any U.S. address \u2014 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\u2122 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 $2,000-$4,500 zoning consultant work.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Full U.S. property address (e.g., '123 Main St, Denver, CO 80202'). Accepts any format \u2014 will be geocoded.",
                      "type": "string"
                    },
                    "persona": {
                      "description": "User persona for tailored analysis (optional). Changes tone and emphasis: investor=deal metrics, developer=feasibility, homeowner=plain English, lender=collateral risk, broker=disclosure items.",
                      "enum": [
                        "investor",
                        "developer",
                        "homeowner",
                        "lender",
                        "broker"
                      ],
                      "type": "string"
                    }
                  },
                  "required": [
                    "address"
                  ],
                  "type": "object"
                },
                "name": "analyze_property"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": true,
                  "readOnlyHint": true,
                  "title": "Get Buildability Score (Quick Screen)"
                },
                "description": "Get a quick Buildability\u2122 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 \u2014 use for deal screening and portfolio filtering.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Full U.S. property address",
                      "type": "string"
                    }
                  },
                  "required": [
                    "address"
                  ],
                  "type": "object"
                },
                "name": "get_buildability_score"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": true,
                  "readOnlyHint": true,
                  "title": "Lookup Zoning (Permitted Uses)"
                },
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Full U.S. property address",
                      "type": "string"
                    }
                  },
                  "required": [
                    "address"
                  ],
                  "type": "object"
                },
                "name": "lookup_zoning"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": true,
                  "readOnlyHint": true,
                  "title": "Check FEMA Flood Zone"
                },
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Full U.S. property address",
                      "type": "string"
                    }
                  },
                  "required": [
                    "address"
                  ],
                  "type": "object"
                },
                "name": "check_flood_zone"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": true,
                  "readOnlyHint": true,
                  "title": "Check Environmental Risks"
                },
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Full U.S. property address (preferred \u2014 gives best results)",
                      "type": "string"
                    },
                    "latitude": {
                      "description": "Property latitude (use if no address available)",
                      "type": "number"
                    },
                    "longitude": {
                      "description": "Property longitude (use if no address available)",
                      "type": "number"
                    }
                  },
                  "required": [],
                  "type": "object"
                },
                "name": "check_environmental_risks"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": false,
                  "openWorldHint": true,
                  "readOnlyHint": true,
                  "title": "Search Comparable Sales"
                },
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Full U.S. property address (preferred \u2014 gives best results)",
                      "type": "string"
                    },
                    "latitude": {
                      "description": "Center latitude for search (use if no address available)",
                      "type": "number"
                    },
                    "longitude": {
                      "description": "Center longitude for search (use if no address available)",
                      "type": "number"
                    },
                    "radius_miles": {
                      "description": "Search radius in miles (default: 0.5, max: 5)",
                      "type": "number"
                    }
                  },
                  "required": [],
                  "type": "object"
                },
                "name": "search_comparable_sales"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": false,
                  "readOnlyHint": true,
                  "title": "Calculate Buildable Envelope"
                },
                "description": "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 \u00d7 width \u00d7 height), usable footprint, and coverage math. Takes lot area, setbacks, FAR, height limit, and coverage as inputs \u2014 a pure calculation tool, does not query data.",
                "inputSchema": {
                  "properties": {
                    "front_setback_ft": {
                      "description": "Front setback in feet (distance from front property line)",
                      "type": "number"
                    },
                    "lot_area_sqft": {
                      "description": "Total lot area in square feet",
                      "type": "number"
                    },
                    "max_far": {
                      "description": "Maximum floor area ratio (e.g., 0.5, 2.0). FAR = building area / lot area.",
                      "type": "number"
                    },
                    "max_height_ft": {
                      "description": "Maximum building height in feet",
                      "type": "number"
                    },
                    "max_lot_coverage": {
                      "description": "Maximum lot coverage as decimal (e.g., 0.45 for 45%)",
                      "type": "number"
                    },
                    "rear_setback_ft": {
                      "description": "Rear setback in feet",
                      "type": "number"
                    },
                    "side_setback_ft": {
                      "description": "Side setback in feet (each side)",
                      "type": "number"
                    }
                  },
                  "required": [
                    "lot_area_sqft"
                  ],
                  "type": "object"
                },
                "name": "calculate_buildable_envelope"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": false,
                  "openWorldHint": true,
                  "readOnlyHint": false,
                  "title": "Submit Correction"
                },
                "description": "Report an error on a ReadyPermit page so Buildability\u2122 can verify and update. USE WHEN: a user mentions that information on ReadyPermit 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 \u2014 this is the civic-infrastructure feedback loop Buildability\u2122 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\u2122. RETURNS: a correction ID for tracking + status.",
                "inputSchema": {
                  "properties": {
                    "issue": {
                      "description": "What is incorrect or outdated. Be specific \u2014 mention the exact fact, rule, or data point.",
                      "type": "string"
                    },
                    "pageUrl": {
                      "description": "Full ReadyPermit URL where the error appears (e.g., 'https://readypermit.ai/adu/los-angeles').",
                      "type": "string"
                    },
                    "reporterContext": {
                      "description": "Optional: how the error was discovered (e.g., 'user self-reported during property research conversation', 'comparing to Austin Code \u00a725-2-1604').",
                      "type": "string"
                    },
                    "sourceDocument": {
                      "description": "Optional: citation or URL supporting the correction (city ordinance, state law, news article, planning department page).",
                      "type": "string"
                    },
                    "suggestion": {
                      "description": "Optional: what the correct information is, if known.",
                      "type": "string"
                    }
                  },
                  "required": [
                    "pageUrl",
                    "issue"
                  ],
                  "type": "object"
                },
                "name": "submit_correction"
              }
            ]
          }
        },
        "requested_protocol_version": "2024-11-05",
        "resumed": true,
        "session_id_present": true,
        "transport": "streamable-http",
        "url": "https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server"
      },
      "latency_ms": 222.43,
      "status": "ok"
    },
    "step_up_auth_probe": {
      "details": {
        "auth_required_checks": [],
        "broad_scopes": [],
        "challenge_headers": [],
        "minimal_scope_documented": false,
        "oauth_present": false,
        "scope_specificity_ratio": 0.0,
        "step_up_signals": [],
        "supported_scopes": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tool_snapshot_probe": {
      "details": {
        "added": [],
        "changed_outputs": [],
        "current_tool_count": 8,
        "previous_tool_count": 8,
        "removed": [],
        "similarity": 1.0
      },
      "latency_ms": null,
      "status": "ok"
    },
    "tools_list": {
      "details": {
        "headers": {
          "content-type": "application/json",
          "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
        },
        "http_status": 200,
        "payload": {
          "id": 2,
          "jsonrpc": "2.0",
          "result": {
            "tools": [
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": true,
                  "readOnlyHint": true,
                  "title": "Analyze Property (Full Buildability Report)"
                },
                "description": "Get complete property intelligence for any U.S. address \u2014 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\u2122 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 $2,000-$4,500 zoning consultant work.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Full U.S. property address (e.g., '123 Main St, Denver, CO 80202'). Accepts any format \u2014 will be geocoded.",
                      "type": "string"
                    },
                    "persona": {
                      "description": "User persona for tailored analysis (optional). Changes tone and emphasis: investor=deal metrics, developer=feasibility, homeowner=plain English, lender=collateral risk, broker=disclosure items.",
                      "enum": [
                        "investor",
                        "developer",
                        "homeowner",
                        "lender",
                        "broker"
                      ],
                      "type": "string"
                    }
                  },
                  "required": [
                    "address"
                  ],
                  "type": "object"
                },
                "name": "analyze_property"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": true,
                  "readOnlyHint": true,
                  "title": "Get Buildability Score (Quick Screen)"
                },
                "description": "Get a quick Buildability\u2122 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 \u2014 use for deal screening and portfolio filtering.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Full U.S. property address",
                      "type": "string"
                    }
                  },
                  "required": [
                    "address"
                  ],
                  "type": "object"
                },
                "name": "get_buildability_score"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": true,
                  "readOnlyHint": true,
                  "title": "Lookup Zoning (Permitted Uses)"
                },
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Full U.S. property address",
                      "type": "string"
                    }
                  },
                  "required": [
                    "address"
                  ],
                  "type": "object"
                },
                "name": "lookup_zoning"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": true,
                  "readOnlyHint": true,
                  "title": "Check FEMA Flood Zone"
                },
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Full U.S. property address",
                      "type": "string"
                    }
                  },
                  "required": [
                    "address"
                  ],
                  "type": "object"
                },
                "name": "check_flood_zone"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": true,
                  "readOnlyHint": true,
                  "title": "Check Environmental Risks"
                },
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Full U.S. property address (preferred \u2014 gives best results)",
                      "type": "string"
                    },
                    "latitude": {
                      "description": "Property latitude (use if no address available)",
                      "type": "number"
                    },
                    "longitude": {
                      "description": "Property longitude (use if no address available)",
                      "type": "number"
                    }
                  },
                  "required": [],
                  "type": "object"
                },
                "name": "check_environmental_risks"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": false,
                  "openWorldHint": true,
                  "readOnlyHint": true,
                  "title": "Search Comparable Sales"
                },
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Full U.S. property address (preferred \u2014 gives best results)",
                      "type": "string"
                    },
                    "latitude": {
                      "description": "Center latitude for search (use if no address available)",
                      "type": "number"
                    },
                    "longitude": {
                      "description": "Center longitude for search (use if no address available)",
                      "type": "number"
                    },
                    "radius_miles": {
                      "description": "Search radius in miles (default: 0.5, max: 5)",
                      "type": "number"
                    }
                  },
                  "required": [],
                  "type": "object"
                },
                "name": "search_comparable_sales"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": false,
                  "readOnlyHint": true,
                  "title": "Calculate Buildable Envelope"
                },
                "description": "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 \u00d7 width \u00d7 height), usable footprint, and coverage math. Takes lot area, setbacks, FAR, height limit, and coverage as inputs \u2014 a pure calculation tool, does not query data.",
                "inputSchema": {
                  "properties": {
                    "front_setback_ft": {
                      "description": "Front setback in feet (distance from front property line)",
                      "type": "number"
                    },
                    "lot_area_sqft": {
                      "description": "Total lot area in square feet",
                      "type": "number"
                    },
                    "max_far": {
                      "description": "Maximum floor area ratio (e.g., 0.5, 2.0). FAR = building area / lot area.",
                      "type": "number"
                    },
                    "max_height_ft": {
                      "description": "Maximum building height in feet",
                      "type": "number"
                    },
                    "max_lot_coverage": {
                      "description": "Maximum lot coverage as decimal (e.g., 0.45 for 45%)",
                      "type": "number"
                    },
                    "rear_setback_ft": {
                      "description": "Rear setback in feet",
                      "type": "number"
                    },
                    "side_setback_ft": {
                      "description": "Side setback in feet (each side)",
                      "type": "number"
                    }
                  },
                  "required": [
                    "lot_area_sqft"
                  ],
                  "type": "object"
                },
                "name": "calculate_buildable_envelope"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": false,
                  "openWorldHint": true,
                  "readOnlyHint": false,
                  "title": "Submit Correction"
                },
                "description": "Report an error on a ReadyPermit page so Buildability\u2122 can verify and update. USE WHEN: a user mentions that information on ReadyPermit 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 \u2014 this is the civic-infrastructure feedback loop Buildability\u2122 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\u2122. RETURNS: a correction ID for tracking + status.",
                "inputSchema": {
                  "properties": {
                    "issue": {
                      "description": "What is incorrect or outdated. Be specific \u2014 mention the exact fact, rule, or data point.",
                      "type": "string"
                    },
                    "pageUrl": {
                      "description": "Full ReadyPermit URL where the error appears (e.g., 'https://readypermit.ai/adu/los-angeles').",
                      "type": "string"
                    },
                    "reporterContext": {
                      "description": "Optional: how the error was discovered (e.g., 'user self-reported during property research conversation', 'comparing to Austin Code \u00a725-2-1604').",
                      "type": "string"
                    },
                    "sourceDocument": {
                      "description": "Optional: citation or URL supporting the correction (city ordinance, state law, news article, planning department page).",
                      "type": "string"
                    },
                    "suggestion": {
                      "description": "Optional: what the correct information is, if known.",
                      "type": "string"
                    }
                  },
                  "required": [
                    "pageUrl",
                    "issue"
                  ],
                  "type": "object"
                },
                "name": "submit_correction"
              }
            ]
          }
        },
        "url": "https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server"
      },
      "latency_ms": 217.7,
      "status": "ok"
    },
    "transport_compliance_probe": {
      "details": {
        "bad_protocol_error": null,
        "bad_protocol_headers": {
          "content-type": "application/json",
          "mcp-session-id": "1267abe1-2908-44f0-ac1f-baf89e0e965d",
          "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
        },
        "bad_protocol_payload": {
          "id": 410,
          "jsonrpc": "2.0",
          "result": {
            "tools": [
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": true,
                  "readOnlyHint": true,
                  "title": "Analyze Property (Full Buildability Report)"
                },
                "description": "Get complete property intelligence for any U.S. address \u2014 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\u2122 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 $2,000-$4,500 zoning consultant work.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Full U.S. property address (e.g., '123 Main St, Denver, CO 80202'). Accepts any format \u2014 will be geocoded.",
                      "type": "string"
                    },
                    "persona": {
                      "description": "User persona for tailored analysis (optional). Changes tone and emphasis: investor=deal metrics, developer=feasibility, homeowner=plain English, lender=collateral risk, broker=disclosure items.",
                      "enum": [
                        "investor",
                        "developer",
                        "homeowner",
                        "lender",
                        "broker"
                      ],
                      "type": "string"
                    }
                  },
                  "required": [
                    "address"
                  ],
                  "type": "object"
                },
                "name": "analyze_property"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": true,
                  "readOnlyHint": true,
                  "title": "Get Buildability Score (Quick Screen)"
                },
                "description": "Get a quick Buildability\u2122 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 \u2014 use for deal screening and portfolio filtering.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Full U.S. property address",
                      "type": "string"
                    }
                  },
                  "required": [
                    "address"
                  ],
                  "type": "object"
                },
                "name": "get_buildability_score"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": true,
                  "readOnlyHint": true,
                  "title": "Lookup Zoning (Permitted Uses)"
                },
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Full U.S. property address",
                      "type": "string"
                    }
                  },
                  "required": [
                    "address"
                  ],
                  "type": "object"
                },
                "name": "lookup_zoning"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": true,
                  "readOnlyHint": true,
                  "title": "Check FEMA Flood Zone"
                },
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Full U.S. property address",
                      "type": "string"
                    }
                  },
                  "required": [
                    "address"
                  ],
                  "type": "object"
                },
                "name": "check_flood_zone"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": true,
                  "readOnlyHint": true,
                  "title": "Check Environmental Risks"
                },
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Full U.S. property address (preferred \u2014 gives best results)",
                      "type": "string"
                    },
                    "latitude": {
                      "description": "Property latitude (use if no address available)",
                      "type": "number"
                    },
                    "longitude": {
                      "description": "Property longitude (use if no address available)",
                      "type": "number"
                    }
                  },
                  "required": [],
                  "type": "object"
                },
                "name": "check_environmental_risks"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": false,
                  "openWorldHint": true,
                  "readOnlyHint": true,
                  "title": "Search Comparable Sales"
                },
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "address": {
                      "description": "Full U.S. property address (preferred \u2014 gives best results)",
                      "type": "string"
                    },
                    "latitude": {
                      "description": "Center latitude for search (use if no address available)",
                      "type": "number"
                    },
                    "longitude": {
                      "description": "Center longitude for search (use if no address available)",
                      "type": "number"
                    },
                    "radius_miles": {
                      "description": "Search radius in miles (default: 0.5, max: 5)",
                      "type": "number"
                    }
                  },
                  "required": [],
                  "type": "object"
                },
                "name": "search_comparable_sales"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": true,
                  "openWorldHint": false,
                  "readOnlyHint": true,
                  "title": "Calculate Buildable Envelope"
                },
                "description": "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 \u00d7 width \u00d7 height), usable footprint, and coverage math. Takes lot area, setbacks, FAR, height limit, and coverage as inputs \u2014 a pure calculation tool, does not query data.",
                "inputSchema": {
                  "properties": {
                    "front_setback_ft": {
                      "description": "Front setback in feet (distance from front property line)",
                      "type": "number"
                    },
                    "lot_area_sqft": {
                      "description": "Total lot area in square feet",
                      "type": "number"
                    },
                    "max_far": {
                      "description": "Maximum floor area ratio (e.g., 0.5, 2.0). FAR = building area / lot area.",
                      "type": "number"
                    },
                    "max_height_ft": {
                      "description": "Maximum building height in feet",
                      "type": "number"
                    },
                    "max_lot_coverage": {
                      "description": "Maximum lot coverage as decimal (e.g., 0.45 for 45%)",
                      "type": "number"
                    },
                    "rear_setback_ft": {
                      "description": "Rear setback in feet",
                      "type": "number"
                    },
                    "side_setback_ft": {
                      "description": "Side setback in feet (each side)",
                      "type": "number"
                    }
                  },
                  "required": [
                    "lot_area_sqft"
                  ],
                  "type": "object"
                },
                "name": "calculate_buildable_envelope"
              },
              {
                "annotations": {
                  "destructiveHint": false,
                  "idempotentHint": false,
                  "openWorldHint": true,
                  "readOnlyHint": false,
                  "title": "Submit Correction"
                },
                "description": "Report an error on a ReadyPermit page so Buildability\u2122 can verify and update. USE WHEN: a user mentions that information on ReadyPermit 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 \u2014 this is the civic-infrastructure feedback loop Buildability\u2122 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\u2122. RETURNS: a correction ID for tracking + status.",
                "inputSchema": {
                  "properties": {
                    "issue": {
                      "description": "What is incorrect or outdated. Be specific \u2014 mention the exact fact, rule, or data point.",
                      "type": "string"
                    },
                    "pageUrl": {
                      "description": "Full ReadyPermit URL where the error appears (e.g., 'https://readypermit.ai/adu/los-angeles').",
                      "type": "string"
                    },
                    "reporterContext": {
                      "description": "Optional: how the error was discovered (e.g., 'user self-reported during property research conversation', 'comparing to Austin Code \u00a725-2-1604').",
                      "type": "string"
                    },
                    "sourceDocument": {
                      "description": "Optional: citation or URL supporting the correction (city ordinance, state law, news article, planning department page).",
                      "type": "string"
                    },
                    "suggestion": {
                      "description": "Optional: what the correct information is, if known.",
                      "type": "string"
                    }
                  },
                  "required": [
                    "pageUrl",
                    "issue"
                  ],
                  "type": "object"
                },
                "name": "submit_correction"
              }
            ]
          }
        },
        "bad_protocol_status_code": 200,
        "delete_error": null,
        "delete_status_code": 200,
        "expired_session_error": null,
        "expired_session_status_code": 200,
        "issues": [
          "missing_protocol_header",
          "bad_protocol_not_rejected",
          "expired_session_not_404"
        ],
        "last_event_id_visible": false,
        "protocol_header_present": false,
        "requested_protocol_version": "2024-11-05",
        "session_id_present": true,
        "transport": "streamable-http"
      },
      "latency_ms": 270.91,
      "status": "error"
    },
    "utility_coverage_probe": {
      "details": {
        "completions": {
          "advertised": false,
          "live_probe": "not_executed",
          "sample_target": {
            "argument_name": "address",
            "name": "investor_analysis",
            "type": "prompt"
          }
        },
        "initialize_capability_keys": [
          "prompts",
          "resources",
          "tools"
        ],
        "pagination": {
          "metadata_signal": false,
          "next_cursor_methods": [],
          "supported": false
        },
        "tasks": {
          "advertised": false,
          "http_status": 404,
          "probe_status": "missing"
        }
      },
      "latency_ms": 188.49,
      "status": "missing"
    }
  },
  "failures": {
    "oauth_authorization_server": {
      "reason": "no_authorization_server"
    },
    "oauth_protected_resource": {
      "error": "Client error '404 Not Found' for url 'https://rnfonkwthefktfvfwypr.supabase.co/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://rnfonkwthefktfvfwypr.supabase.co/.well-known/oauth-protected-resource"
    },
    "openid_configuration": {
      "reason": "no_authorization_server"
    },
    "server_card": {
      "error": "Client error '404 Not Found' for url 'https://rnfonkwthefktfvfwypr.supabase.co/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://rnfonkwthefktfvfwypr.supabase.co/.well-known/mcp/server-card.json"
    },
    "transport_compliance_probe": {
      "bad_protocol_error": null,
      "bad_protocol_headers": {
        "content-type": "application/json",
        "mcp-session-id": "1267abe1-2908-44f0-ac1f-baf89e0e965d",
        "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
      },
      "bad_protocol_payload": {
        "id": 410,
        "jsonrpc": "2.0",
        "result": {
          "tools": [
            {
              "annotations": {
                "destructiveHint": false,
                "idempotentHint": true,
                "openWorldHint": true,
                "readOnlyHint": true,
                "title": "Analyze Property (Full Buildability Report)"
              },
              "description": "Get complete property intelligence for any U.S. address \u2014 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\u2122 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 $2,000-$4,500 zoning consultant work.",
              "inputSchema": {
                "properties": {
                  "address": {
                    "description": "Full U.S. property address (e.g., '123 Main St, Denver, CO 80202'). Accepts any format \u2014 will be geocoded.",
                    "type": "string"
                  },
                  "persona": {
                    "description": "User persona for tailored analysis (optional). Changes tone and emphasis: investor=deal metrics, developer=feasibility, homeowner=plain English, lender=collateral risk, broker=disclosure items.",
                    "enum": [
                      "investor",
                      "developer",
                      "homeowner",
                      "lender",
                      "broker"
                    ],
                    "type": "string"
                  }
                },
                "required": [
                  "address"
                ],
                "type": "object"
              },
              "name": "analyze_property"
            },
            {
              "annotations": {
                "destructiveHint": false,
                "idempotentHint": true,
                "openWorldHint": true,
                "readOnlyHint": true,
                "title": "Get Buildability Score (Quick Screen)"
              },
              "description": "Get a quick Buildability\u2122 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 \u2014 use for deal screening and portfolio filtering.",
              "inputSchema": {
                "properties": {
                  "address": {
                    "description": "Full U.S. property address",
                    "type": "string"
                  }
                },
                "required": [
                  "address"
                ],
                "type": "object"
              },
              "name": "get_buildability_score"
            },
            {
              "annotations": {
                "destructiveHint": false,
                "idempotentHint": true,
                "openWorldHint": true,
                "readOnlyHint": true,
                "title": "Lookup Zoning (Permitted Uses)"
              },
              "description": "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.",
              "inputSchema": {
                "properties": {
                  "address": {
                    "description": "Full U.S. property address",
                    "type": "string"
                  }
                },
                "required": [
                  "address"
                ],
                "type": "object"
              },
              "name": "lookup_zoning"
            },
            {
              "annotations": {
                "destructiveHint": false,
                "idempotentHint": true,
                "openWorldHint": true,
                "readOnlyHint": true,
                "title": "Check FEMA Flood Zone"
              },
              "description": "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.",
              "inputSchema": {
                "properties": {
                  "address": {
                    "description": "Full U.S. property address",
                    "type": "string"
                  }
                },
                "required": [
                  "address"
                ],
                "type": "object"
              },
              "name": "check_flood_zone"
            },
            {
              "annotations": {
                "destructiveHint": false,
                "idempotentHint": true,
                "openWorldHint": true,
                "readOnlyHint": true,
                "title": "Check Environmental Risks"
              },
              "description": "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.",
              "inputSchema": {
                "properties": {
                  "address": {
                    "description": "Full U.S. property address (preferred \u2014 gives best results)",
                    "type": "string"
                  },
                  "latitude": {
                    "description": "Property latitude (use if no address available)",
                    "type": "number"
                  },
                  "longitude": {
                    "description": "Property longitude (use if no address available)",
                    "type": "number"
                  }
                },
                "required": [],
                "type": "object"
              },
              "name": "check_environmental_risks"
            },
            {
              "annotations": {
                "destructiveHint": false,
                "idempotentHint": false,
                "openWorldHint": true,
                "readOnlyHint": true,
                "title": "Search Comparable Sales"
              },
              "description": "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.",
              "inputSchema": {
                "properties": {
                  "address": {
                    "description": "Full U.S. property address (preferred \u2014 gives best results)",
                    "type": "string"
                  },
                  "latitude": {
                    "description": "Center latitude for search (use if no address available)",
                    "type": "number"
                  },
                  "longitude": {
                    "description": "Center longitude for search (use if no address available)",
                    "type": "number"
                  },
                  "radius_miles": {
                    "description": "Search radius in miles (default: 0.5, max: 5)",
                    "type": "number"
                  }
                },
                "required": [],
                "type": "object"
              },
              "name": "search_comparable_sales"
            },
            {
              "annotations": {
                "destructiveHint": false,
                "idempotentHint": true,
                "openWorldHint": false,
                "readOnlyHint": true,
                "title": "Calculate Buildable Envelope"
              },
              "description": "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 \u00d7 width \u00d7 height), usable footprint, and coverage math. Takes lot area, setbacks, FAR, height limit, and coverage as inputs \u2014 a pure calculation tool, does not query data.",
              "inputSchema": {
                "properties": {
                  "front_setback_ft": {
                    "description": "Front setback in feet (distance from front property line)",
                    "type": "number"
                  },
                  "lot_area_sqft": {
                    "description": "Total lot area in square feet",
                    "type": "number"
                  },
                  "max_far": {
                    "description": "Maximum floor area ratio (e.g., 0.5, 2.0). FAR = building area / lot area.",
                    "type": "number"
                  },
                  "max_height_ft": {
                    "description": "Maximum building height in feet",
                    "type": "number"
                  },
                  "max_lot_coverage": {
                    "description": "Maximum lot coverage as decimal (e.g., 0.45 for 45%)",
                    "type": "number"
                  },
                  "rear_setback_ft": {
                    "description": "Rear setback in feet",
                    "type": "number"
                  },
                  "side_setback_ft": {
                    "description": "Side setback in feet (each side)",
                    "type": "number"
                  }
                },
                "required": [
                  "lot_area_sqft"
                ],
                "type": "object"
              },
              "name": "calculate_buildable_envelope"
            },
            {
              "annotations": {
                "destructiveHint": false,
                "idempotentHint": false,
                "openWorldHint": true,
                "readOnlyHint": false,
                "title": "Submit Correction"
              },
              "description": "Report an error on a ReadyPermit page so Buildability\u2122 can verify and update. USE WHEN: a user mentions that information on ReadyPermit 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 \u2014 this is the civic-infrastructure feedback loop Buildability\u2122 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\u2122. RETURNS: a correction ID for tracking + status.",
              "inputSchema": {
                "properties": {
                  "issue": {
                    "description": "What is incorrect or outdated. Be specific \u2014 mention the exact fact, rule, or data point.",
                    "type": "string"
                  },
                  "pageUrl": {
                    "description": "Full ReadyPermit URL where the error appears (e.g., 'https://readypermit.ai/adu/los-angeles').",
                    "type": "string"
                  },
                  "reporterContext": {
                    "description": "Optional: how the error was discovered (e.g., 'user self-reported during property research conversation', 'comparing to Austin Code \u00a725-2-1604').",
                    "type": "string"
                  },
                  "sourceDocument": {
                    "description": "Optional: citation or URL supporting the correction (city ordinance, state law, news article, planning department page).",
                    "type": "string"
                  },
                  "suggestion": {
                    "description": "Optional: what the correct information is, if known.",
                    "type": "string"
                  }
                },
                "required": [
                  "pageUrl",
                  "issue"
                ],
                "type": "object"
              },
              "name": "submit_correction"
            }
          ]
        }
      },
      "bad_protocol_status_code": 200,
      "delete_error": null,
      "delete_status_code": 200,
      "expired_session_error": null,
      "expired_session_status_code": 200,
      "issues": [
        "missing_protocol_header",
        "bad_protocol_not_rejected",
        "expired_session_not_404"
      ],
      "last_event_id_visible": false,
      "protocol_header_present": false,
      "requested_protocol_version": "2024-11-05",
      "session_id_present": true,
      "transport": "streamable-http"
    }
  },
  "remote_url": "https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server",
  "server_card_payload": null,
  "server_identifier": "ai.readypermit/geo"
}

Known versions

Validation history

7 day score delta
n/a
30 day score delta
n/a
Recent healthy ratio
100%
Freshness
3.5h
TimestampStatusScoreLatencyTools
May 13, 2026 02:35:10 PM UTC Healthy 74.7 3379.0 ms 8
May 13, 2026 02:34:03 AM UTC Healthy 75.2 3129.5 ms 8
May 12, 2026 02:27:35 PM UTC Healthy 74.7 3700.2 ms 8
May 12, 2026 02:21:02 AM UTC Healthy 71.6 3267.2 ms 8

Validation timeline

ValidatedSummaryScoreProtocolAuth modeToolsHigh-risk toolsChanges
May 13, 2026 02:35:10 PM UTC Healthy 74.7 2024-11-05 public 8 2 none
May 13, 2026 02:34:03 AM UTC Healthy 75.2 2024-11-05 public 8 2 none
May 12, 2026 02:27:35 PM UTC Healthy 74.7 2024-11-05 public 8 2 none
May 12, 2026 02:21:02 AM UTC Healthy 71.6 2024-11-05 public 8 2 none

Recent validation runs

StartedStatusSummaryLatencyChecks
May 13, 2026 02:35:07 PM UTC Completed Healthy 3379.0 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 13, 2026 02:34:00 AM UTC Completed Healthy 3129.5 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 12, 2026 02:27:32 PM UTC Completed Healthy 3700.2 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 12, 2026 02:20:59 AM UTC Completed Healthy 3267.2 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe