IDX Broker MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 营销与社交媒体

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://idx-broker.usefulapi.io/mcp

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

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

{
  "servers": {
    "idx-broker": {
      "type": "http",
      "url": "https://idx-broker.usefulapi.io/mcp"
    }
  }
}

https://idx-broker.usefulapi.io/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月9日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• idx_get_account_info

  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.

• idx_get_account_type

  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.

• idx_list_agents

  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.

• idx_list_offices

  Offices on a multi-user IDX Broker account. Filter by one field or by a time window. GET /clients/offices.

• idx_list_leads

  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

• idx_get_lead

  One 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_notes

  Notes on a lead, or one note when note_id is given. GET /leads/note/{leadID}[/{noteID}].

• idx_list_lead_searches

  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}].

• idx_list_lead_saved_properties

  Properties a lead saved (or one when property_id is given). GET /leads/property/{leadID}[/{propertyID}].

• idx_get_lead_traffic

  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}.

• idx_list_featured_listings

  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.

• idx_list_sold_pending_listings

  The account's sold and pending listings, that is those removed from the MLS feed. GET /clients/soldpending.

• idx_list_off_market_listings

  The account's off-market listings. GET /clients/offmarket.

• idx_list_supplemental_listings

  The account's supplemental (non-MLS) listings with a basic set of fields. GET /clients/supplemental.

• idx_list_saved_links

  Saved links (pre-built property search pages) of the account with id, name and URL. GET /clients/savedlinks.

• idx_get_saved_link_count

  The total number of properties a saved link currently matches. GET /clients/savedlinks/{savedLinkID}/count.

• idx_list_widgets

  The JavaScript widgets on the account with id, name, URL and options. GET /clients/widgets.

• idx_get_widget

  One JavaScript widget with its settings. GET /clients/widgets/{id}.

• idx_list_system_links

  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.

• idx_list_approved_mls

  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.

• idx_get_mls_age

  When an MLS feed was last downloaded and processed and when its images were last gathered (UTC). GET /mls/age/{idxID}.

• idx_list_mls_property_types

  Property 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_fields

  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}.

• idx_list_mls_locations

  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|posta

• idx_create_lead

  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 re

• idx_add_lead_note

  WRITE: adds a note to a lead (visible to the account's agents). Returns the new note id. PUT /leads/note/{leadID}.

• idx_update_lead

  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}.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 21 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 27 个工具描述，未发现针对 AI 的隐藏指令

与“营销与社交媒体”中的其他服务器比较i

• 星标数多于此分类中其他 3686 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 3686 个服务器的 93% 更新
• 基础检查结果等于或优于此分类中其他 3686 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{