IDX Broker MCP by usefulapi
REMOTE · IDX-BROKER.USEFULAPI.IO
Read IDX Broker leads, agents, listings and MLS data; create and update leads and notes.
Available components
Last scanned (7 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 25 Oct 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 4212 tokens (~156/item across 27 items; 27 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 27 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 28 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.3.0 → 1.4.0 functional
- Server version: 1.2.0 → 1.3.0 functional
- Server version: 1.0.0 → 1.2.0 functional
- 23 Oct 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Probed https://idx-broker.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of idx-broker.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://idx-broker.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://idx-broker.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://idx-broker.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://idx-broker.usefulapi.io/mcp |
| Authorisation server | https://idx-broker.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://idx-broker.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/idx-broker/ |
| http (plaintext) | http://idx-broker.usefulapi.io/mcp | Inconclusive | 302 | http://idx-broker.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
idx_add_lead_note Add lead note ~63
WRITE: adds a note to a lead (visible to the account's agents). Returns the new note id. PUT /leads/note/{leadID}.
| Name | Type | Req | Description |
|---|---|---|---|
| lead_id | integer | yes | IDX lead id. |
| note | string | yes | Note text. |
No output schema declared.
No examples provided.
idx_create_lead Create lead ~161
WRITE: 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_lead. Returns the new lead id. PUT /leads/lead.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Lead email address. | |
| fields | object | – | Other updatable lead fields by IDX name, e.g. {"phone": "555-0100"}. firstName, lastName and email cannot be repeated here. |
| first_name | string | yes | Lead first name. |
| last_name | string | yes | Lead last name. |
No output schema declared.
No examples provided.
idx_get_account_info Get account info ~59
The 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
idx_get_account_type Get account type ~48
The 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
idx_get_lead Get lead ~92
One lead by id with its details, last 5 viewed listings and searches, and the total number of listings viewed. GET /leads/lead/{leadID}.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
| lead_id | integer | yes | IDX lead id (from idx_list_leads). |
No output schema declared.
No examples provided.
idx_get_lead_traffic Get lead traffic ~224
Website 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}.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
| interval | number | – | Hours of data to return, counted back from start_datetime (default: now). 0.0166 (one minute) to 168; decimals allowed. IDX default when omitted: 1 hour; pass up to 168 for one week. |
| lead_id | integer | yes | IDX lead id. |
| limit | integer | – | Number of items to return (use with offset). |
| offset | integer | – | Items to skip from the beginning (default 0). |
| start_datetime | string | – | Where the interval starts counting back (the newest moment wanted). Default: now. ISO 8601 with a timezone. |
No output schema declared.
No examples provided.
idx_get_mls_age Get MLS data age ~94
When an MLS feed was last downloaded and processed and when its images were last gathered (UTC). GET /mls/age/{idxID}.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
| idx_id | string | yes | IDX MLS id such as a001 (see idx_list_approved_mls). |
No output schema declared.
No examples provided.
idx_get_saved_link_count Count properties of a saved link ~53
The total number of properties a saved link currently matches. GET /clients/savedlinks/{savedLinkID}/count.
| Name | Type | Req | Description |
|---|---|---|---|
| saved_link_id | integer | yes | Saved link id (from idx_list_saved_links). |
No output schema declared.
No examples provided.
idx_get_widget Get widget ~70
One JavaScript widget with its settings. GET /clients/widgets/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
| widget_id | integer | yes | Widget id (from idx_list_widgets). |
No output schema declared.
No examples provided.
idx_list_agents List agents ~196
Agents 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.
| Name | Type | Req | Description |
|---|---|---|---|
| date_type | string | – | Which date the time window applies to. |
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
| filter_field | string | – | Field to filter on; needs filter_value. |
| filter_value | string | – | Value to match in filter_field. |
| interval | number | – | Hours of data to return, counted back from start_datetime (default: now). 0.0166 (one minute) to 8765; decimals allowed. |
| start_datetime | string | – | Where the interval starts counting back (the newest moment wanted). Default: now. ISO 8601 with a timezone. |
No output schema declared.
No examples provided.
idx_list_approved_mls List approved MLSs ~84
The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
No output schema declared.
No examples provided.
idx_list_featured_listings List featured listings ~222
The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| date_type | string | – | Which date the time window applies to (default dateAdded). |
| disclaimers | boolean | – | Include the MLS disclaimer and courtesy text in the reply. |
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
| interval | number | – | Hours of data to return, counted back from start_datetime (default: now). 0.0166 (one minute) to 8765; decimals allowed. |
| limit | integer | – | Number of items to return (use with offset). |
| offset | integer | – | Items to skip from the beginning (default 0). |
| start_datetime | string | – | Where the interval starts counting back (the newest moment wanted). Default: now. ISO 8601 with a timezone. |
No output schema declared.
No examples provided.
idx_list_lead_notes List lead notes ~203
Notes on a lead, or one note when note_id is given. GET /leads/note/{leadID}[/{noteID}].
| Name | Type | Req | Description |
|---|---|---|---|
| date_type | string | – | Which date the time window applies to. |
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
| interval | number | – | Hours of data to return, counted back from start_datetime (default: now). 0.0166 (one minute) to 168; decimals allowed. IDX default when omitted: 1 hour; pass up to 168 for one week. |
| lead_id | integer | yes | IDX lead id. |
| note_id | integer | – | One note id; omit for all notes of the lead. |
| start_datetime | string | – | Where the interval starts counting back (the newest moment wanted). Default: now. ISO 8601 with a timezone. |
No output schema declared.
No examples provided.
idx_list_lead_saved_properties List lead saved properties ~204
Properties a lead saved (or one when property_id is given). GET /leads/property/{leadID}[/{propertyID}].
| Name | Type | Req | Description |
|---|---|---|---|
| date_type | string | – | Which date the time window applies to. |
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
| interval | number | – | Hours of data to return, counted back from start_datetime (default: now). 0.0166 (one minute) to 168; decimals allowed. IDX default when omitted: 1 hour; pass up to 168 for one week. |
| lead_id | integer | yes | IDX lead id. |
| property_id | integer | – | One saved property id; omit for all saved properties of the lead. |
| start_datetime | string | – | Where the interval starts counting back (the newest moment wanted). Default: now. ISO 8601 with a timezone. |
No output schema declared.
No examples provided.
idx_list_lead_searches List lead saved searches ~213
Saved property searches of a lead (or one search when search_id is given), with the results URL of each. GET /leads/search/{leadID}[/{searchID}].
| Name | Type | Req | Description |
|---|---|---|---|
| date_type | string | – | Which date the time window applies to. |
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
| interval | number | – | Hours of data to return, counted back from start_datetime (default: now). 0.0166 (one minute) to 168; decimals allowed. IDX default when omitted: 1 hour; pass up to 168 for one week. |
| lead_id | integer | yes | IDX lead id. |
| search_id | integer | – | One saved search id; omit for all searches of the lead. |
| start_datetime | string | – | Where the interval starts counting back (the newest moment wanted). Default: now. ISO 8601 with a timezone. |
No output schema declared.
No examples provided.
idx_list_leads List leads ~261
List 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. Uses one of the key's hourly API accesses. GET /leads/lead.
| Name | Type | Req | Description |
|---|---|---|---|
| date_type | string | – | Which date the time window applies to (default subscribeDate). |
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
| interval | number | – | Hours of data to return, counted back from start_datetime (default: now). 0.0166 (one minute) to 168; decimals allowed. IDX default when omitted: 1 hour; pass up to 168 for one week. |
| offset | integer | – | Items to skip from the beginning (default 0). |
| sort_by | string | – | Sort by creation order, asc or desc. |
| start_datetime | string | – | Where the interval starts counting back (the newest moment wanted). Default: now. ISO 8601 with a timezone. |
No output schema declared.
No examples provided.
idx_list_mls_locations List MLS cities, counties or postal codes ~198
Cities, 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}.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
| filter_field | string | – | Field to filter on (must fit kind); needs filter_value. |
| filter_value | string | – | Value to match in filter_field. |
| idx_id | string | yes | IDX MLS id such as a001 (see idx_list_approved_mls). |
| kind | string | yes | Which list. |
No output schema declared.
No examples provided.
idx_list_mls_property_types List MLS property types ~128
Property types of an MLS with the IDX type id, the MLS name, the parent type and subtypes. GET /mls/propertytypes/{idxID}.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
| filter_field | string | – | Field to filter on; needs filter_value. |
| filter_value | string | – | Value to match in filter_field. |
| idx_id | string | yes | IDX MLS id such as a001 (see idx_list_approved_mls). |
No output schema declared.
No examples provided.
idx_list_mls_search_fields List MLS search fields ~132
The 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}.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
| filter_field | string | – | Field to filter on; needs filter_value. |
| filter_value | string | – | Value to match in filter_field. |
| idx_id | string | yes | IDX MLS id such as a001 (see idx_list_approved_mls). |
No output schema declared.
No examples provided.
idx_list_off_market_listings List off-market listings ~196
The account's off-market listings. GET /clients/offmarket.
| Name | Type | Req | Description |
|---|---|---|---|
| date_type | string | – | Which date the time window applies to (default dateAdded). |
| disclaimers | boolean | – | Include the MLS disclaimer and courtesy text in the reply. |
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
| interval | number | – | Hours of data to return, counted back from start_datetime (default: now). 0.0166 (one minute) to 8765; decimals allowed. |
| limit | integer | – | Number of items to return (use with offset). |
| offset | integer | – | Items to skip from the beginning (default 0). |
| start_datetime | string | – | Where the interval starts counting back (the newest moment wanted). Default: now. ISO 8601 with a timezone. |
No output schema declared.
No examples provided.
idx_list_offices List offices ~181
Offices on a multi-user IDX Broker account. Filter by one field or by a time window. GET /clients/offices.
| Name | Type | Req | Description |
|---|---|---|---|
| date_type | string | – | Which date the time window applies to. |
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
| filter_field | string | – | Field to filter on; needs filter_value. |
| filter_value | string | – | Value to match in filter_field. |
| interval | number | – | Hours of data to return, counted back from start_datetime (default: now). 0.0166 (one minute) to 8765; decimals allowed. |
| start_datetime | string | – | Where the interval starts counting back (the newest moment wanted). Default: now. ISO 8601 with a timezone. |
No output schema declared.
No examples provided.
idx_list_saved_links List saved links ~170
Saved links (pre-built property search pages) of the account with id, name and URL. GET /clients/savedlinks.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
| interval | number | – | Hours of data to return, counted back from start_datetime (default: now). 0.0166 (one minute) to 8765; decimals allowed. |
| limit | integer | – | Number of items to return (use with offset). |
| offset | integer | – | Items to skip from the beginning (default 0). |
| start_datetime | string | – | Where the interval starts counting back (the newest moment wanted). Default: now. ISO 8601 with a timezone. |
No output schema declared.
No examples provided.
idx_list_sold_pending_listings List sold and pending listings ~208
The account's sold and pending listings, that is those removed from the MLS feed. GET /clients/soldpending.
| Name | Type | Req | Description |
|---|---|---|---|
| date_type | string | – | Which date the time window applies to (default dateAdded). |
| disclaimers | boolean | – | Include the MLS disclaimer and courtesy text in the reply. |
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
| interval | number | – | Hours of data to return, counted back from start_datetime (default: now). 0.0166 (one minute) to 8765; decimals allowed. |
| limit | integer | – | Number of items to return (use with offset). |
| offset | integer | – | Items to skip from the beginning (default 0). |
| start_datetime | string | – | Where the interval starts counting back (the newest moment wanted). Default: now. ISO 8601 with a timezone. |
No output schema declared.
No examples provided.
idx_list_supplemental_listings List supplemental listings ~210
The account's supplemental (non-MLS) listings with a basic set of fields. GET /clients/supplemental.
| Name | Type | Req | Description |
|---|---|---|---|
| date_type | string | – | Which date the time window applies to (default dateAdded). |
| disclaimers | boolean | – | Include the MLS disclaimer and courtesy text in the reply. |
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
| interval | number | – | Hours of data to return, counted back from start_datetime (default: now). 0.0166 (one minute) to 8765; decimals allowed. |
| limit | integer | – | Number of items to return (use with offset). |
| offset | integer | – | Items to skip from the beginning (default 0). |
| start_datetime | string | – | Where the interval starts counting back (the newest moment wanted). Default: now. ISO 8601 with a timezone. |
No output schema declared.
No examples provided.
idx_list_system_links List system links ~76
The system pages of the account's site (search, featured, contact...) with name, id and URL, which can be linked to directly. GET /clients/systemlinks.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
No output schema declared.
No examples provided.
idx_list_widgets List widgets ~94
The JavaScript widgets on the account with id, name, URL and options. GET /clients/widgets.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Only return these fields (IDX `rf`); ["*"] returns every available field. Narrow it to save API size. |
| limit | integer | – | Number of items to return (use with offset). |
| offset | integer | – | Items to skip from the beginning (default 0). |
No output schema declared.
No examples provided.
idx_update_lead Update lead ~115
WRITE: 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}.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | yes | Fields to set, by IDX name, e.g. {"phone": "555-0100"}. |
| lead_id | integer | yes | IDX lead id. |
No output schema declared.
No examples provided.
How do I install the IDX Broker MCP by usefulapi server?
IDX Broker MCP by usefulapi is a hosted endpoint at https://idx-broker.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · idx-broker.usefulapi.io
claude mcp add --transport http io-usefulapi-idx-broker 'https://idx-broker.usefulapi.io/mcp'
What is the IDX Broker MCP by usefulapi server?
IDX Broker MCP by usefulapi is listed in the public MCP registry as io.usefulapi/idx-broker. Read IDX Broker leads, agents, listings and MLS data; create and update leads and notes. This page covers its hosted endpoint (https://idx-broker.usefulapi.io/mcp).
Is the IDX Broker MCP by usefulapi server safe to use?
IDX Broker MCP by usefulapi scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the IDX Broker MCP by usefulapi server expose?
IDX Broker MCP by usefulapi exposes 27 tools: idx_get_account_info, idx_get_account_type, idx_list_agents, idx_list_offices, idx_list_leads, and 22 more. Their descriptions and schemas cost roughly 3,955 tokens of context every time the server is loaded.
Does the IDX Broker MCP by usefulapi server require authentication?
Yes. IDX Broker MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the IDX Broker MCP by usefulapi server still maintained?
IDX Broker MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.