Is Company Discovery List Builder free?

Yes, Company Discovery List Builder is free to use.

How do I install Company Discovery List Builder?

Company Discovery List Builder is a local plugin. Install it using npm package: @mambalabsdev/mcp-company-discovery-list-builder and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Company Discovery List Builder safe to use?

Yes. Company Discovery List Builder passed MCP Marketplace's automated security scan with a score of 10/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What credentials does Company Discovery List Builder need?

Company Discovery List Builder requires the following credentials or environment variables: APIFY_TOKEN. You can find setup instructions on the server detail page.

What AI apps work with Company Discovery List Builder?

Company Discovery List Builder uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Company Discovery List Builder MCP Server

by mambabuilt

Developer ToolsLow Risk10.0Local

Free

Build a company list from live hiring data or from US SEC filings mentioning a phrase.

About

Build a company list from live hiring data or from US SEC filings mentioning a phrase.

Security Report

10.0

Low Risk10.0Low Risk

Valid MCP server (2 strong, 3 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (68/68 approved).

9 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

Shell Command Execution

Runs commands on your machine. Be cautious — only use if you trust this plugin.

What You'll Need

Set these up before or after installing:

Apify API token from https://console.apify.com/account/integrationsRequired

Environment variable: APIFY_TOKEN

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "com-mambabuilt-mcp-company-discovery-list-builder": {
      "env": {
        "APIFY_TOKEN": "your-apify-token-here"
      },
      "args": [
        "-y",
        "@mambalabsdev/mcp-company-discovery-list-builder"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Company Discovery List Builder MCP Server

MCP server for the Mamba Labs Company Discovery List Builder actor on Apify.

Market in, companies out. Give it role keywords and a location and it returns the companies currently hiring for that. A second mode returns US SEC filers whose filings contain your phrase. No paid data source is involved.

Install

npx -y @mambalabsdev/mcp-company-discovery-list-builder

Claude Desktop

{
  "mcpServers": {
    "mamba-company-discovery-list-builder": {
      "command": "npx",
      "args": ["-y", "@mambalabsdev/mcp-company-discovery-list-builder"],
      "env": { "APIFY_TOKEN": "your-apify-token" }
    }
  }
}

Get an Apify token at console.apify.com/account/integrations.

Tool

`build_company_list`

Input	Type	Required	Notes
`mode`	enum	yes	hiring returns companies currently hiring for your role keywords, built from a live index of public Greenhouse and Ashby job boards. filings returns US SEC filers whose filings contain your phrase. One of: `hiring`, `filings`.
`role_keywords`	string	no	Comma separated. Matched as whole words against live job titles, so account executive matches Enterprise Account Executive and does not match Executive Assistant. Leave empty to match any role. Used in hiring mode.
`filing_phrase`	string	no	Exact phrase searched in SEC filings, for example agentic AI. Used in filings mode.
`filing_forms`	string	no	Comma separated SEC form types, for example 10-K,10-Q. Used in filings mode. Default: "10-K".
`location_contains`	string	no	Substring match against the job location string, for example London, Remote, New York. Locations are free text on every job board, so this is a plain substring test: Remote does not match US Remote.
`min_open_jobs`	string	no	Skip companies with fewer open roles than this. A rough size proxy. Sent as a string so it works from Clay. Default: "1".
`max_companies`	string	no	How many companies to return, 1 to 2000. Sent as a string so it works from Clay. You are billed per company returned, not per company examined. Default: "100".
`resolve_domains`	boolean	no	Look up each company's website. On by default: it adds roughly a second per company and about two thirds of companies resolve. Set false for a faster list without domains. Check domain_status and domain_confidence before trusting a result. Default: true.
`refresh_universe`	boolean	no	Force a fresh Common Crawl enumeration instead of the cached one. The cached universe is rebuilt about monthly on its own, so leave this off unless you need the newest crawl. Default: false.
`max_charge_usd`	number	no	Optional cost cap in USD for this run. The actor stops before an item that could take its charges past this amount. Omit to rely on the maximum cost per run set in Apify.

Billing

You are charged per company returned, not per company examined, plus a small actor start fee. max_companies is therefore a hard cost cap.

Price per event on the Apify FREE plan, from the live pricing record; paid Apify plans pay less per event.

Event	Price (USD)
Actor Start (`apify-actor-start`)	0.00005
Company found (`company-found`)	0.004

Pricing is on the actor's Apify page. Running this server consumes Apify credits.

What this server does and does not do

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 tool starts the actor run and polls it to a finished status, so a long run is not cut off at 300 seconds. The run is allowed 1,800 seconds. If it is still going two minutes after that, the call stops waiting and returns the run ID with a link to it in the Apify Console, where the results land when it finishes. A run that does not succeed comes back as an error with its run ID and status.