An assistant that can change your IDX Broker account needs guardrails. This guide explains how the IDX Broker MCP handles confirmations, what data it returns, and what is stored. It describes how the product is documented. The IDX Broker MCP is early software, so verify important changes in IDX Broker and report anything odd to support@virtualresults.net. We make no guarantees of uptime or data accuracy.
The three-call confirmation
- Reads are immediate. Looking things up changes nothing.
- Creating a new record is one step, then read back. The assistant checks that the record exists.
- Changing or deleting something existing takes three calls. 32 tools work this way. The first call changes nothing and returns an "Are you sure?" with a token. The second asks "Are you really sure?" with a new token. The third call runs the change. The questions are meant to be put to you word for word, and a mismatch in the target or the change makes the chain fail closed. In practice the assistant asks you to confirm twice.
Some creations also use the three-call flow because they change your public site immediately or publish publicly: custom CSS, sub-headers, wrapper cache clearing, and both Social Pro publish tools.
The 32 tools cover: updating or deleting leads, saved searches, notes, saved properties, market reports, saved links, widgets, legacy widgets and supplemental listings; bulk lead updates; updating account info; custom CSS and sub-headers; clearing the wrapper cache; and the Social Pro publish tools.
Deletes have no undo
Deleting in IDX Broker cannot be undone. Updates merge onto the current values, so fields you do not mention are kept.
What the result words mean
created, updated and deleted are verified by reading the record back. _unverified results probably worked but could not be confirmed. update_not_applied means IDX Broker accepted the request and changed nothing. Social Pro posts are always published_unverified. See troubleshooting.
Social Pro: handle with care
Social Pro publishing is the least proven part. It has not been verified against a live Social Pro account. Treat it as experimental and check your social accounts afterward.
What data comes back
From your own account only: leads and their contact information, activity, notes, saved searches, saved links with match counts, widgets with settings and embed addresses, featured, sold-pending, off-market and your own listings, message metadata, account profile, custom CSS and sub-headers, and MLS counts and totals.
Counts and totals come from your MLS data: active listing counts by city, county or zip, and total asking price by property type. There are no medians or sold statistics.
On accounts under Virtual Results' IDX partnership, MLS-wide search returns matching listings and full listing records. It is limited to the MLSs the caller is approved for, sold data needs approval, and opted-out addresses stay hidden. These are documented design limits, so verify results against your MLS.
Missing data is reported as no data, never as zero.
What it does not expose
- Lead passwords. The assistant can neither set nor see them.
- Tools for Virtual Results' partner administration. Each connection is designed to act only on your own organization's account.
- Editing of agents or multi-user settings.
What is stored
Your IDX Broker key is stored encrypted, for your organization only. It is not echoed back or logged. Key management is limited to organization admins and re-checked on every request. What your AI app keeps about your chat is governed by that app's own settings and policies.
Side effects to know about
- Creating a lead makes IDX Broker send that lead its own verify-your-email message. Email updates default to on.
- Hourly limits apply per key.
Good practice
- Start with read-only prompts.
- Read each confirmation before you agree.
- Do not paste your key in chat if you would rather use the private link.
- Check important changes in IDX Broker.
Related: documentation overview, disconnect guide. Sign up.