Skip to main content
Glama
jlucasmcrell

Apify Public Data & Leads

by jlucasmcrell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Apify Public Data & Leads

  • actors-mcp-server by apify

    actors-mcp-serverofficial

    apify
    A
    license
    A
    quality
    A
    maintenance
    Use 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
    12
    30,525 npm
    13,947
    MIT

Related Servers

  • The Mine Works MCP servers by themineworks

    The Mine Works MCP serversofficial

    themineworks
    A
    license
    Not graded
    quality
    C
    maintenance
    Seven 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.
    1
    MIT

  • webdata-tools-mcp

    tacps126
    A
    license
    A
    quality
    A
    maintenance
    21 web-data tools for AI agents: jobs, hiring signals, news, research and field trends, reviews, Reddit leads, contacts, property, Shopify, events.
    25
    439 npm
    MIT

  • getregdata

    Nolpak14
    A
    license
    A
    quality
    B
    maintenance
    Exposes 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.
    38
    6
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

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

ActivitySlowing
ResponsivenessNo issues

Resources