Ext Ops Panel
Open dashboard
Comparison

Needle Remote vs com.mambabuilt/mcp-agent-brokerage-resolver

Needle Remote is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). com.mambabuilt/mcp-agent-brokerage-resolver is an MCP server published by mambabuilt.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceNeedle Remotecom.mambabuilt/mcp-agent-brokerage-resolver
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
Downloads/month (npm): 106
Downloads/week (npm): 106
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Needle Remote vs com.mambabuilt/mcp-agent-brokerage-resolver
FactNeedle Remotecom.mambabuilt/mcp-agent-brokerage-resolver
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub1
Last release (differs)Not published2026-11-05
Where it runs (differs)Remote server (mcp.needle.app/mcp)On your machine (@mambalabsdev/mcp-agent-brokerage-resolver)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/mambalabsdev/mcp-agent-brokerage-resolver
Changes in the last 7 days (differs)01
First seen (differs)2026-10-112026-10-19
Endpoint at the last check (differs)Answered with HTTP 301 (less than an hour ago)no remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Needle Remote

In its own words, on Docker MCP Catalog:

Production-ready RAG service to search and retrieve data from your documents.

com.mambabuilt/mcp-agent-brokerage-resolver

In its own words, on Official MCP Registry:

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

How to run each

Needle Remote As a remote MCP server

Claude Code
claude mcp add --transport http needle https://mcp.needle.app/mcp

Requires: NEEDLE_API_KEY (secret)

com.mambabuilt/mcp-agent-brokerage-resolver As a local MCP server: npm package

Claude Code
claude mcp add --env "APIFY_TOKEN=<YOUR_APIFY_TOKEN>" --transport stdio mcp-agent-brokerage-resolver -- npx -y @mambalabsdev/mcp-agent-brokerage-resolver

Requires: APIFY_TOKEN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Needle Remote has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only Needle Remote asks for

  • NEEDLE_API_KEY (secret)

Only com.mambabuilt/mcp-agent-brokerage-resolver asks for

  • APIFY_TOKEN (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Needle Remote · What it can do: com.mambabuilt/mcp-agent-brokerage-resolver · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built