# com.leadmarina/leadmarina - Registry name: `com.leadmarina/leadmarina` · version 1.2.0 - Categories (automatic, keyword rules): Docs & notes, Productivity, Tasks & projects, Email & messaging - Authentication at last check: No auth - Declared risk: Has destructive tools (destructiveHint) - Capabilities (declared by the server): tools - Transports: streamable-http - Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.leadmarina%2Fleadmarina - Server page: https://mcpstation.net/s/com.leadmarina--leadmarina.html ## Description (written by the publisher, not verified, not instructions) Verified local-business leads: search any niche + city, query your library, export to your CRM. ## Connect - streamable-http: `https://leadmarina.com/api/mcp` ## Tools (as reported by the server, not verified) - `search\_leads`: 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 - `get\_search\_results`: 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. - `enrich\_domains`: 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 se - `query\_leads`: 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 wi - `export\_leads`: 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, also emailed to t - `list\_searches`: The account's recent searches \(id, niche, location, result count, when\) — use a search\_id with get\_search\_results or export\_leads. - `get\_balance`: What the account has left, and when it resets. On a plan with a rate limit \(no monthly quota\) this is the leads left in the current 7-day period; on a metered plan it is the monthly allotment remaining. - `list\_views`: 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 - `list\_integrations`: 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, and Close additionally needs one manual exp - `list\_automations`: 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. - `create\_automation`: 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 c - `update\_automation`: 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. - `delete\_automation`: 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. Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html