accueil / serveurs / Communication / com.qualisend/email-verification
com.qualisend/email-verification
serveur MCP (Model Context Protocol) · Qualisend 1.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que com.qualisend/email-verification est sûr ?
Au dernier audit MCP Hub, le serveur MCP « com.qualisend/email-verification » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 12 outils
- analyze_email_header≈ 185 tokens
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.
Paramètres, retour & exemple (1)
Paramètresraw· string · requis
The raw email headers (paste the message source).
Exemple d'appel{"name": "analyze_email_header", "arguments": {"raw": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - check_blacklist≈ 264 tokens
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.
Paramètres, retour & exemple (1)
Paramètrestarget· string · requis
A domain (acme.com) or an IPv4 address.
Exemple d'appel{"name": "check_blacklist", "arguments": {"target": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - check_disposable≈ 170 tokens
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.
Paramètres, retour & exemple (1)
Paramètresemail· string · requis
The email address to check.
Exemple d'appel{"name": "check_disposable", "arguments": {"email": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - check_domain≈ 167 tokens
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.
Paramètres, retour & exemple (1)
Paramètresdomain· string · requis
The domain to check, e.g. acme.com.
Exemple d'appel{"name": "check_domain", "arguments": {"domain": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - check_typo≈ 151 tokens
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.
Paramètres, retour & exemple (1)
Paramètresemail· string · requis
The email address to check for a typo.
Exemple d'appel{"name": "check_typo", "arguments": {"email": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - generate_dns_record≈ 528 tokens
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.
Paramètres, retour & exemple (14)
Paramètresall· string · optionnel · ~all | -all | ?all
SPF: how strict to be with everyone else (default ~all).ip4· array · optionnel
SPF: allowed IPv4 addresses/ranges.ip6· array · optionnel
SPF: allowed IPv6 addresses/ranges.pct· number · optionnel
DMARC: percent of mail the policy applies to.rua· string · optionnel
DMARC: email to receive summary reports.ruf· string · optionnel
DMARC: email to receive detailed failure reports.mode· string · optionnel · enforce | testing | none
MTA-STS: policy mode (default testing).type· string · requis · spf | dmarc | bimi | mta-sts
Which record to create.domain· string · requis
The domain the record is for.policy· string · optionnel · none | quarantine | reject
DMARC: what to do with mail that fails checks.logoUrl· string · optionnel
BIMI: https link to the brand's SVG logo.mxHosts· array · optionnel
MTA-STS: the domain's mail-server hostnames.includes· array · optionnel
SPF: services allowed to send (e.g. _spf.google.com).authorityUrl· string · optionnel
BIMI: https link to the VMC certificate.
Exemple d'appel{"name": "generate_dns_record", "arguments": {"type": "spf", "domain": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_credit_balance≈ 91 tokens
Return the number of verification credits available in your Qualisend workspace.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "get_credit_balance", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_verification≈ 164 tokens
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.
Paramètres, retour & exemple (1)
Paramètresjob_id· string · requis
The job_id returned by a verify tool.
Exemple d'appel{"name": "get_verification", "arguments": {"job_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - lookup_smtp_code≈ 151 tokens
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.
Paramètres, retour & exemple (1)
Paramètrescode· string · requis
The SMTP code, e.g. 550 or 5.1.1.
Exemple d'appel{"name": "lookup_smtp_code", "arguments": {"code": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - verify_email≈ 152 tokens
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.
Paramètres, retour & exemple (1)
Paramètresemail· string · requis
The email address to verify.
Exemple d'appel{"name": "verify_email", "arguments": {"email": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - verify_emails≈ 158 tokens
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.
Paramètres, retour & exemple (1)
Paramètresemails· array · requis
Email addresses to verify (1-50).
Exemple d'appel{"name": "verify_emails", "arguments": {"emails": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - verify_list≈ 210 tokens
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.
Paramètres, retour & exemple (1)
Paramètresemails· array · requis
Email addresses to verify (1-1000).
Exemple d'appel{"name": "verify_list", "arguments": {"emails": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».