MCP Agent Brokerage Resolver

Agent to Brokerage Resolver MCP Server

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
• Quick start
• Prerequisites
• Example prompts
• Tool
• Inputs
• Pricing
• Your keys
• Full actor documentation
• License

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

• Node.js 18 or newer.
• An Apify API token from console.apify.com/account/integrations, set as APIFY_TOKEN. The server lists its tool without a token; a call needs one.

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

Pricing

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

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.