Company Discovery List Builder MCP Server
Related Servers
Alternatives to Company Discovery List Builder MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables monitoring of job postings by keyword, returning companies currently advertising those roles enriched with firmographics and LinkedIn URLs via Apify.185 npmMIT
- AlicenseAqualityAmaintenanceEnables B2B lead generation through Apify's Prospect Engine actor, supporting company enrichment, job discovery, contact finding, and full ICP-gated outreach workflows.176 npmMIT
- AlicenseAqualityAmaintenanceEnables users to turn keywords or social media handles into finished influencer lead lists with contact details, using the Apify actor.10MIT
- AlicenseAqualityAmaintenanceEnables pushing enriched leads into Instantly or Smartlead campaigns with ICP score gating, deduplication, and dry-run previews via an Apify actor.187 npmMIT
- AlicenseAqualityAmaintenanceExtracts people (names and titles) from a company's team, leadership, or about page given a domain. Uses Apify to crawl and return structured data, with optional filters for seniority and email inclusion.165 npmMIT
- AlicenseAqualityBmaintenanceEnables users to convert a vendor partner directory (such as PartnerPage or the Shopify Partner Directory) or a trade body member list into one company row per listing, each carrying website, domain, tier, tags, and location for Clay-ready output. It runs the extraction on Apify, returning dataset rows for up to 20 directory URLs with optional deduping, detail enrichment, and a cost cap.1367 npmMIT
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.