Skip to main content
Glama
evascrape

Evascrape MCP server

Official
by evascrape
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Evascrape MCP server

No user-submitted related servers found.

    Related Servers

    • leads-mcp

      AtomicIntuition
      A
      license
      A
      quality
      D
      maintenance
      Lead generation MCP server for AI agents. Find emails, verify contacts, enrich profiles, and search prospects using Hunter.io, Apollo.io, and Abstract API.
      8
      13 npm
      MIT
    • scrapercity-cli by scrapercity

      scrapercity-cliofficial

      scrapercity
      A
      license
      B
      quality
      A
      maintenance
      B2B lead generation MCP server with 20+ lead generation tools - Apollo scraping, Google Maps, email finder, email validator, mobile finder, skip trace, ecommerce store data, and more.
      25
      466 npm
      1
      MIT
    • Getlead MCP server by Adgrowofficial

      Getlead MCP serverofficial

      Adgrowofficial
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables finding B2B leads with verified work emails, finding and verifying email addresses, and running cold email outreach from any MCP client.
      MIT
    • FullEnrich MCP by FullEnrich

      FullEnrich MCPofficial

      FullEnrich
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to search B2B people and companies, enrich contacts with verified emails and mobile phone numbers via waterfall enrichment across 25+ providers, and export results as CSV or JSON. Supports prospecting, org mapping, candidate sourcing, and outreach workflows through OAuth-authenticated remote access from any MCP-compatible client.
      9
      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 7 tools

    Disambiguation5/5

    The three lead tools clearly target different sources (Google Maps scraping, Apollo URL export, LinkedIn filter-based search), and the support tools (check_balance, job_status, estimate_cost, download) each have a distinct role. No two tools can be reasonably confused for the same task.

    Naming Consistency4/5

    All names use snake_case consistently, but the convention varies slightly: source-oriented nouns (google_maps_leads, linkedin_leads, apollo_export) mix with verb-oriented names (check_balance, estimate_cost, download, job_status). Still predictable and readable throughout.

    Tool Count5/5

    Seven tools is well-scoped for a scraping service: three job-starting sources plus four support operations (balance, status, cost, download). Every tool earns its place with no redundancy.

    Completeness4/5

    The job lifecycle (start -> poll -> download), cost estimation, and balance checks are all covered, matching the async job model. Minor gaps like listing/cancelling existing jobs or a job history tool exist but agents can work around them.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources