Skip to content

LeadMarina MCP server

com.leadmarina/leadmarinaleadmarina.comstreamable-httpv1.3.0Scanned

Verified local-business leads: search by niche and US city, export to Close, GoHighLevel or Sheets.

19 tools: 3 can delete or cancel things, 5 change things and 11 only read.

Tools: 3 delete, 0 irreversible, 5 write, 11 read.
  • Reads private data · 1
  • Reads text others write · 5
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the LeadMarina MCP server can do

The LeadMarina MCP server is published by leadmarina.com, a domain the MCP Registry verified. It has 19 tools. It can delete or cancel things (3 tools: export_leads, delete_automation and control_advanced_search) and create or change data (5 tools: search_leads, enrich_domains, create_automation, update_automation and 1 more). 11 tools only read.

1 tool reads private data (list_views); 5 tools bring in text other people can write (search_leads, enrich_domains, export_leads and 2 more).

The fixed checks matched 2 findings (long-description and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 1.3.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

19 tools

Deletes or cancels 3Claude Code: deny
  • delete_automationPermanently delete an automation.No findings

    Why it is in this group

    • The name "delete_automation" says "delete": a word for removing or ending something.
    • The description says "Permanently delete".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Delete an automation
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • export_leadsPush leads into a connected destination: 'close' (CRM — uses the account's saved field mapping), 'ghl' (GoHighLevel sub-account), 'google_sheets' (new spreadsheet, or pass spreadsh…Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "push": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,229 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: ".... Or pass campaign_id instead of search_id to export one advanced search's leads."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Export leads to a destination
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Changes things 5Claude Code: ask
  • create_automationCreate an automation: re-run a search on a schedule and send the results somewhere automatically.Reads text others writeNo findings

    Why it is in this group

    • The name "create_automation" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Schedule a recurring search
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • enrich_domainsAlready have businesses?Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Enrich business domains
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • search_leadsRun a live search for local businesses by niche + city (e.g.Reads text others writeNo findings

    Why it is in this group

    • The name "search_leads" says "search": a word for reading.
    • The description's first verb is "run": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search local-business leads
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • update_automationPause an automation (active=false) so it stops running and stops spending leads, or resume it (active=true).No findings

    Why it is in this group

    • The name "update_automation" says "update": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Pause or resume an automation
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 11Show 11 read-only tools
  • find_placesWhere an advanced search can run — the US and its territories for now.No findings

    Why it is in this group

    • The name "find_places" says "find": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find places
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_balanceWhat the account has left.No findings

    Why it is in this group

    • The name "get_balance" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get lead balance
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_search_resultsFetch a search's leads with verification filled in as enrichment progresses.No findings

    Why it is in this group

    • The name "get_search_results" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get search results
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_advanced_searchesThis account's advanced searches, newest first: status, leads so far, searches done of total.No findings

    Why it is in this group

    • The name "list_advanced_searches" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List advanced searches
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_automationsThe account's automations — saved searches that re-run on a schedule and export themselves.No findings

    Why it is in this group

    • The name "list_automations" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List scheduled searches
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_integrationsWhich export destinations this account has connected (Close, GoHighLevel, Google Sheets) and whether each is ready to receive leads.No findings

    Why it is in this group

    • The name "list_integrations" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List connected integrations
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_searchesThe account's recent searches (id, niche, location, result count, when) — use a search_id with get_search_results or export_leads.No findings

    Why it is in this group

    • The name "list_searches" says "list": a word for reading.
    Description, as the server wrote it
    The account's recent searches (id, niche, location, result count, when) — use a search_id with get_search_results or export_leads.

    Annotations the server declares

    • title: List recent searches
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_viewsThe account's saved views from the leads table — each a named set of filters the user already built (e.g.Reads private dataNo findings

    Why it is in this group

    • The name "list_views" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "table": it reads databases.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List saved views
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • query_leadsSearch ALL leads the account has ever collected (across every search) with filters and sorting — no new search is run and no leads are spent.No findings

    Why it is in this group

    • The name "query_leads" says "query": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Query the lead library
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:41 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
8
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://leadmarina.com/.well-known/oauth-protected-resource
Authorization servers
https://leadmarina.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 8 tools that change things (3 destructive, 5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://leadmarina.com/api/mcp: tools/list returned 19 tools to an anonymous client, including export_leads (destructive), delete_automation (destructive), control_advanced_search (destructive), search_leads (write), enrich_domains (write) and 3 more

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 6 to 8

Findings

Matches of fixed checks, with the text they matched.

1 warn1 info
  • The server marks "control_advanced_search" destructive (destructiveHint: true), and its name says "search", a word for reading.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":true,"openWorldHint":false}; The name "control_advanced_search" says "search": a word for reading.

    What this check looks for
  • The description is 2,229 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: ".... Or pass campaign_id instead of search_id to export one advanced search's leads."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools6 changed.~6 changedView diff
  2. Tools6 added, 5 changed.+6 added~5 changedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 8.View diff
    • Tools that change things, listed without credentials: 6 to 8

Install

Pinned to version 1.3.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http leadmarina https://leadmarina.com/api/mcp
claude mcp add --transport http leadmarina https://leadmarina.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__leadmarina__get_search_results",
      "mcp__leadmarina__query_leads",
      "mcp__leadmarina__list_searches",
      "mcp__leadmarina__get_balance",
      "mcp__leadmarina__list_views",
      "mcp__leadmarina__list_integrations",
      "mcp__leadmarina__list_automations",
      "mcp__leadmarina__find_places",
      "mcp__leadmarina__estimate_advanced_search",
      "mcp__leadmarina__list_advanced_searches",
      "mcp__leadmarina__get_advanced_search"
    ],
    "ask": [
      "mcp__leadmarina__search_leads",
      "mcp__leadmarina__enrich_domains",
      "mcp__leadmarina__create_automation",
      "mcp__leadmarina__update_automation",
      "mcp__leadmarina__run_advanced_search"
    ],
    "deny": [
      "mcp__leadmarina__export_leads",
      "mcp__leadmarina__delete_automation",
      "mcp__leadmarina__control_advanced_search"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as leadmarina. Review it before you use it.

Capability tags behind 6 rules
  • mcp__leadmarina__search_leads untrusted-input
  • mcp__leadmarina__enrich_domains untrusted-input
  • mcp__leadmarina__export_leads untrusted-input
  • mcp__leadmarina__list_views private-data
  • mcp__leadmarina__create_automation untrusted-input
  • mcp__leadmarina__run_advanced_search untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.leadmarina/leadmarina/verify?hash=efffa7c1efdd0039d9bd85bfddf70a92724493268d3f9b02bbda5ec3cb76a3d4" | jq -e '.changed == false'

Pinned hash efffa7c1efdd, from Nov 12, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.leadmarina/leadmarina/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.leadmarina/leadmarina
[![Anlyon Radar](https://radar.anlyon.com/badge/com.leadmarina/leadmarina.svg)](https://radar.anlyon.com/servers/com.leadmarina/leadmarina)

Source: MCP Registry · repository. Synced Oct 31, 2026, 04:17 UTC.

LeadMarina MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the LeadMarina MCP server safe?

No scan can promise that. What its definitions show: 19 tools, 8 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the LeadMarina MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: export_leads, delete_automation and control_advanced_search.

Can the LeadMarina MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the LeadMarina MCP server have?

19 tools: 3 destructive, 5 write, 11 read. export_leads, delete_automation, control_advanced_search, search_leads, enrich_domains, create_automation, update_automation, run_advanced_search and 11 more.

Does the LeadMarina MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the LeadMarina MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the LeadMarina MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.