Email List Validation Email Verification
REMOTE · APP.EMAILLISTVALIDATION.COM
Verify emails (valid/invalid/risky/unknown): MX, SMTP, catch-all, disposable. Free agent key.
Available components
Last scanned (4 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 25 Oct 2026.
Category Marketing and SEO
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security0
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 1 Nov 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 31 Oct 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 30 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 29 Oct 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 28 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 26 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Stability: 0.50 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 25 Oct 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.
- 23 Oct 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.
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 1 Nov 2026 · Probed https://app.emaillistvalidation.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.emaillistvalidation.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| emaillistvalidation.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.emaillistvalidation.com/mcp | Unreachable | ||
| http (plaintext) | http://app.emaillistvalidation.com/mcp | Inconclusive | 404 |
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 →
estimate_cost ~116
Estimate the credit cost of a verification before running it, and whether the user can afford it. Provide either a count of emails, a list_id to re-verify, or an operation ('single'/'finder'). Always quote this before proposing anything billable.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | integer | – | Number of emails to verify (1 credit each). |
| list_id | integer | – | Estimate re-verifying an existing list by its id. |
| operation | string | – | Operation type: bulk/single (1 credit) or finder (3 credits). |
No output schema declared.
No examples provided.
explain_result ~112
Explain what a verification status or reason means in plain English, with a send recommendation. Covers valid, invalid, catch-all/accept-all, unknown, greylisted, disposable, role, free, spam-trap, abuse, do-not-mail, no-mx, disabled, and network. Use when a user asks what a result means.
| Name | Type | Req | Description |
|---|---|---|---|
| term | string | yes | The status/reason to explain, e.g. 'catch-all', 'GREYLISTED', 'unknown', 'role'. Case-insensitive. |
No output schema declared.
No examples provided.
get_api_key ~106
Get your own free API key for this server (no account needed; 25 email verifications per day). Optional: the verification tools already work without a key on a shared trial. Returns the key once — reconnect with 'Authorization: Bearer <api_key>' for your own quota and the list tools.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | Optional operator email or URL. |
| name | string | – | Your agent's name. |
| purpose | string | – | What you verify emails for. |
No output schema declared.
No examples provided.
get_batch_status ~31
Get the progress and status of a bulk verification list/job by id.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | integer | yes | – |
No output schema declared.
No examples provided.
get_credit_balance ~23
Get the current credit balance and a short usage summary for the account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_list ~36
Get the details of a single bulk verification list by its id.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | integer | yes | The id of the bulk verification list. |
No output schema declared.
No examples provided.
list_lists ~33
List the user's bulk verification lists/jobs, most recent first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of lists to return. |
No output schema declared.
No examples provided.
verify_batch ~67
Verify a batch of email addresses (up to 25 per call with an agent key). Returns per-email verdicts and saves a list. Costs 1 credit per email.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | Email addresses to verify. |
| name | string | – | Optional label for the saved list. |
No output schema declared.
No examples provided.
verify_email ~47
Verify the deliverability of a single email address. Returns a verdict (valid, invalid, risky, unknown). Costs 1 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to verify. |
No output schema declared.
No examples provided.
How do I install the Email List Validation Email Verification MCP server?
Email List Validation Email Verification is a hosted endpoint at https://app.emaillistvalidation.com/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 · app.emaillistvalidation.com
claude mcp add --transport http com-emaillistvalidation-email-verification 'https://app.emaillistvalidation.com/mcp'
What is the Email List Validation Email Verification MCP server?
Email List Validation Email Verification is an MCP server listed in the public MCP registry as com.emaillistvalidation/email-verification. Verify emails (valid/invalid/risky/unknown): MX, SMTP, catch-all, disposable. Free agent key. This page covers its hosted endpoint (https://app.emaillistvalidation.com/mcp).
Is the Email List Validation Email Verification MCP server safe to use?
Email List Validation Email Verification scores 0 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 Email List Validation Email Verification MCP server expose?
Email List Validation Email Verification exposes 9 tools: get_api_key, get_credit_balance, list_lists, get_list, explain_result, and 4 more. Their descriptions and schemas cost roughly 571 tokens of context every time the server is loaded.
Does the Email List Validation Email Verification MCP server require authentication?
Its publisher declares no required credentials for Email List Validation Email Verification. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Email List Validation Email Verification MCP server still maintained?
Email List Validation Email Verification has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.