Urflrealtor Mcp

io.github.Th3Slack3rPublished by GitHub account Th3Slack3rv1.0.0Updated Oct 24, 2026

Florida Real Estate API — agent verification, property data, market trends, comps, lead tools.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

A local MCP server for Florida real estate data, letting an assistant verify agents and look up properties, market trends, comps and leads.

What you can do
Verify real estate agents in Florida and check their credentials or status through the API's agent verification tools, where available in the API's tool set, which is not enumerated here. Retrieve Florida property data and comparable sales (comps) for a given listing or area. Review market trends to support pricing or investment questions. Work with lead-related tools for capturing or managing prospective clients. The manifest lists no tools, so the exact operations and their inputs are not documented in the supplied material.
When to use it
Useful when an assistant needs Florida-specific real estate information, such as checking an agent, pulling property details or comps, or reviewing local market trends, and you are comfortable running a local server for that API.
Requirements
Runs as a local process on the user's machine over stdio; desktop only, with no web executable. No packages, environment variables, headers or authentication are declared, so any API access details would need to be supplied separately.
Before you install
The server is described as wrapping a real estate API, but no credentials, endpoints or tool list are declared, so you cannot confirm what data it sends or where. Lead tools may create or change records. Verify the provider and API before installing.

Installation

In SourceWeft

  1. Open Urflrealtor Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.