Mcp Agent Brokerage Resolver

com.mambabuiltPublished by mambabuilt.comv1.0.2Updated Nov 7, 2026

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

VerifiedSTDIODesktop onlyLocation & LifestyleBusiness & Commerce

Overview

AI-generated overview

Looks up US real estate agents on state license registers to return their brokerage, brokerage size band, and license status via an Apify actor.

What you can do
  • Resolve one agent or a batch by license number or name and state, returning brokerage of record, brokerage active agent count and size band, and license status and expiry
  • List the active agents at a given brokerage by its license number
  • List brokerage offices in a zip code, optionally with each office's active agents
  • Report ambiguous, unmatched, unsupported-state or capped inputs as free rows with a row_status explanation
When to use it
Useful when you need to check which brokerage a licensed US agent is affiliated with, how large that brokerage is, or whether a license is active, and when you want rosters of agents at a firm or offices in a zip code. Coverage is 19 states, with brokerage data only in CA, IA, MO, NV, NY, OH, OR, TX and VT.
Requirements
Runs locally as an npm package over stdio, so Node.js 18 or newer is needed. An Apify account and an Apify API token set as the APIFY_TOKEN environment variable are required; the tool is listed without a token but a call needs one. Network access to Apify is required, and the client must be a desktop MCP client.
Before you install
Calls are billed per event to your Apify account (per matched lookup row, per roster row, and per run start), so repeated or large roster requests cost money; an optional max_charge_usd input caps a run's charges. The APIFY_TOKEN is a secret that grants access to your Apify account. Each run sends its Apify run token to a Mamba Labs service that verifies the run against the Apify API. Results come from third-party state registers and may be incomplete for unsupported states.

Installation

In SourceWeft

  1. Open Mcp Agent Brokerage Resolver in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Agent to Brokerage Resolver MCP Server

[Glama score] [MCP Registry] [npm version] [npm downloads] [license] [mcpservers.org]

[Agent 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

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:

json
{  "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:

json
{ "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.

Source: README.md at commit 41fe4c4

Tools

1

resolve_agent_brokerage

Resolve agent brokerage

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. Read-only; requires an APIFY_TOKEN and consumes Apify credits per matched row.

Parameterszipcitymodezipsstateagentslicensesagent_nameactive_onlymax_resultsbrokerage_nameinclude_agents+3 more

Version history

2
  1. v1.0.2LatestNov 5, 2026
  2. v1.0.1Oct 19, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts