Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Qualisend Email Verification

REMOTE · APP.QUALISEND.COM · SCANNED AUG 15

Verify email addresses and clean lists to improve deliverability and sender reputation.

74 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1339 tokens (~111/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 Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · app.qualisend.com

# add to Claude Code
claude mcp add --transport http com-qualisend-email-verification https://app.qualisend.com/api/mcp
# ~/.codex/config.toml
[mcp_servers.com-qualisend-email-verification]
url = "https://app.qualisend.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-qualisend-email-verification": {
      "type": "remote",
      "url": "https://app.qualisend.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-qualisend-email-verification --url https://app.qualisend.com/api/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-qualisend-email-verification:
    url: "https://app.qualisend.com/api/mcp"
// mcp.json
{
  "mcpServers": {
    "com-qualisend-email-verification": {
      "type": "http",
      "url": "https://app.qualisend.com/api/mcp"
    }
  }
}

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

Changelog

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.

  • 15 Aug 26 +8
    • Authorization: unverified → partial security
    • Stability: unverified → 0.03 functional
  • 14 Aug 26 66

    First indexed and scored.

Diagnostics

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 15 Aug 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=YR2,O=Let's Encrypt,C=US 16 Jul 2026 14 Oct 2026 RSA 2048 SHA256-RSA 511bc811f142d7eea8cf42c82b16aef97f1
SANs: app.qualisend.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
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
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=()
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
MCP tools · 12 exposed · ~1,149 tokens

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.

Tool Tokens
analyze_email_header ~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.

NameTypeReqDescription
rawstringyesThe raw email headers (paste the message source).

No output schema declared.

No examples provided.

check_blacklist ~88

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.

NameTypeReqDescription
targetstringyesA domain (acme.com) or an IPv4 address.

No output schema declared.

No examples provided.

check_disposable ~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.

NameTypeReqDescription
emailstringyesThe email address to check.

No output schema declared.

No examples provided.

check_domain ~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.

NameTypeReqDescription
domainstringyesThe domain to check, e.g. acme.com.

No output schema declared.

No examples provided.

check_typo ~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.

NameTypeReqDescription
emailstringyesThe email address to check for a typo.

No output schema declared.

No examples provided.

generate_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.

NameTypeReqDescription
allstringSPF: how strict to be with everyone else (default ~all).
authorityUrlstringBIMI: https link to the VMC certificate.
domainstringyesThe domain the record is for.
includesarraySPF: services allowed to send (e.g. _spf.google.com).
ip4arraySPF: allowed IPv4 addresses/ranges.
ip6arraySPF: allowed IPv6 addresses/ranges.
logoUrlstringBIMI: https link to the brand's SVG logo.
modestringMTA-STS: policy mode (default testing).
mxHostsarrayMTA-STS: the domain's mail-server hostnames.
pctnumberDMARC: percent of mail the policy applies to.
policystringDMARC: what to do with mail that fails checks.
ruastringDMARC: email to receive summary reports.
rufstringDMARC: email to receive detailed failure reports.
typestringyesWhich record to create.

No output schema declared.

No examples provided.

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 ~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.

NameTypeReqDescription
job_idstringyesThe job_id returned by a verify tool.

No output schema declared.

No examples provided.

lookup_smtp_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.

NameTypeReqDescription
codestringyesThe SMTP code, e.g. 550 or 5.1.1.

No output schema declared.

No examples provided.

verify_email ~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.

NameTypeReqDescription
emailstringyesThe email address to verify.

No output schema declared.

No examples provided.

verify_emails ~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.

NameTypeReqDescription
emailsarrayyesEmail addresses to verify (1–50).

No output schema declared.

No examples provided.

verify_list ~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.

NameTypeReqDescription
emailsarrayyesEmail addresses to verify (1–1000).

No output schema declared.

No examples provided.