# com.leadmarina/leadmarina (remote · leadmarina.com)

Verified local-business leads: search any niche + city, query your library, export to your CRM.

- Trust score: 77/100 (medium)
- Change this week: +53
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `leadmarina.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-leadmarina-leadmarina/api-mcp.md), [page](https://verifymcp.io/servers/com-leadmarina-leadmarina/api-mcp)

## Channel facts

- Endpoint: `https://leadmarina.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1079 tokens (~154/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.com-leadmarina-leadmarina]
url = "https://leadmarina.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-leadmarina-leadmarina": {
      "type": "remote",
      "url": "https://leadmarina.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-leadmarina-leadmarina --url https://leadmarina.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-leadmarina-leadmarina:
    url: "https://leadmarina.com/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-leadmarina-leadmarina": {
      "type": "http",
      "url": "https://leadmarina.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 76, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-31 (score 75, +51)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 24, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-27 (score 24, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 24)

First indexed and scored.

## MCP tools (7)

### `search_leads` (~149 tokens)

Search local-business leads

Run a live search for local businesses by niche + city (e.g. query 'electrician', location 'Austin, TX'). Returns the first batch immediately with a search_id; more results are found and verified in the background — every email is SMTP-checked and every phone verified with line type + carrier. Spends 1 lead per result. Poll get_search_results until enrichment is 'complete'.

Input parameters:

- `location` (string): City, e.g. 'Austin, TX'. Ignored if location_code is given.
- `location_code` (number): Optional exact location code (skips the city lookup).
- `query` (string, required): Business niche/category keyword, e.g. 'electrician'.

Output parameters:

- `delivered_so_far` (number)
- `enrichment` (string): 'pending' until background verification finishes.
- `leads_remaining` (number)
- `location` (string|null)
- `next_step` (string)
- `query` (string)
- `search_id` (string)

### `get_search_results` (~109 tokens)

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.

Input parameters:

- `limit` (number): Max leads to return (default 25, max 100).
- `offset` (number): Pagination offset (default 0).
- `search_id` (string, required): The search_id returned by search_leads or enrich_domains.

Output parameters:

- `enrichment` (string): 'pending' or 'complete'.
- `leads_remaining` (number|null)
- `location` (string|null)
- `query` (string|null)
- `results` (array)
- `search_id` (string)
- `showing` (string): Range shown, e.g. '1–25'.
- `total_leads` (number)

### `enrich_domains` (~80 tokens)

Enrich business 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 domain. Returns a search_id to poll with get_search_results.

Input parameters:

- `domains` (array, required): Business domains, e.g. ['acme.com'] (max 10).

Output parameters:

- `enriching` (array): Domains accepted (balance-capped).
- `enrichment` (string)
- `next_step` (string)
- `search_id` (string)

### `query_leads` (~282 tokens)

Query the lead library

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. Filter fields include: name, category, city, state, rating, reviews, website, claimed, owner_name, phone_1, email_1, email_1_status, phone_1_type, google_cid. Operators: contains, not_contains, is, is_not, starts_with, gt, gte, lt, lte, is_empty, is_not_empty, is_true, is_false. Combine rows with conj 'and'/'or'. Example: find rated-4.5+ plumbers in Austin with a verified email: filters=[{field:'category',operator:'contains',value:'plumb'},{field:'city',operator:'is',value:'Austin',conj:'and'},{field:'email_1_status',operator:'is',value:'safe',conj:'and'}].

Input parameters:

- `cursor` (string): Opaque pagination cursor from a previous call.
- `filters` (array): Filter conditions (optional — omit for everything, newest data first).
- `limit` (number): Max leads to return (default 25, max 100).
- `sort` (array): Sort keys, e.g. [{id:'reviews',dir:-1}]. Optional.

Output parameters:

- `next_cursor` (string|null): Pass back as 'cursor' for the next page.
- `results` (array)
- `returned` (number)
- `total_matching` (number|null): Exact match count (first page only; absent on later pages).

### `export_leads` (~245 tokens)

Export leads to a destination

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' (emailed to the account owner + download link). Exports EITHER one search's leads (pass search_id) or the whole library (set all=true, capped at 1000, optionally narrowed with the same filters as query_leads). Previously exported leads are UPDATED in place (matched by Google CID) — never duplicated; the user's own CRM notes/columns are never touched.

Input parameters:

- `all` (boolean): Export the whole library instead (max 1000 leads).
- `destination` (string, required): Where the leads go.
- `filters` (array): With all=true: narrow the library using query_leads-style filter rows.
- `search_id` (string): Export this search's leads.
- `spreadsheet_id` (string): google_sheets only: add to this existing LeadMarina-created sheet instead of a new one.

Output parameters:

- `download_url` (string): File exports only: 7-day download link.
- `exported` (number): Leads sent to the destination.
- `file` (string): File exports only: the file name.
- `note` (string)
- `outcome` (string): Human-readable result, e.g. added/updated counts.

### `list_searches` (~57 tokens)

List recent searches

The account's recent searches (id, niche, location, result count, when) — use a search_id with get_search_results or export_leads.

Input parameters:

- `limit` (number): Max searches (default 10, max 25).

Output parameters:

- `searches` (array)

### `get_balance` (~18 tokens)

Get lead balance

The account's remaining monthly leads and current plan.

Output parameters:

- `leads_remaining` (number)
- `note` (string)
- `plan` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-leadmarina-leadmarina/api-mcp#diagnostics

## Score history

- 2026-08-03: 77
- 2026-08-02: 76
- 2026-08-01: 76
- 2026-07-31: 75
- 2026-07-30: 24
- 2026-07-29: 24
- 2026-07-28: 24
- 2026-07-27: 24
- 2026-07-26: 24

## Links

- Remote endpoint: https://leadmarina.com/api/mcp
- Website: https://leadmarina.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-leadmarina-leadmarina/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-leadmarina-leadmarina/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-leadmarina-leadmarina/api-mcp