actors-mcp-serverofficial
A
licenseA
qualityA
maintenanceUse 3,000+ pre-built cloud tools from Apify, known as Actors, to extract data from websites, e-commerce, social media, search engines, maps, and more
10
27,480 npm
9,184
MIT
Apify Public Data & Leads
by jlucasmcrell
Related Servers
Alternatives to Apify Public Data & Leads
Related Servers
- AlicenseNot gradedqualityCmaintenanceSeven remote MCP servers exposing 51 published Apify scrapers as agent tools: company diligence, social listening, recruiting, real estate, lead generation, e-commerce and academic research. Billed per result, and a call that returns nothing is never charged.1MIT
- AlicenseAqualityBmaintenanceExposes 29 official business-registry actors as MCP tools for KYC/AML, beneficial-owner (UBO), credit-risk and adverse-media workflows across 11 jurisdictions (EU, US, UAE). Sourced via Apify; pay-per-result.386MIT
- AlicenseNot gradedqualityDmaintenanceEnables web scraping, browser automation, and dataset management through Apify's actor platform.MIT
- AlicenseAqualityNot gradedmaintenanceUnified API for Government Data and Web Scraping100-
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to search Google Maps places and retrieve reviews, photos, scrape jobs, results, and exports through a hosted MCP API.MIT
Crawlora MCPofficial
AlicenseCqualityAmaintenanceHosted MCP server for 3,093 structured public web-data tools across 420 platform groups, returning clean JSON for search, maps, commerce, social, and finance.4500536 npm1MIT
TDQS
A4.1/5.0
Scored across 40 tools
Disambiguation4/5
Most tools are clearly distinguished by data source (e.g., app_store vs google_play, linkedin vs glassdoor, sec_edgar vs sec_form_4). The main ambiguity comes from aggregator/subset pairs like company_registry_search vs french_company_search vs gleif_lei_search, and us_business_entity_search vs its state-specific tools, but the detailed 'When NOT to use' and 'Named alternatives' sections resolve this for an agent that reads them.
Naming Consistency4/5
The large majority follow a snake_case source_subject_search pattern (e.g., epa_facility_search, nhtsa_vehicle_recall_search, linkedin_jobs_search), which is predictable and scannable. A minority use noun-phrase or action names (twitch_live_streams, usaspending_contracts, us_census_geocoder, tech_stack_detector), but there is no camelCase mixing and the overall style remains consistent.
Tool Count2/5
At 40 tools, the set is well beyond the 25+ threshold that reads as too many, and the broad 'public data & leads' purpose does not justify the granular duplication: three contractor-license tools, five business-entity tools, and two overlapping company-registry tools. The count could be meaningfully trimmed by keeping only the multi-state/multi-platform aggregators and dropping the single-state/single-dataset variants.
Completeness3/5
The set covers a wide swath of public-data categories, including business registries, contractor licenses, jobs, app reviews, biomedical research, government contracting, and security vulnerabilities. However, for a server branded as 'Leads', it lacks general web search, people/contact enrichment, and most US state business registries, leaving notable gaps that agents must work around.
Maintenance
ActivityMaintained
ResponsivenessNo issues