Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
Leadmarina is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
13
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Verified local-business leads: search any niche + city, query your library, export to your CRM.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http leadmarina-mcp https://leadmarina.com/api/mcp
# 2 — ask your agent for something these tools do
# search_leads, get_search_results, enrich_domains and 10 more
Leadmarina costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LEAll 1 server
leadmarina1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http leadmarina-mcp https://leadmarina.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Business niche/category keyword, e.g. 'electrician'. |
| location | string | no | City, e.g. 'Austin, TX'. Not needed with location_code, which is always what is searched. |
| location_code | number | no | Optional exact location code. When given, it is what is searched, whatever location says. Sent with location, the search is named after the code's own place (or after location when the code's own name |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search_id | string | yes | The search_id returned by search_leads or enrich_domains. |
| limit | number | no | Max leads to return (default 25, max 1000). |
| offset | number | no | Pagination offset (default 0). |
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 num
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domains | array | yes | Business domains, e.g. ['acme.com'] (max 10). |
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 sen
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search_id | string | no | Only this search's leads (a search_id from search_leads or list_searches) — e.g. to narrow one search before export_leads with the same search_id and filters. Omit to query the whole library. |
| filters | array | no | Conditions, each {field, operator, value, conj}; omit to match every lead. text fields [operators: contains, not_contains, is, is_not, is_empty, is_not_empty]: name, category, city, state, country, po |
| sort | array | no | Sort keys in priority order, e.g. [{id:'reviews',dir:-1}] for most-reviewed first. id is any filter field id (the column ids email_1, email_1_status, phone_1, phone_1_type and phone_1_carrier work too |
| limit | number | no | Max leads to return (default 25, max 1,000). |
| cursor | string | no | next_cursor from the previous call, for the next page. It carries that call's filters and sort: send it alone, or with the same filters and sort — different ones are refused. Leave it out to start a n |
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 the account owner when the file is small enough to attach). Exports EITHER one search's leads (pass s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| destination | string | yes | Where the leads go. |
| search_id | string | no | Export this search's leads. |
| all | boolean | no | Export the whole library instead of one search. |
| filters | array | no | Optional query_leads-style filter rows: within the search when search_id is given, across the library with all=true. |
| spreadsheet_id | string | no | google_sheets only: add to this existing LeadMarina-created sheet instead of a new one. |
| cursor | string | no | Continue an export: the next_cursor a previous export_leads call returned. Pass it with the same search_id/all and filters. |
The account's recent searches (id, niche, location, result count, when) — use a search_id with get_search_results or export_leads.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | number | no | Max searches (default 10, max 25). |
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.
No parameter schema on file.
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.
No parameter schema on file.
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 export first to save its field mapping. File destinations (csv/xlsx/json) always work and need nothing
No parameter schema on file.
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.
No parameter schema on file.
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 conn
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | string | yes | The niche to search, e.g. 'roofing contractor'. |
| cities | array | yes | Cities to search, e.g. ['Austin, TX'] (max 25). |
| cadence | string | yes | How often it repeats. |
| destination | string | no | Where each run's leads go. 'none' just saves them to the library. |
| spreadsheet_id | string | no | google_sheets only: add each run to this existing LeadMarina-created sheet, updating rows already in it. |
| start_at | string | no | ISO timestamp for the first run. Defaults to now (runs on the next tick, within 15 min). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The automation id from list_automations. |
| active | boolean | yes | false to pause, true to resume. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The automation id from list_automations. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Leadmarina or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.2.0.
1.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Leadmarina can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.