Evascrape MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVASCRAPE_API_KEY | Yes | Key from your Evascrape account (starts with evs_live_). Required to authenticate with the Evascrape API. | |
| EVASCRAPE_BASE_URL | No | Override the API host, for testing. Must be https. |
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 |
|---|---|
| google_maps_leadsA | Find local businesses and their contact details from Google Maps: name, address, phone, website, rating, and the email address published on the business website where there is one. Use this for requests like "find 200 dentists in Austin with their emails", "get me restaurants in Berlin with phone numbers" or "build a list of plumbers near Manchester". This is the best starting point for local business prospecting. Costs $12 per 1,000 records from a prepaid balance; you are refunded for anything not delivered. Returns a job id, not the data: poll job_status, then call download. |
| apollo_exportA | Export the results of a people search you already built on Apollo.io, past Apollo's own export cap and without consuming Apollo export credits. You must supply the Apollo search URL. Only leads that have a verified email address are delivered, so the count can be lower than the number Apollo displays. Costs $9 per 1,000. Returns a job id: poll job_status, then download. |
| linkedin_leadsA | Build a list of people from LinkedIn and Sales Navigator audiences using filters, and get their verified work email addresses. This takes filters, not a LinkedIn URL: job titles, locations, company domains, keywords, industry, company size and revenue range. Use it for requests like "CMOs at SaaS companies in California" or "heads of engineering at companies using Stripe". Costs $9 per 1,000. If you get far fewer results than requested, set include_unverified to true: that single filter is the most common reason a list comes back short. Returns a job id: poll job_status, then download. |
| job_statusA | Check whether an Evascrape job has finished. Call this about 30 seconds after starting a job and then every 20 to 30 seconds. When the status is "succeeded", call download to read the records. |
| downloadA | Read the records of a finished Evascrape job as structured data. Returns the field names and the rows, paged. Ask for a job that has already reached the status "succeeded". With email verification enabled you can pick a variant: "good" for deliverable addresses only, "risk" for catch-all, "bad" for undeliverable. Default "all". |
| check_balanceA | Show how much prepaid credit is left on the Evascrape account, in USD. Check this before starting a large job. |
| estimate_costA | Return what a job would cost without starting it or charging anything. Use this before spending on behalf of someone, or when the user asks how much a list will cost. |
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 7 tools
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.
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.
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.
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.