com.mambabuilt/mcp-agent-brokerage-resolver

Find a US real estate agent's brokerage, brokerage size, and license status from state registers.

OtherTypeScriptv1.0.1

Agent to Brokerage Resolver MCP Server

Smithery Glama score MCP Registry npm version npm downloads license mcpservers.org

An MCP server for the Mamba Labs Agent to Brokerage Resolver actor on Apify. Give it a licensed US real estate agent, by license number or by name and state, and get the brokerage of record from the official state license register, that brokerage's active agent count and size band, and the agent's license status and expiry. It can also list every active agent at a brokerage, or every brokerage office in a zip code.

What's Inside

What it does

Look up a licensed US real estate agent on the official state license register and get the brokerage of record, the brokerage's active agent count and size band (1, 2-15, 16-50, 51+), and the agent's license status and expiry. Covers 19 states; brokerage data in CA, IA, MO, NV, NY, OH, OR, TX, and VT. Three modes: lookup (one agent or a list, by license number or by name), roster_firm (active agents at one brokerage), and roster_zip (brokerage offices in a zip code, NY, MO, OR, and VT). Returns no emails, phone numbers, or home addresses. Ambiguous or unmatched inputs return a free row with row_status explaining why. A run that does not succeed is returned as an error with its run ID.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

{
  "mcpServers": {
    "mamba-agent-brokerage-resolver": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-agent-brokerage-resolver"
      ],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Restart the client. The resolve_agent_brokerage tool appears.

Prerequisites

Example prompts

  • "Which brokerage is Texas agent 134224-SA with, and how big is it?"
  • "List the active agents at the brokerage with Texas license 566433-BB."
  • "Which real estate brokerages have an office in zip 14201, and how many agents does each have?"

Tool

resolve_agent_brokerage. One tool. Example arguments:

{ "mode": "lookup", "state": "TX", "license_number": "134224-SA" }

Inputs

InputTypeRequiredDescription
modestringnolookup, roster_firm, or roster_zip. Default lookup.
statestringnoTwo letter licensing state, for example TX.
license_numberstringnoLookup mode. The agent's license number as the register prints it.
agent_namestringnoLookup mode, when there is no license number. First and last name.
brokerage_namestringnoNarrows a name match; names the firm in roster_firm mode.
citystringnoNarrows a name match by office city or license county.
licensesstringnoLookup batch, one per line: state then license number.
agentsstringnoLookup batch, one per line: state, name, brokerage, city, separated by a vertical bar.
brokerage_license_numberstringnoroster_firm mode. The brokerage's license number.
zipstringnoroster_zip mode. A five digit zip code.
zipsstringnoroster_zip batch, one zip per line.
include_agentsstringnoroster_zip mode. true also lists each office's active agents.
active_onlystringnoRoster modes. Active licenses only. Default true.
max_resultsstringnoRoster modes. Rows per brokerage or zip, 1 to 1000. Default 100.
max_charge_usdstringnoOptional. The run stops before the row that would take its charges over this amount.

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

EventFree planBronzeSilverGold
agent-resolved, per matched lookup row$0.005$0.00475$0.0045$0.00425
roster-row, per roster row$0.002$0.0019$0.0018$0.0017
apify-actor-start, per run start$0.0005$0.000475$0.00045$0.000425

Ambiguous, not found, unsupported state, and capped rows are never charged.

Your keys

The actor needs no provider key. It reads MMG's own index of the state license registers through a Mamba Labs service and holds no key of its own. Each actor run sends its own Apify run token to that service, which reads the run from the Apify API on every request to confirm it is a live run of this actor. The service caches no result and never stores or logs the token.

Full actor documentation

apify.com/mambalabs/agent-brokerage-resolver

License

MIT. See LICENSE.

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y @mambalabsdev/mcp-agent-brokerage-resolver

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json
{
  "mcpServers": {
    "com-mambabuilt-mcp-agent-brokerage-resolver": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-agent-brokerage-resolver"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

@mambalabsdev/mcp-agent-brokerage-resolvernpm

Compatible MCP Clients

com.mambabuilt/mcp-agent-brokerage-resolver works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More