This server is a B2B prospecting tool that acts as a thin client for the Prospect Engine actor on Apify. It offers four configurable modes:
Enrich Companies: Resolve identity, firmographics, LinkedIn and social profiles for given domains or names.
Discover Jobs: Find companies hiring by keywords, country, location, and recency; filter by remote, company size, and exclude staffing agencies.
Find Contacts: Locate people at companies by job title, seniority, department, with optional email discovery and verification via integrated APIs (Findymail, Icypeas, Prospeo, Reoon, BounceBan).
Full Pipeline: Chain discovery, enrichment, ICP scoring (A–D tiers using presets like editorial_services or generic_b2b), and contact discovery, gated by minimum ICP score.
Additional features include:
Fine-tuned control over results via parameters like max_results, max_pages, lookback_days, and new_postings_only.
Integration with third‑party APIs (SerpApi, Serper) for job and people search.
Customizable signal taxonomy for company classification.
Delta detection to return only new postings not seen before.
Company size filtering and optional social media resolution (Facebook, Instagram, X, YouTube).
Cost control through caps on API calls and results.
Read-only operation; surfaces errors explicitly rather than silently returning empty results.
Enables enrichment of company profiles with Facebook social media presence.
Allows filtering out job postings from Fiverr and similar gig marketplaces.
Allows filtering out job postings from Freelancer and similar gig marketplaces.
Enables enrichment of company profiles with Instagram social media presence.
Allows filtering out job postings from Upwork and similar gig marketplaces.
Enables enrichment of company profiles with YouTube social media presence.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Prospect Engine MCP Server Enrich company domains: acme.com, globex.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for the Mamba Labs Prospect Engine actor on Apify.
Four modes in one actor: enrich companies you already have, discover who is hiring for your keywords, find contacts at a company, or run the whole chain end to end with an ICP gate in the middle.
npx -y @mambalabsdev/mcp-b2b-prospect-engine{
"mcpServers": {
"mamba-b2b-prospect-engine": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-b2b-prospect-engine"],
"env": { "APIFY_TOKEN": "your-apify-token" }
}
}
}Get an Apify token at console.apify.com/account/integrations.
Related MCP server: Prospeo MCP Server
run_prospect_engineFour modes in one actor: enrich companies you already have, discover who is hiring for your keywords, find contacts at a company, or run the whole chain end to end with an ICP gate in the middle.
Input | Type | Required | Notes |
| enum | 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 description. find_contacts finds people at each company. full chains all three. |
| array | no | One domain per line. Used by enrich_companies and find_contacts. |
| array | no | One name per line. Used when you have a name but no domain. |
| array | no | Roles to search for. Used by discover_jobs and full. Example: copy editor, proofreader, content editor. |
| string | no | Two letter country code for job search, for example us or gb. |
| string | no | Optional location filter for job search, for example New York. |
| string | no | Drop postings older than this many days. Sent as a string because Clay sends every field as a string. |
| string | no | Cap on postings returned per run. Keeps a broad keyword set from running away. |
| string | no | 1 to 5. Each page is one SerpAPI call, so this is the main cost dial on discovery. |
| string | no | true to return only postings not seen in a previous run. |
| string | no | YYYY-MM-DD watermark for delta detection when the cross-run cache is unavailable. |
| string | no | true to keep only postings flagged remote by the board. |
| 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. |
| string | no | Drop companies above this headcount. Same condition as the minimum. |
| string | no | true to drop postings from staffing and recruitment agencies. |
| string | no | true to drop Upwork, Fiverr, Freelancer and similar gig listings. |
| array | no | Additional marketplace names to filter out. |
| 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. |
| string | no | 1 to 25. |
| array | no | Titles to search for when finding contacts. |
| array | no | c_level, vp, director, manager, senior. |
| array | no | marketing, sales, engineering, product, finance, hr, operations, legal. |
| string | no | true to run the email waterfall. Needs an Icypeas or Prospeo key, which you supply and are billed for directly. |
| string | no | true to verify each address. Needs a Reoon or BounceBan key. |
| string | no | true to score every row against the ICP rules and tier it A to D. |
| enum | no | Which scoring model to apply. "editorial_services" scores for a seller of managed copy editing and proofreading. "generic_b2b" scores on hiring intent, employer resolvability and headcount with no service-specific vocabulary. |
| string | no | In full mode, only companies scoring at or above this go on to contact discovery. Default 45: at 25 the filter passed every keyword-discovered editorial posting, because 25 is the floor such a posting can score. |
| array | no | Any company whose name contains one of these is excluded. |
| array | no | Override the default signal types. Each entry is an object with type, strength, title_keywords, and optional also_keywords and description_keywords. |
| string | no | true to resolve Facebook, Instagram, X and YouTube alongside LinkedIn. |
| string | no | 5 to 120. A source that exceeds this is marked degraded and the run continues. |
| string | no | true to ignore the 7 day cross-run cache and recompute everything. |
| string | no | Your Serper.dev key. Powers people search in find_contacts, which is the highest-coverage layer. Without it the free fallback is measurably poor. |
| string | no | Your Findymail key. First provider in the email waterfall. |
| string | no | Your Icypeas key. Runs on Findymail misses. |
| string | no | Your Prospeo key. Runs on the residual after Findymail and Icypeas. |
| string | no | Your Reoon key. First email verification provider. |
| string | no | Your BounceBan key. Second verifier, used for the catch-all case. |
| string | no | Your SerpApi key. Required by discover_jobs and full. Distinct from a Serper key: different vendor. |
You are charged per company enriched, per contact verified and per job posting discovered, at different rates for basic and full enrichment. Vendor API calls are billed to you by those vendors directly.
Pricing is on the actor's Apify page. Running this server consumes Apify credits.
It is a thin client for the Apify actor. It passes your input through and returns the actor's output unchanged. Every behavior described above lives in the actor, not here.
Errors are surfaced, never swallowed. An invalid input, an invalid token, an exhausted balance, a timeout, or a run that returns anything other than a dataset all come back as an explicit tool error rather than as an empty result.
The actor is on the Apify Store. This wrapper is MIT licensed.
Built by Mamba Labs
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, including postings a job board placed on an employer's behalf. find_contacts finds people at the companies you name, with optional email discovery and verification. full runs discovery, enrichment, ICP scoring and then contact discovery, passing only the companies at or above min_icp_score through to the contact stage. Every row comes back flat and Clay ready with per field provenance. Vendor keys are yours: you supply them, those vendors bill you directly, and the per event price covers the actor only. discover_jobs and full require a SerpApi key, which is a different vendor from the Serper key that powers people search. Note that this actor is a pass through wrapper over the live actor, so any classification behavior you see is the actor's own. Requires an APIFY_TOKEN and consumes Apify credits. Read only: it enriches and discovers, it writes nothing.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | 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 description. find_contacts finds people at each company. full chains all three. Default: "enrich_companies". | |
| country | No | Two letter country code for job search, for example us or gb. Default: "us". | |
| domains | No | One domain per line. Used by enrich_companies and find_contacts. | |
| keywords | No | Roles to search for. Used by discover_jobs and full. Example: copy editor, proofreader, content editor. Default: ["copy editor", "proofreader", "content editor"]. | |
| location | No | Optional location filter for job search, for example New York. | |
| max_pages | No | 1 to 5. Each page is one SerpAPI call, so this is the main cost dial on discovery. Default: "1". | |
| score_icp | No | true to score every row against the ICP rules and tier it A to D. Default: "true". | |
| seniority | No | c_level, vp, director, manager, senior. | |
| icp_preset | No | Which scoring model to apply. "proofed_editorial" scores for a seller of managed copy editing and proofreading. "generic_b2b" scores on hiring intent, employer resolvability and headcount with no service-specific vocabulary. Default: "proofed_editorial". | |
| job_titles | No | Titles to search for when finding contacts. | |
| skip_cache | No | true to ignore the 7 day cross-run cache and recompute everything. Default: "false". | |
| departments | No | marketing, sales, engineering, product, finance, hr, operations, legal. | |
| max_results | No | Cap on postings returned per run. Keeps a broad keyword set from running away. Default: "25". | |
| remote_only | No | true to keep only postings flagged remote by the board. Default: "false". | |
| serpapi_key | No | Your SerpApi key. Required by discover_jobs and full. Distinct from a Serper key: different vendor. | |
| verify_email | No | true to verify each address. Needs a Reoon or BounceBan key. Default: "true". | |
| company_names | No | One name per line. Used when you have a name but no domain. | |
| include_email | No | true to run the email waterfall. Needs an Icypeas or Prospeo key, which you supply and are billed for directly. Default: "false". | |
| lookback_days | No | Drop postings older than this many days. Sent as a string because Clay sends every field as a string. Default: "30". | |
| min_icp_score | No | In full mode, only companies scoring at or above this go on to contact discovery. Default 45: at 25 the filter passed every keyword-discovered editorial posting, because 25 is the floor such a posting can score. Default: "45". | |
| reoon_api_key | No | Your Reoon key. First email verification provider. | |
| include_social | No | true to resolve Facebook, Instagram, X and YouTube alongside LinkedIn. Default: "true". | |
| serper_api_key | No | Your Serper.dev key. Powers people search in find_contacts, which is the highest-coverage layer. Without it the free fallback is measurably poor. | |
| icypeas_api_key | No | Your Icypeas key. Runs on Findymail misses. | |
| prospeo_api_key | No | Your Prospeo key. Runs on the residual after Findymail and Icypeas. | |
| signal_taxonomy | No | Override the default signal types. Each entry is an object with type, strength, title_keywords, and optional also_keywords and description_keywords. | |
| target_contacts | No | 1 to 25. Default: "3". | |
| company_size_max | No | Drop companies above this headcount. Same condition as the minimum. | |
| company_size_min | 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. | |
| exclude_staffing | No | true to drop postings from staffing and recruitment agencies. Default: "true". | |
| bounceban_api_key | No | Your BounceBan key. Second verifier, used for the catch-all case. | |
| findymail_api_key | No | Your Findymail key. First provider in the email waterfall. | |
| new_postings_only | No | true to return only postings not seen in a previous run. Default: "false". | |
| previous_run_date | No | YYYY-MM-DD watermark for delta detection when the cross-run cache is unavailable. | |
| extra_marketplaces | No | Additional marketplace names to filter out. | |
| fetch_posting_page | 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". | |
| extra_exclude_names | No | Any company whose name contains one of these is excluded. | |
| source_timeout_secs | No | 5 to 120. A source that exceeds this is marked degraded and the run continues. Default: "30". | |
| exclude_marketplaces | No | true to drop Upwork, Fiverr, Freelancer and similar gig listings. Default: "true". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description explicitly states 'Read only: it enriches and discovers, it writes nothing,' reinforcing the annotations. It adds substantial context beyond annotations: vendor key billing, APIFY_TOKEN requirement, pass-through wrapper nature, and that classification behavior is the actor's own. This fully discloses behavioral nuances.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is lengthy but well-organized: it starts with the core definition, then breaks down each mode, then covers vendor keys and operational notes. Every sentence contributes unique information (e.g., per-field provenance, SerpApi vs Serper distinction), though some redundancy exists. For a tool with 39 parameters and 4 modes, the length is justified.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (39 parameters, 4 modes, no output schema), the description is remarkably complete. It covers mode-specific behaviors, key requirements, billing, output format ('Every row comes back flat and Clay ready with per field provenance'), caching, and read-only semantics. It effectively compensates for the lack of an output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for all 39 parameters, so the baseline is 3. The description adds high-level flow context (e.g., 'full runs discovery, enrichment, ICP scoring and then contact discovery') but does not provide additional details on individual parameters beyond what the schema already specifies. It does not compensate further, so a 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states 'A composed prospecting actor with four modes' and enumerates each mode with its function (enrich_companies, discover_jobs, find_contacts, full). It clearly defines the tool's purpose of enriching and discovering prospects, leaving no ambiguity about what the tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context on when to use each mode and what prerequisites are needed (e.g., 'discover_jobs and full require a SerpApi key'). It notes that enrich_companies needs no vendor key and that the tool is read-only and Clay-ready, implying typical use cases. However, there are no explicit exclusions or alternatives since no sibling tools exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0run_prospect_engineWith only one tool, there is no possibility of confusing it with others. The tool's name clearly indicates a single entry point, even though it internally supports multiple modes.
The single tool name follows a clear 'verb_noun' pattern (run_prospect_engine), and there are no other tools to create inconsistency.
Having only one tool for a multi-step prospecting workflow (enrichment, job discovery, contact finding) is under-scoped. The distinct functions would typically be separated into multiple tools for clarity and modularity.
Despite being a single tool, it covers the core prospecting actions described: enrichment, job discovery, ICP scoring, and contact discovery. As a read-only actor, no write operations are expected, so there are no obvious gaps in the stated domain.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Build prospecting lists from buying signals, enrich them, and run LinkedIn outreach.
B2B prospecting from your Enginy workspace: find, enrich, and reach contacts and companies.
B2B lead generation, email verification, company enrichment, and agentic GTM Ops.
Run B2B outreach from your AI agent: 250+ tools for campaigns, leads, LinkedIn and email workflows.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mambalabsdev/mcp-b2b-prospect-engine'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
