LeadMarina
Server Details
Verified local-business leads: search by niche and US city, export to Close, GoHighLevel or Sheets.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- macgregordev/leadmarina-mcp
- GitHub Stars
- 0
- Server Listing
- LeadMarina MCP server
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 19 tools
The search family (search_leads, run_advanced_search, query_leads, get_search_results, list_searches) overlaps conceptually, but the descriptions draw explicit boundaries: live niche+city search vs. multi-keyword/place batch search vs. free querying of already-collected leads vs. polling results vs. history. A few pairs (search_leads vs. run_advanced_search, get_search_results vs. query_leads) could still be misselected by a hurried agent, but the cross-references reduce that risk substantially.
Almost everything follows a clean snake_case verb_noun pattern (create_automation, delete_automation, list_searches, get_balance, export_leads). The main blemish is the pause/resume/stop lifecycle being named control_advanced_search for searches but update_automation for automations, and 'control' is a vaguer verb than 'update' or 'pause'.
Nineteen tools is on the heavy side but each covers a distinct slice of the product: simple search, advanced search (run/estimate/get/list/control), automations (CRUD-ish), library query, export, views, integrations, places, balance, and domain enrichment. No obvious redundancy or filler tools; it would benefit slightly from consolidating the advanced-search listing/status tools.
Coverage is broad and coherent across the full lifecycle: discover places, estimate, run, poll, query, filter via saved views, export, schedule with automations, and check balance/integrations. Minor gaps remain — no way to cancel or delete a plain search_leads run (only advanced searches get control), no delete/cleanup of library leads, and no single-automation getter (list only).
Available Tools
19 toolscontrol_advanced_searchPause, resume or stop an advanced searchBDestructiveIdempotentInspect
action pause or stop takes effect after the batches running now (a queued batch is cancelled and refunded); resume carries on.
Inputs: action (required), campaign_id (required). Returns: id, name, leads, places, +12 more
create_automationSchedule a recurring searchAInspect
Create an automation: re-run a search on a schedule and send the results somewhere automatically. Pass cities as plain strings (e.g. ['Austin, TX', 'Dallas, TX']) — they're resolved for you. IT SPENDS LEADS ON EVERY RUN, one per result, so confirm the niche, cities and cadence with the user before creating one. A destination of 'close', 'ghl' or 'google_sheets' requires that integration to be connected already (Close with no saved field mapping sends Close's own fields); 'csv' | 'xlsx' | 'json' emails a file and needs nothing set up. Every city must resolve and the destination must be one of the listed values, or nothing is created and the error says what to fix. Up to 20 automations, 25 cities each. Automations search US places only for now: a city outside the US is refused. Advanced search's options (a country other than the US — a territory included — max_leads, exact_category) are refused here too.
Inputs: cities (required), cadence (required), keyword (required), start_at, +2 more. Returns: id, note, cities, cadence, +4 more
delete_automationDelete an automationADestructiveIdempotentInspect
Permanently delete an automation. This cannot be undone — confirm with the user first, and prefer update_automation with active=false if they only want it to stop for now. Leads already collected by past runs are kept; only the schedule is removed.
Inputs: id (required). Returns: id, note, deleted
enrich_domainsEnrich business domainsAInspect
Already have businesses? Pass up to 10 website domains to run the full enrichment + verification pipeline on them (verified emails + phones, owner name, socials). Costs 1 lead per distinct domain — spellings of the same site (acme.com, www.acme.com, https://acme.com/contact) count once. Returns a search_id to poll with get_search_results. US businesses only for now: their phones are read as US numbers.
Inputs: domains (required). Returns: note, enriching, next_step, search_id, +1 more
estimate_advanced_searchEstimate an advanced searchARead-onlyIdempotentInspect
What an advanced search (many keywords across many places) would find and how long it would take — without starting it or spending anything. expected_leads is the most likely number of unique leads (each business is charged once however many keywords or places find it); low–high is the range it lands in most of the time.
Inputs: keywords (required), name, places, country, +3 more. Returns: low, high, time, places, +8 more
export_leadsExport leads to a destinationADestructiveInspect
Push leads into a connected destination: 'close' (CRM — uses the account's saved field mapping), 'ghl' (GoHighLevel sub-account), 'google_sheets' (new spreadsheet, or pass spreadsheet_id for one LeadMarina created before), or a file — 'csv' | 'xlsx' | 'json' (a 7-day download link in the answer; not emailed). Exports EITHER one search's leads (pass search_id) or the whole library (set all=true). Either can be narrowed with the same filter rows as query_leads — with search_id they apply within that search. Leads go out best-ranked first (rank, then id), the order of the leads table. LIMITS PER CALL, which differ by destination because CRMs take one API call per lead: csv/xlsx 50,000 · json 25,000 · google_sheets 5,000 · close/ghl 1,000. For a big library going to a CRM, export csv and import the file instead. If more leads match than the limit, the response sets truncated=true and returns next_cursor — relay that to the user, the export was partial; to send the next batch, call export_leads again with the SAME destination, search_id or all, and filters, plus cursor=next_cursor — for google_sheets also spreadsheet_id from this response, or the next batch goes into a new spreadsheet (up to 50,000 leads a spreadsheet; past that the response has no spreadsheet_id and the next batch starts a new one, or export csv). A next_cursor with not_sent means the destination's time limit cut this batch short: the same call with that cursor sends the rest. An all=true export spread over several calls reads the library live, so a lead that a search running between calls finds again can be skipped or sent twice; for one consistent copy, export the library in a single csv/xlsx (up to 50,000 leads) or json (up to 25,000) call while no search is running. Close, GoHighLevel and a LeadMarina-created sheet passed as spreadsheet_id UPDATE previously exported leads in place (matched by Google CID), never touching the user's own CRM notes/columns — unless update_existing is false (then Close skips leads it already has, and a sheet appends every row); a file or a new sheet is a fresh copy every time — so do not repeat a call that succeeded. Or pass campaign_id instead of search_id to export one advanced search's leads.
Inputs: destination (required), all, cursor, filters, +6 more. Returns: file, note, limit, outcome, +9 more
find_placesFind US states and placesARead-onlyIdempotentInspect
Where an advanced search can run — the US and its territories for now. With no arguments: the US and its territories (Puerto Rico, Guam …), with their codes. With country 'US': its states and their codes. With q: US places whose name contains q, with their codes and states — for run_advanced_search's places, or search_leads' location_code.
Inputs: q, country. Returns: places, region, country, regions, +2 more
get_advanced_searchGet an advanced searchBRead-onlyIdempotentInspect
One advanced search: status, leads so far, progress by keyword, its top places and the newest batch running now.
Inputs: campaign_id (required). Returns: id, name, leads, places, +15 more
get_balanceGet lead balanceARead-onlyInspect
What the account has left. On a plan with a rate limit this is the smaller of what the account holds and what is left in the current 7-day period (period_* describe that week, and period_resets_at is when the week resets); on a metered plan it is the account's lead balance. On a rate-limited plan with a monthly allowance, the note names the allowance when it can be read.
Inputs: no named parameters. Returns: note, plan, period_used, period_limit, +2 more
get_search_resultsGet search resultsARead-onlyInspect
Fetch a search's leads with verification filled in as enrichment progresses. Poll until enrichment is 'complete'. Each lead includes verified emails (SMTP status), verified phones (line type + carrier), owner name where identified, socials, and the business profile.
Inputs: search_id (required), limit, offset. Returns: query, stage, period, results, +10 more
list_advanced_searchesList advanced searchesARead-onlyIdempotentInspect
This account's advanced searches, newest first: status, leads so far, searches done of total. The newest limit, plus any still running or paused past them.
Inputs: limit. Returns: advanced_searches
list_automationsList scheduled searchesARead-onlyInspect
The account's automations — saved searches that re-run on a schedule and export themselves. Shows each one's niche, cities, cadence, destination, whether it's active, when it next runs, and how the last run went.
Inputs: no named parameters. Returns: count, automations, data_sources
list_integrationsList connected integrationsARead-onlyInspect
Which export destinations this account has connected (Close, GoHighLevel, Google Sheets) and whether each is ready to receive leads. Check this BEFORE export_leads or create_automation with a CRM destination — those fail if the integration isn't connected. Close with no saved field mapping sends Close's own fields (name, website, address, contact, phone, email). File destinations (csv/xlsx/json) always work and need nothing connected.
Inputs: no named parameters. Returns: integrations
list_searchesList recent searchesARead-onlyInspect
The account's recent searches (id, niche, location, result count, when) — use a search_id with get_search_results or export_leads.
Inputs: limit. Returns: searches
list_viewsList saved viewsARead-onlyInspect
The account's saved views from the leads table — each a named set of filters the user already built (e.g. 'Roofers with a mobile number'). Returns each view's filter conditions in the exact shape query_leads and export_leads accept, so "export my Hot Leads view to Close" works without rebuilding the filters by hand.
Inputs: no named parameters. Returns: count, views
query_leadsQuery the lead libraryARead-onlyInspect
Search ALL leads the account has ever collected (across every search) with filters and sorting — no new search is run and no leads are spent. A Google listing found more than once appears once, with its most recent data. Up to 1,000 leads per call (default 25). When next_cursor is set, call again with cursor = next_cursor for the next page: the cursor carries its filters and sort, so it can be sent alone. Pass search_id to query one search's leads instead of the whole library. Example — plumbers in Austin rated 4.5 or higher with a safe email, most-reviewed first: filters=[{field:'category',operator:'contains',value:'plumb'},{field:'city',operator:'is',value:'Austin',conj:'and'},{field:'rating',operator:'gte',value:'4.5',conj:'and'},{field:'email_status',operator:'is',value:'safe',conj:'and'}], sort=[{id:'reviews',dir:-1}]. A field, operator or value the tool cannot use comes back as an error that names it and lists what works. Pass campaign_id instead of search_id to query one advanced search's leads.
Inputs: sort, limit, cursor, filters, +2 more. Returns: results, returned, next_cursor, data_sources, +1 more
run_advanced_searchRun an advanced searchAInspect
Start an advanced search: many keywords across many US places — the whole US, whole states or single places — run in the background in batches, each business charged once (1 lead), stopping at lead_cap if set. Estimate first with estimate_advanced_search and confirm with the user: it spends leads. Follow it with get_advanced_search; read its leads with query_leads or send them with export_leads (campaign_id). Up to 25 running or paused at once, and 40 new ones (or 250,000 searches) a day.
Inputs: keywords (required), name, places, country, +3 more. Returns: id, name, leads, places, +17 more
search_leadsSearch local-business leadsAInspect
Run a live search for local businesses by niche + city (e.g. query 'electrician', location 'Austin, TX'). Returns a search_id and, usually, the first batch immediately (its listings are in results; their emails and phones are not verified yet — when discovery is 'in_progress' the provider was slow and the whole search was queued, so the leads arrive through get_search_results); more results are found and verified in the background — every email is SMTP-checked and phones are verified with line type + carrier. Spends 1 lead per result. Poll get_search_results until enrichment is 'complete'. If enrichment is already 'complete', nothing was found and nothing more is coming; if capped is true, the balance covered fewer leads than were found. With country, a US territory (PR, GU, VI, AS, MP) is searched; max_leads stops it early and exact_category keeps only that Google category. For many keywords or places at once, use run_advanced_search.
Inputs: query (required), country, location, max_leads, +2 more. Returns: found, query, capped, results, +8 more
update_automationPause or resume an automationAIdempotentInspect
Pause an automation (active=false) so it stops running and stops spending leads, or resume it (active=true). Pausing is the safe way to stop an automation you might want back — use delete_automation only when the user wants it gone for good.
Inputs: id (required), active (required). Returns: id, note, active, data_sources
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Local business leads by niche and city: owner names, checked emails, phone line types, site tech.
Local business leads with email and phone, plus hiring and ad signals. For you or your AI agent.
Finds, filters, and verifies local-business leads; every email carries a verification receipt.
Find 16M+ US businesses by city/category; build lead lists with owners, contacts, status and hours.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceDiscovers local businesses needing a website via OpenStreetMap and verifies their leads with checks like website existence, email deliverability, and site quality scoring.23 PyPIMIT

LocalPro MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceProvides verified local trade and service business data (e.g., radon mitigation, foundation repair) to AI agents via tools like search_providers and list_niches.1MIT
LeadMerlin MCP serverofficial
AlicenseNot gradedqualityBmaintenanceEnables MCP clients to find local businesses by niche and city and retrieve enriched lead data such as owner names, verified emails, phone line types, and website technology. It also supports enriching existing domains and checking website tech stacks.MIT- AlicenseNot gradedqualityDmaintenanceFinds, filters, and verifies local-business leads on demand; every returned email carries a verification receipt (verifier, verdict, timestamp). Credit-based with per-key spend budgets; 25 free validated leads at signup.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.