ai.kaiv/email-check

Est-ce que ai.kaiv/email-check est sûr ?

Au dernier audit MCP Hub, le serveur MCP « ai.kaiv/email-check » 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 4 outils

• check_email_domain≈ 901 tokens

  Full email posture for a domain: can it receive mail, and can it be spoofed? Runs MX, SPF and DMARC lookups together and returns a plain-language verdict alongside the raw records: can_receive_mail, spoofable, and a list of specific findings. Use this as the default check before emailing an unfamiliar domain, when judging whether inbound mail claiming to be from a domain could be forged, or when auditing your own domains. Prefer this over the single-record tools unless you already know which record you need.

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis
    Domain to check, e.g. "example.com". A full email address is accepted and the domain is taken from it.

  Exemple d'appel

  {"name": "check_email_domain", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"mx": {}, "spf": {}, "dmarc": {}, "domain": "texte", "summary": "texte", "findings": [], "spoofable": true, "checked_at": "texte", "can_receive_mail": true}}

• get_dmarc_record≈ 472 tokens

  DMARC record, policy, and whether it actually protects. Returns the DMARC TXT record at _dmarc.<domain>, its policy (none / quarantine / reject), the percentage it applies to, and whether that policy protects against spoofing. Also flags the case of MULTIPLE DMARC records, which RFC 7489 requires receivers to treat as no policy at all — a domain in that state is unprotected however strict its records look. A policy of "none" is monitoring only and does not stop forged mail. Use when assessing whether mail claiming to be from a domain can be trusted.

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis
    Domain to check, e.g. "example.com". A full email address is accepted and the domain is taken from it.

  Exemple d'appel

  {"name": "get_dmarc_record", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"found": true, "domain": "texte", "policy": "none", "record": "texte", "meaning": "texte", "percent": 1, "protects": true, "all_records": [], "multiple_records": true}}

• get_mx_records≈ 314 tokens

  Mail exchanger records for a domain. Returns the MX hosts in priority order and whether any exist. A domain with no MX records cannot receive mail, so sending to it will bounce. Use when you only need deliverability and not spoofing posture; use check_email_domain for the full picture.

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis
    Domain to check, e.g. "example.com". A full email address is accepted and the domain is taken from it.

  Exemple d'appel

  {"name": "get_mx_records", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"found": true, "hosts": [], "domain": "texte", "can_receive_mail": true}}

• get_spf_record≈ 385 tokens

  SPF record and how strict it is. Returns the SPF TXT record, the qualifier on its `all` mechanism (fail / softfail / neutral / pass) and what that means in practice, plus whether more than one SPF record exists — which receivers treat as an error, leaving the domain unprotected. Use when diagnosing why mail from a domain is being rejected or marked.

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis
    Domain to check, e.g. "example.com". A full email address is accepted and the domain is taken from it.

  Exemple d'appel

  {"name": "get_spf_record", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"found": true, "domain": "texte", "record": "texte", "strict": true, "meaning": "texte", "qualifier": "fail", "multiple_records": true}}

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é ».

Créer un compte / revendiquer →

Source

https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250