# com.mambabuilt/mcp-agent-brokerage-resolver (npm · @mambalabsdev/mcp-agent-brokerage-resolver)

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

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@mambalabsdev/mcp-agent-brokerage-resolver`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-mambabuilt-mcp-agent-brokerage-resolver/mambalabsdev-mcp-agent-brokerage-resolver.md), [page](https://verifymcp.io/servers/com-mambabuilt-mcp-agent-brokerage-resolver/mambalabsdev-mcp-agent-brokerage-resolver)

## Channel facts

- Registry: `npm`
- Package: `@mambalabsdev/mcp-agent-brokerage-resolver`
- Version: `1.0.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 16 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 617 tokens (~617/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the com.mambabuilt/mcp-agent-brokerage-resolver server?

com.mambabuilt/mcp-agent-brokerage-resolver runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-agent-brokerage-resolver. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-mambabuilt-mcp-agent-brokerage-resolver -- npx -y @mambalabsdev/mcp-agent-brokerage-resolver
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add com-mambabuilt-mcp-agent-brokerage-resolver -- npx -y @mambalabsdev/mcp-agent-brokerage-resolver
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mambabuilt-mcp-agent-brokerage-resolver": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mambalabsdev/mcp-agent-brokerage-resolver"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-mambabuilt-mcp-agent-brokerage-resolver --command npx --arg -y --arg @mambalabsdev/mcp-agent-brokerage-resolver
```

### Hermes

```yaml
mcp_servers:
  com-mambabuilt-mcp-agent-brokerage-resolver:
    command: "npx"
    args: ["-y", "@mambalabsdev/mcp-agent-brokerage-resolver"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-mambabuilt-mcp-agent-brokerage-resolver": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@mambalabsdev/mcp-agent-brokerage-resolver"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mambabuilt-mcp-agent-brokerage-resolver -t stdio -c npx -a -y @mambalabsdev/mcp-agent-brokerage-resolver
```

### Other

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 69, +11)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85

## MCP tools (1)

### `resolve_agent_brokerage` (~617 tokens)

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.

Input parameters:

- `active_only` (string): Roster modes. List only agents with an active license. Default true.
- `agent_name` (string): Lookup mode, when there is no license number. First and last name. Add brokerage_name or city to narrow a common name.
- `agents` (string): Lookup mode, many at once. One per line: state | name | brokerage (optional) | city (optional).
- `brokerage_license_number` (string): roster_firm mode. The brokerage's license number.
- `brokerage_name` (string): Lookup mode: narrows a name match. roster_firm mode: the brokerage to list, by its exact registered name.
- `city` (string): Lookup mode: narrows a name match by the brokerage office city or the license county.
- `include_agents` (string): roster_zip mode. true also lists the active agents at each office. Default false.
- `license_number` (string): Lookup mode. The agent's license number as the state register prints it, for example 134224-SA. The most reliable lookup.
- `licenses` (string): Lookup mode, many at once. One per line: state then license number, for example TX 0123456.
- `max_charge_usd` (string): Optional. The run stops before the row that would take its charges over this amount.
- `max_results` (string): Roster modes. Most rows one brokerage or zip returns, 1 to 1000. Default 100.
- `mode` (string): lookup finds one agent or a list. roster_firm lists the active agents at one brokerage. roster_zip lists brokerage offices in a zip code (NY, MO, OR, VT). Default lookup.
- `state` (string): Two letter licensing state, for example TX. Used with license_number, agent_name, or the brokerage fields.
- `zip` (string): roster_zip mode. A five digit zip code.
- `zips` (string): roster_zip mode, many at once. One zip code per line.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-mambabuilt-mcp-agent-brokerage-resolver/mambalabsdev-mcp-agent-brokerage-resolver#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 73
- 2026-10-29: 73
- 2026-10-28: 72
- 2026-10-27: 72
- 2026-10-26: 71
- 2026-10-25: 71
- 2026-10-24: 71
- 2026-10-23: 70
- 2026-10-22: 70
- 2026-10-21: 69
- 2026-10-20: 69
- 2026-10-19: 58

## Common questions

### What is the com.mambabuilt/mcp-agent-brokerage-resolver server?

com.mambabuilt/mcp-agent-brokerage-resolver is listed in the public MCP registry as com.mambabuilt/mcp-agent-brokerage-resolver. Find a US real estate agent's brokerage, brokerage size, and license status from state registers. This page covers its npm package (@mambalabsdev/mcp-agent-brokerage-resolver).

### Is the com.mambabuilt/mcp-agent-brokerage-resolver server safe to use?

com.mambabuilt/mcp-agent-brokerage-resolver scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the com.mambabuilt/mcp-agent-brokerage-resolver server expose?

com.mambabuilt/mcp-agent-brokerage-resolver exposes 1 tool: resolve_agent_brokerage. Their descriptions and schemas cost roughly 617 tokens of context every time the server is loaded.

### Is the com.mambabuilt/mcp-agent-brokerage-resolver server still maintained?

com.mambabuilt/mcp-agent-brokerage-resolver is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the com.mambabuilt/mcp-agent-brokerage-resolver server under?

com.mambabuilt/mcp-agent-brokerage-resolver declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@mambalabsdev/mcp-agent-brokerage-resolver
- Socket report: https://socket.dev/npm/package/@mambalabsdev/mcp-agent-brokerage-resolver
- Repository: https://github.com/mambalabsdev/mcp-agent-brokerage-resolver
- Changelog RSS feed: https://verifymcp.io/servers/com-mambabuilt-mcp-agent-brokerage-resolver/mambalabsdev-mcp-agent-brokerage-resolver.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mambabuilt-mcp-agent-brokerage-resolver/mambalabsdev-mcp-agent-brokerage-resolver.json
- HTML version of this page: https://verifymcp.io/servers/com-mambabuilt-mcp-agent-brokerage-resolver/mambalabsdev-mcp-agent-brokerage-resolver