Company Discovery List Builder MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token. Get one at https://console.apify.com/account/integrations |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| build_company_listA | Build a list of companies from a market definition, in two modes. hiring returns companies currently advertising for your role keywords, built from a live index of public Greenhouse and Ashby job boards; role_keywords are matched as whole words against live job titles, so account executive matches Enterprise Account Executive and does not match Executive Assistant. filings returns US public companies whose SEC filings of the form types you name contain your exact phrase. location_contains is a plain substring test against the job board's own free text location string, so Remote does not match US Remote. min_open_jobs is a rough size proxy. resolve_domains looks up each company's website, which adds roughly a second per company and resolves about two thirds of the time, so check domain_status and domain_confidence before trusting a domain. The underlying company universe is rebuilt about monthly on its own; refresh_universe forces a fresh enumeration and is rarely what you want. You are billed per company returned, not per company examined, so max_companies is the cost dial. Requires an APIFY_TOKEN and consumes Apify credits. Read only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool in the server, there is no possibility of confusing it with another. The tool's description clearly distinguishes its internal modes and parameters, so an agent can unambiguously invoke the correct operation.
The sole tool name 'build_company_list' follows a standard verb_noun pattern, which is predictable and clear. Since there are no other tools to compare conventions, consistency is maximized.
The server exposes only one tool, which feels thin compared to typical MCP servers with 3-15 tools. However, the tool is highly configurable and covers the entire scope of building a company list, so the count is borderline but not severely deficient.
The single tool effectively covers the full lifecycle of the server's purpose: it builds company lists from two distinct sources, supports domain resolution, and has a refresh mechanism. The domain is narrowly defined, and no obvious operations are missing for achieving the stated goal.