Home / MCP registry index / com.usprimerealty/florida-home-search

Florida Home Search by U.S. Prime Realty

com.usprimerealty/florida-home-search in the official MCP registry. Endpoint https://api.usprimerealty.com/mcp.

The registry describes it as: Search Florida properties and new construction for sale with U.S. Prime Realty.

We read its 13 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

get_guides_list download_guides search_properties listing_details mortgage_calculator affordability_calculator send_contact_info save_listings notify_agent get_appointment_slots book_appointment reschedule_appointment cancel_appointment

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-usprimerealty-florida-home-search/badge.svg)](https://lazaretto.dev/mcp-registry/com-usprimerealty-florida-home-search)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.