FindLeadEmails
REMOTE · WWW.FINDLEADEMAILS.COM
Find and verify B2B work emails, single or bulk. OAuth sign-in or API key; pay per verified email.
Available components
Last scanned (11 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage69
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 7% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 23 Oct 26 +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.
- 21 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://www.findleademails.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.findleademails.com | CN=YR1,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | RSA 2048 | SHA256-RSA | 6937827c024f7121a400255746bdcc3b186 |
| SANs: www.findleademails.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.findleademails.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| findleademails.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://www.findleademails.com/.well-known/oauth-protected-resource", scope="mcp"
Bearer resource_metadata="https://www.findleademails.com/.well-known/oauth-protected-resource", scope="mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Protected resource metadata
| Document | https://www.findleademails.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://www.findleademails.com/api/mcp |
| Authorisation server | https://www.findleademails.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.findleademails.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.findleademails.com/api/mcp | HTTPS enforced | 308 | https://www.findleademails.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_job Create an async bulk job ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| callback_url | – | – | – |
| name | – | – | – |
| records | array | yes | – |
No output schema declared.
No examples provided.
find_email Find one email ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company_domain | string | – | – |
| company_linkedin_url | – | – | – |
| company_name | – | – | – |
| first_name | string | yes | – |
| last_name | string | yes | – |
| linkedin_url | – | – | – |
No output schema declared.
No examples provided.
find_emails_bulk Find emails in bulk ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| records | array | yes | – |
No output schema declared.
No examples provided.
get_job_results Get a job's results ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | integer | – | – |
| job_id | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_job_status Get a job's status ~43
Read progress and per-outcome counters for a job created with create_job. Does not spend credits and does not change the job.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
verify_email Verify one email ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to check, for example jane.doe@company.com |
No output schema declared.
No examples provided.
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.
remote · www.findleademails.com
claude mcp add --transport http com-findleademails-mcp 'https://www.findleademails.com/api/mcp'
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.