IDX Broker MCP by usefulapi

io.usefulapi/idx-broker · v1.0.0 · sales-and-crm

IDX Broker MCP by usefulapi is healthy: it completed an MCP handshake in 1017 ms and exposes 27 tools.

Read IDX Broker leads, agents, listings and MLS data; create and update leads and notes.

Endpoint: https://idx-broker.usefulapi.io/mcp (streamable-http)

Repository · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count27
Latency1017 ms
Last checked (UTC)2026-10-23T11:05:21.435Z

Health history

Checked (UTC)StatusLatencyError
2026-10-23T11:05:21.435ZHealthy1017

Tools (27)

idx_get_account_infoThe IDX Broker client account this access key belongs to: company and contact details and account settings (access keys and passwords are never returned). The reply also shows how many of the key's hourly API accesses are used. GET /clients/accountinfo.
idx_get_account_typeThe IDX Broker plan of the account (Lite or Platinum). It sets the hourly API limit: 300 accesses per key on Lite, 500 on Platinum. GET /clients/accounttype.
idx_list_agentsAgents on a multi-user IDX Broker account (id, name, office, contact details, category, language, login dates). Filter by one field or by a time window. GET /clients/agents.
idx_list_officesOffices on a multi-user IDX Broker account. Filter by one field or by a time window. GET /clients/offices.
idx_list_leadsList the account's leads (website registrants) with contact details, status, agent owner, and last viewed listings and searches. A reply holds up to 500 leads; pass offset to page on and look for pagination information in the reply. Filter by a time window on signup, edit, login or activity date. Us
idx_get_leadOne lead by id with its details, last 5 viewed listings and searches, and the total number of listings viewed. GET /leads/lead/{leadID}.
idx_list_lead_notesNotes on a lead, or one note when note_id is given. GET /leads/note/{leadID}[/{noteID}].
idx_list_lead_searchesSaved property searches of a lead (or one search when search_id is given), with the results URL of each. GET /leads/search/{leadID}[/{searchID}].
idx_list_lead_saved_propertiesProperties a lead saved (or one when property_id is given). GET /leads/property/{leadID}[/{propertyID}].
idx_get_lead_trafficWebsite traffic history of one lead: date, page, referrer and IP of each visit (at most 5,000 rows per request; use interval/offset/limit to narrow it). GET /leads/leadtraffic/{leadID}.
idx_list_featured_listingsThe account's featured (active) listings with address, price, status, photos and agent. Only the account's own listings are returned, never general MLS data. GET /clients/featured.
idx_list_sold_pending_listingsThe account's sold and pending listings, that is those removed from the MLS feed. GET /clients/soldpending.
idx_list_off_market_listingsThe account's off-market listings. GET /clients/offmarket.
idx_list_supplemental_listingsThe account's supplemental (non-MLS) listings with a basic set of fields. GET /clients/supplemental.
idx_list_saved_linksSaved links (pre-built property search pages) of the account with id, name and URL. GET /clients/savedlinks.
idx_get_saved_link_countThe total number of properties a saved link currently matches. GET /clients/savedlinks/{savedLinkID}/count.
idx_list_widgetsThe JavaScript widgets on the account with id, name, URL and options. GET /clients/widgets.
idx_get_widgetOne JavaScript widget with its settings. GET /clients/widgets/{id}.
idx_list_system_linksThe system pages of the account's site (search, featured, contact...) with name, id and URL, which can be linked to directly. GET /clients/systemlinks.
idx_list_approved_mlsThe MLSs approved for display on the account, with their IDX ids (such as a001) and names. Use the id in the other MLS tools. GET /mls/approvedmls.
idx_get_mls_ageWhen an MLS feed was last downloaded and processed and when its images were last gathered (UTC). GET /mls/age/{idxID}.
idx_list_mls_property_typesProperty types of an MLS with the IDX type id, the MLS name, the parent type and subtypes. GET /mls/propertytypes/{idxID}.
idx_list_mls_search_fieldsThe fields of an MLS that can be searched under MLS rules: field name, display name and the property types they belong to. GET /mls/searchfields/{idxID}.
idx_list_mls_locationsCities, counties or postal codes present in an MLS's data, with ids and a count of occurrences. Filter fields: cities = cityID, cityName, stateAbrv, mlsPtID; counties = countyID, countyName, stateAbrv, mlsPtID; postalcodes = id, stateAbrv, mlsPtID. GET /mls/{cities|counties|postalcodes}/{idxID}.
idx_create_leadWRITE: creates a new lead in the IDX Broker account (and may trigger the account's own lead notifications). Needs a correctly formatted email with a valid MX record; IDX rejects bad addresses with a server error. Extra fields go in `fields` by their IDX name, as seen on a lead returned by idx_get_le
idx_add_lead_noteWRITE: adds a note to a lead (visible to the account's agents). Returns the new note id. PUT /leads/note/{leadID}.
idx_update_leadWRITE: changes fields of an existing lead; the given values replace the stored ones. Only pass what must change. Field names are the IDX lead field names as seen on a lead returned by idx_get_lead (for example firstName, lastName, email, phone, status). POST /leads/lead/{leadID}.