# FindLeadEmails (remote · www.findleademails.com)

Find and verify B2B work emails, single or bulk. OAuth sign-in or API key; pay per verified email.

- Trust score: 85/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Endpoint: `https://www.findleademails.com/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.1.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-11-05.

- **Endpoint Security**: 97/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 supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 702 tokens (~117/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 69/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 7% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the FindLeadEmails MCP server?

FindLeadEmails is a hosted endpoint at https://www.findleademails.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-findleademails-mcp 'https://www.findleademails.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-findleademails-mcp": {
      "url": "https://www.findleademails.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-findleademails-mcp": {
      "type": "http",
      "url": "https://www.findleademails.com/api/mcp"
    }
  }
}
```

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

```json
{
  "McpServers": {
    "com-findleademails-mcp": {
      "Transport": "http",
      "Url": "https://www.findleademails.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-findleademails-mcp -t streamable-http -u 'https://www.findleademails.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-findleademails-mcp": {
      "type": "http",
      "url": "https://www.findleademails.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-11-05 (score 85, +1)

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

### 2026-11-03 (score 84, +1)

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

### 2026-11-01 (score 83, +1)

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

### 2026-10-30 (score 82, +1)

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

### 2026-10-27 (score 81, +1)

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

### 2026-10-25 (score 80, +1)

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

### 2026-10-23 (score 79, +1)

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

### 2026-10-21 (score 78, +1)

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

## MCP tools (6)

### `find_email` (~152 tokens)

Find one email

Find and verify one person's work email from their name and company domain, or from a LinkedIn company page URL when you do not have the domain. Costs 1 credit only when the result is verified. Misses, catch-alls, and cached repeats are free and still return at 0 credits. A billable result fails at 0 balance; the error includes https://www.findleademails.com/pricing. This stores the lookup. It does not delete or modify the person's data.

Input parameters:

- `company_domain` (string)
- `company_linkedin_url`
- `company_name`
- `first_name` (string, required)
- `last_name` (string, required)
- `linkedin_url`

### `verify_email` (~110 tokens)

Verify one email

Check whether one email address is a real mailbox. Costs 1 credit only when the mailbox is confirmed valid. Invalid, catch-all, unknown, and repeats are free and still return at 0 credits. A new valid mailbox fails at 0 balance; the error includes https://www.findleademails.com/pricing. The credit is spent after a valid result. This does not modify the mailbox.

Input parameters:

- `email` (string, required): The email address to check, for example jane.doe@company.com

### `find_emails_bulk` (~96 tokens)

Find emails in bulk

Find and verify emails for up to 100 people. Use create_job for a larger list. 1 credit per verified result. Free outcomes still return at 0 credits. Rows run until a billable result cannot be paid for; later rows are skipped with insufficient_credits and https://www.findleademails.com/pricing. This stores the lookups. It does not delete data.

Input parameters:

- `records` (array, required)

### `create_job` (~105 tokens)

Create an async bulk job

Queue a large list and return a job id. Reserves one credit per row up front and refunds what rows do not use. If the wallet cannot cover every row, the job is refused up front (no partial queue) with insufficient_credits and https://www.findleademails.com/pricing. Poll get_job_status, then page get_job_results. Each call creates a new job.

Input parameters:

- `callback_url`
- `name`
- `records` (array, required)

### `get_job_status` (~43 tokens)

Get a job's status

Read progress and per-outcome counters for a job created with create_job. Does not spend credits and does not change the job.

Input parameters:

- `job_id` (string, required)

### `get_job_results` (~75 tokens)

Get a job's results

Read one page of a job's per-row results. Readable while the job is still running. Pass cursor back as the next cursor until next_cursor is null. Does not spend credits and does not change the job.

Input parameters:

- `cursor` (integer)
- `job_id` (string, required)
- `limit` (integer)

## Diagnostics

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

## Score history

- 2026-11-05: 85
- 2026-11-04: 84
- 2026-11-03: 84
- 2026-11-02: 83
- 2026-11-01: 83
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 81
- 2026-10-28: 81
- 2026-10-27: 81
- 2026-10-26: 80
- 2026-10-25: 80
- 2026-10-24: 79
- 2026-10-23: 79
- 2026-10-22: 78
- 2026-10-21: 78
- 2026-10-20: 77
- 2026-10-19: 77

## Common questions

### What is the FindLeadEmails MCP server?

FindLeadEmails is an MCP server listed in the public MCP registry as com.findleademails/mcp. Find and verify B2B work emails, single or bulk. OAuth sign-in or API key; pay per verified email. This page covers its hosted endpoint (https://www.findleademails.com/api/mcp).

### Is the FindLeadEmails MCP server safe to use?

FindLeadEmails scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the FindLeadEmails MCP server expose?

FindLeadEmails exposes 6 tools: find_email, verify_email, find_emails_bulk, create_job, get_job_status, get_job_results. Their descriptions and schemas cost roughly 581 tokens of context every time the server is loaded.

### Does the FindLeadEmails MCP server require authentication?

Yes. FindLeadEmails asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the FindLeadEmails MCP server still maintained?

FindLeadEmails is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the FindLeadEmails MCP server?

VerifyMCP ran 13 checks on FindLeadEmails, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://www.findleademails.com/api/mcp
- Repository: https://github.com/findleademails/findleademails-mcp
- Website: https://www.findleademails.com/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-findleademails-mcp/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-findleademails-mcp/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-findleademails-mcp/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-findleademails-mcp/api-mcp