# com.qualisend/email-verification

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.0
- **Author:** com.qualisend
- **License:** Unknown
- **Endpoints:** streamable-http https://app.qualisend.com/api/mcp
- **Source:** https://app.qualisend.com
- **Endpoint health:** reachable (last checked 2026-09-25T21:50:06.185Z, 5 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 9 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-25T21:50:06.185Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

12 declared. Observed from a live `tools/list` probe.
- `verify_email` — Verify a single email address - syntax, domain/MX, disposable + role detection, typo suggestion, and mailbox reachability. Returns a deliverability verdict (del
- `verify_emails` — 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), 
- `verify_list` — 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 i
- `get_credit_balance` — Return the number of verification credits available in your Qualisend workspace.
- `get_verification` — 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 verdi
- `check_domain` — 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 pla
- `generate_dns_record` — 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, wit
- `analyze_email_header` — 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 chec
- `check_disposable` — 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 
- `check_typo` — 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. Availa
- `lookup_smtp_code` — 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. Ava
- `check_blacklist` — 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

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"email-verification\": {\n      \"type\": \"http\",\n      \"url\": \"https://app.qualisend.com/api/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/com.qualisend%2Femail-verification
- Install plan: https://forgeregistry.com/api/v1/packages/com.qualisend%2Femail-verification/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/com.qualisend%2Femail-verification
- HTML page: https://forgeregistry.com/registry/com.qualisend%2Femail-verification
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.