Email Check

ai.kaivPublished by kaiv.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Turn any OpenAPI/Swagger spec or REST API docs link into a managed MCP server. Free account.

The publisher's own server: Kaiva Bridge

VerifiedStreamable HTTPWeb executableCommunication & CollaborationSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that lets an assistant check a domain's email setup: MX deliverability, SPF, and DMARC spoofing posture.

What you can do
  • Run a full email posture check on a domain, combining deliverability and spoofability into a plain-language verdict with raw records
  • Look up MX records in priority order and see whether the domain can receive mail at all
  • Retrieve the SPF record, its all-mechanism qualifier, and whether duplicate SPF records exist
  • Retrieve the DMARC record, its policy and percentage, whether it protects against spoofing, and flag multiple DMARC records
When to use it
Useful before emailing an unfamiliar domain, when validating signup or contact addresses, or when diagnosing why mail bounces or a domain can be spoofed. Good for quick DNS-based email hygiene checks without leaving the assistant.
Requirements
A remote streamable HTTP endpoint at api.kaiv.ai; no packages, environment variables, headers, or authentication are declared. The registry description mentions a free account, but no credential mechanism is specified. Network access to the endpoint is required.
Before you install
The registry description advertises turning OpenAPI specs into MCP servers, which does not match the email-check tools listed, so verify what the endpoint actually exposes. Queries reveal which domains you are investigating to a third-party service. Results are DNS-based and can be stale or incomplete.

Installation

In SourceWeft

  1. Open Email Check in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.kaiv%2Femail-check/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "email-check": {
      "type": "http",
      "url": "https://api.kaiv.ai/api/bridge/mcp/email-check-b6ab5250"
    }
  }
}

Tools

4

check_email_domain

Check Email Domain

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.

Parametersdomainrequired

get_dmarc_record

Get Dmarc Record

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.

Parametersdomainrequired

get_mx_records

Get Mx Records

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.

Parametersdomainrequired

get_spf_record

Get Spf Record

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.

Parametersdomainrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Kaiv integrations