Home / MCP registry index / io.usefulapi/idx-broker

IDX Broker MCP by usefulapi

io.usefulapi/idx-broker in the official MCP registry. Endpoint https://idx-broker.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Read IDX Broker leads, agents, listings and MLS data; create and update leads and notes.

We read its 27 tools on 2026-10-31. 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.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http idx-broker https://idx-broker.usefulapi.io/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "idx-broker": {
      "url": "https://idx-broker.usefulapi.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"idx-broker","type":"http","url":"https://idx-broker.usefulapi.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

idx_get_account_info idx_get_account_type idx_list_agents idx_list_offices idx_list_leads idx_get_lead idx_list_lead_notes idx_list_lead_searches idx_list_lead_saved_properties idx_get_lead_traffic idx_list_featured_listings idx_list_sold_pending_listings idx_list_off_market_listings idx_list_supplemental_listings idx_list_saved_links idx_get_saved_link_count idx_list_widgets idx_get_widget idx_list_system_links idx_list_approved_mls idx_get_mls_age idx_list_mls_property_types idx_list_mls_search_fields idx_list_mls_locations idx_create_lead idx_add_lead_note idx_update_lead

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): c06ce2408d1bf02a. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-idx-broker/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-idx-broker)

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.