Name: B2b Prospect Engine
Author: Mamba Labs

B2b Prospect Engine MCP

Enrich companies, discover hiring signals and find verified contacts in one actor.

Grade A Local · stdio API key 1 tool v1.2.0 · 16 Oct 2026

No reviews yet by Mamba Labsnpm 1,430 Runs on your machine, nothing hosted

96/100

trust score

downloads a day

local

runs on your machine

591

downloads in 30d

What it does

Turn a domain or a hiring keyword into enriched company records and verified contacts, with ICP scoring and the source of every field.

All of the work runs on Mamba Labs actors on Apify. This server is a thin client: it starts the run, waits for it, and hands back the results. Add it to Claude, Cursor, or any MCP client with one npx line and your own APIFY_TOKEN.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --env 'APIFY_TOKEN=${APIFY_TOKEN}' --transport stdio b2b-prospect-engine-mcp '--' npx -y @mambalabsdev/mcp-b2b-prospect-engine

# 2 — ask your agent for something these tools do
#   run_prospect_engine

It needs APIFY_TOKEN: this reads it from your environment, so export it first.

B2b Prospect Engine costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publisher

Mamba Labs63 servers

8 categories · publishing since 2026

All 63 servers

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts B2b Prospect Engine as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.

Claude Codedeclared by this listing

This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads APIFY_TOKEN (Apify API token from https://console.apify.com/account/integrations) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx APIFY_TOKEN … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.

claude mcp add --scope user --env 'APIFY_TOKEN=${APIFY_TOKEN}' --transport stdio b2b-prospect-engine-mcp '--' npx -y @mambalabsdev/mcp-b2b-prospect-engine

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

It reaches a system of yours, so it needs your own credential rather than the publisher’s: APIFY_TOKEN — Apify API token from https://console.apify.com/account/integrations. You set it in your own client’s config, on your machine — this marketplace never holds it.

What it writes

One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.

What you approve

1 tool, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Read from its source code. A server that builds its tool list when it starts can list more tools than this.

A composed prospecting actor with four modes. enrich_companies resolves identity, firmographics, LinkedIn and social for each domain or company name you supply, and needs no vendor key at all. discover_jobs finds who is hiring for your keywords and resolves the real employer behind each posting,…

Parameter	Type	Required	Notes
mode	string	no	What to run. enrich_companies resolves identity, firmographics, LinkedIn and social for each company. discover_jobs finds who is hiring for your keywords and resolves the real employer from the job de
domains	array	no	One domain per line. Used by enrich_companies and find_contacts.
company_names	array	no	One name per line. Used when you have a name but no domain.
keywords	array	no	Roles to search for. Used by discover_jobs and full. Example: copy editor, proofreader, content editor. Default: ["copy editor", "proofreader", "content editor"].
country	string	no	Two letter country code for job search, for example us or gb. Default: "us".
location	string	no	Optional location filter for job search, for example New York.
lookback_days	string	no	Drop postings older than this many days. Sent as a string because Clay sends every field as a string. Default: "30".
max_results	string	no	Cap on postings returned per run. Keeps a broad keyword set from running away. Default: "25".
max_pages	string	no	1 to 5. Each page is one SerpAPI call, so this is the main cost dial on discovery. Default: "1".
new_postings_only	string	no	true to return only postings not seen in a previous run. Default: "false".
previous_run_date	string	no	YYYY-MM-DD watermark for delta detection when the cross-run cache is unavailable.
remote_only	string	no	true to keep only postings flagged remote by the board. Default: "false".
company_size_min	string	no	Drop companies below this headcount. Only takes effect once headcount is known, so it applies in full mode and to any discovery row that carried an employee count. Discovery alone does not enrich.
company_size_max	string	no	Drop companies above this headcount. Same condition as the minimum.
exclude_staffing	string	no	true to drop postings from staffing and recruitment agencies. Default: "true".
exclude_marketplaces	string	no	true to drop Upwork, Fiverr, Freelancer and similar gig listings. Default: "true".
extra_marketplaces	array	no	Additional marketplace names to filter out.
fetch_posting_page	string	no	true to open the job posting when the description alone does not identify the employer. Slower, and it is what catches a job board posting on an employer's behalf. Default: "true".
target_contacts	string	no	1 to 25. Default: "3".
target_roles	array	no	Only enrich contacts whose title plausibly matches one of these roles. Filters after discovery and before any paid email lookup, so a non-matching contact costs nothing. Leave empty to keep every cont

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under MIT
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install B2b Prospect Engine or to call it, at any volume.

ATrust score 96 / 100

Release 1.2.0 · scanned 16 Oct 2026

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score96

Findings1 threat · 0 capability

Capabilitymoderate

Coveragesource

Verificationrepo

Surface digestcd9fa4181b8933ee18ac8db6937d3269d914fb8f236d6bf1c35c69dfb6985159

Score vectorthreat 100 → client 96

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
verification-discount	repo	publisher verification (public source) — no provenance, but the source is public and inspectable	−1
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfaceread

Implementation sourceread

Package metadataread

Live transportnot available

Tools were statically extracted from the published source (1 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
run_prospect_engine	external-sink	external-sink: declares readOnlyHint: false, openWorldHint: true, handler sends an HTTP POST (fetch(https://api.apify.com/v2/acts/${actorPath}/runs?timeout=${ACTOR_RUN_TIMEOUT_SECS}) at build/index.js:79

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digestcd9fa4181b8933ee

Scanned2026-10-16

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.