Qualisend Email Verification
REMOTE · APP.QUALISEND.COM
Verify email addresses and clean lists to improve deliverability and sender reputation.
Available components
Last scanned (22 minutes ago)
Scores higher than 96% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Marketing and SEO
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1413 tokens (~117/item across 12 items; 12 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 18 Sept 26 −1
- Tool “check_blacklist” rewrote its description, which is the text the model reads security
- 13 Sept 26 +1
- Stability: 0.97 → pass security
- 12 Sept 26 88
- The server rewrote its instructions, which are the text every model session reads security
- Tool “analyze_email_header” rewrote its description, which is the text the model reads security
- Tool “check_blacklist” rewrote its description, which is the text the model reads security
- Tool “check_disposable” rewrote its description, which is the text the model reads security
- Tool “check_domain” rewrote its description, which is the text the model reads security
- Tool “generate_dns_record” rewrote its description, which is the text the model reads security
- Tool “verify_email” rewrote its description, which is the text the model reads security
- “verify_emails” reworded the description of “emails” cosmetic
- “verify_list” reworded the description of “emails” cosmetic
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Aug 26 0
- Authorization: unverified → partial ▲ security
- Stability: unverified → 0.03 ▲ functional
- 14 Aug 26 0
First indexed and scored.
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 17 Oct 2026 · Probed https://app.qualisend.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=app.qualisend.com | CN=YR1,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | RSA 2048 | SHA256-RSA | 5e69beed0e0a535c3d07e1de0f9fadf4ec0 |
| SANs: app.qualisend.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 app.qualisend.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| qualisend.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.qualisend.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://app.qualisend.com/api/mcp | HTTPS enforced | 308 | https://app.qualisend.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 →
analyze_email_header Analyze an email's headers ~96
Read the hidden technical details of an email (its 'headers') to show the route it took, how long each step took, and whether it passed spam/authentication checks - handy for figuring out why a message was slow or went to spam. Paste the message source / 'Show original'. No credit used. Available on the Qualisend Pro plan.
| Name | Type | Req | Description |
|---|---|---|---|
| raw | string | yes | The raw email headers (paste the message source). |
No output schema declared.
No examples provided.
check_blacklist Check a domain or IP against email blacklists ~162
Check whether a sending domain or IP is currently on any of the major email blacklists that can push your mail to spam - a point-in-time reputation check across lists like Spamhaus, SpamCop, and Barracuda. No credit used. Requires the Qualisend Blacklist Monitoring add-on. Read the result carefully: `listed_on` are confirmed listings, while `undetermined_on` are lists that did not answer (commonly Spamhaus refusing a shared resolver). `clean` is true only when every list answered and none matched, so a non-empty `undetermined_on` means those lists are UNKNOWN - do not report them as clear or as listings.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | A domain (acme.com) or an IPv4 address. |
No output schema declared.
No examples provided.
check_disposable Check if an email is throwaway / generic / free ~77
Tell whether an email address is a throwaway/temporary one, a generic team inbox (like info@ or support@), or a free consumer address (like gmail) - useful for spotting low-quality sign-ups. No credit used. Available on the Qualisend Pro plan.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to check. |
No output schema declared.
No examples provided.
check_domain Check a domain's email setup ~82
Check whether a domain is set up to send email that reaches the inbox - its mail servers plus its SPF and DMARC sender-authentication, and what's missing. A plain deliverability health check for a sending domain. No credit used. Available on the Qualisend Pro plan.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to check, e.g. acme.com. |
No output schema declared.
No examples provided.
check_typo Suggest a fix for a mistyped email ~69
Spot a likely typo in an email's domain (like gmial.com) and suggest the correct one, so you don't lose contacts to misspelled addresses. No credit used. Available on the Qualisend Pro plan.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to check for a typo. |
No output schema declared.
No examples provided.
generate_dns_record Create an email-authentication DNS record ~306
Create the exact DNS setting a domain needs so its email is trusted and harder to spoof - SPF, DMARC, BIMI, or MTA-STS. Returns the record to copy into DNS, with where to put it. No credit used. Available on the Qualisend Pro plan.
| Name | Type | Req | Description |
|---|---|---|---|
| all | string | – | SPF: how strict to be with everyone else (default ~all). |
| authorityUrl | string | – | BIMI: https link to the VMC certificate. |
| domain | string | yes | The domain the record is for. |
| includes | array | – | SPF: services allowed to send (e.g. _spf.google.com). |
| ip4 | array | – | SPF: allowed IPv4 addresses/ranges. |
| ip6 | array | – | SPF: allowed IPv6 addresses/ranges. |
| logoUrl | string | – | BIMI: https link to the brand's SVG logo. |
| mode | string | – | MTA-STS: policy mode (default testing). |
| mxHosts | array | – | MTA-STS: the domain's mail-server hostnames. |
| pct | number | – | DMARC: percent of mail the policy applies to. |
| policy | string | – | DMARC: what to do with mail that fails checks. |
| rua | string | – | DMARC: email to receive summary reports. |
| ruf | string | – | DMARC: email to receive detailed failure reports. |
| type | string | yes | Which record to create. |
No output schema declared.
No examples provided.
get_credit_balance Get credit balance ~23
Return the number of verification credits available in your Qualisend workspace.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_verification Get a verification result ~78
Look up the status and result of a verification you started, by job_id (returned from verify_email/verify_emails). For a single check it returns the final verdict once the mailbox probe completes; for a batch it returns progress + a result-mix summary.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job_id returned by a verify tool. |
No output schema declared.
No examples provided.
lookup_smtp_code Explain a mail-server error code ~82
Explain a mail-server reply/error code (like 550 or 5.1.1) in plain English, and say whether it's a temporary hiccup or a permanent failure. No credit used. Available on the Qualisend Pro plan.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The SMTP code, e.g. 550 or 5.1.1. |
No output schema declared.
No examples provided.
verify_email Verify an email address ~69
Verify a single email address - syntax, domain/MX, disposable + role detection, typo suggestion, and mailbox reachability. Returns a deliverability verdict (deliverable / risky / undeliverable / unknown). Consumes 1 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to verify. |
No output schema declared.
No examples provided.
verify_emails Verify a batch of email addresses ~67
Verify up to 50 email addresses at once and get a deliverability verdict for each, synchronously. Consumes 1 credit per address. For larger lists (up to 1000), use verify_list.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | Email addresses to verify (1-50). |
No output schema declared.
No examples provided.
verify_list Verify a large list of email addresses ~112
Verify a large list of up to 1000 email addresses. This runs ASYNCHRONOUSLY: it creates ONE bulk job, returns a job_id immediately, and the mailbox probes run in the background. Poll get_verification with the job_id for progress and a result summary (counts by verdict). Consumes 1 credit per address. For lists larger than 1000, use the Qualisend dashboard or bulk API.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | Email addresses to verify (1-1000). |
No output schema declared.
No examples provided.
How do I install the Qualisend Email Verification MCP server?
Qualisend Email Verification is a hosted endpoint at https://app.qualisend.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 · app.qualisend.com
claude mcp add --transport http com-qualisend-email-verification 'https://app.qualisend.com/api/mcp'
What is the Qualisend Email Verification MCP server?
Qualisend Email Verification is an MCP server listed in the public MCP registry as com.qualisend/email-verification. Verify email addresses and clean lists to improve deliverability and sender reputation. This page covers its hosted endpoint (https://app.qualisend.com/api/mcp).
Is the Qualisend Email Verification MCP server safe to use?
Qualisend Email Verification scores 88 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 Qualisend Email Verification MCP server expose?
Qualisend Email Verification exposes 12 tools: verify_email, verify_emails, verify_list, get_credit_balance, get_verification, and 7 more. Their descriptions and schemas cost roughly 1,223 tokens of context every time the server is loaded.
Does the Qualisend Email Verification MCP server require authentication?
No. We connected to Qualisend Email Verification without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Qualisend Email Verification MCP server still maintained?
Qualisend Email Verification is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.