How do I install MAILTYPE — Email Domain Capability Intelligence?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does MAILTYPE — Email Domain Capability Intelligence need an API key?

No required environment variable is listed on this record.

What transport does MAILTYPE — Email Domain Capability Intelligence use?

MAILTYPE — Email Domain Capability Intelligence is reached over HTTP.

When was MAILTYPE — Email Domain Capability Intelligence last checked?

Last checked 2026-11-09. Email-domain intelligence: MX capability, provider, disposable status, SPF, DMARC, and MTA-STS.

MAILTYPE — Email Domain Capability Intellige MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://mailtype-api.onrender.com/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http io.github.gsterlingpress-mailtype https://mailtype-api.onrender.com/mcp

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.gsterlingpress-mailtype": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://mailtype-api.onrender.com/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 1.0.2
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

MAILTYPE

Email/domain → objective mail capability intelligence.

MAILTYPE is a tiny REST + MCP API for applications that need fast, objective domain-level email infrastructure answers before accepting, storing, routing, or acting on an email address.

Live API: https://mailtype-api.onrender.com/docs
OpenAPI: https://mailtype-api.onrender.com/openapi.json
Playground: https://mailtype-api.onrender.com/play?q=gmail.com
MCP endpoint: https://mailtype-api.onrender.com/mcp

What it returns

DOMAIN_EXISTS
CAN_RECEIVE_MAIL
MX records and provider
disposable-domain evidence
SPF
DMARC
MTA-STS
confidence, evidence, and checked_at

Why MAILTYPE

MAILTYPE deliberately does not perform SMTP probing or claim that an individual mailbox exists. It answers the cheaper, objective domain-level questions that software often needs first. UNKNOWN is a valid answer whenever the evidence is insufficient.

REST

curl -H "X-API-Key: YOUR_KEY" \
  https://mailtype-api.onrender.com/v1/domain/gmail.com

curl -H "X-API-Key: YOUR_KEY" \
  https://mailtype-api.onrender.com/v1/email/[email protected]

MCP

Endpoint: POST https://mailtype-api.onrender.com/mcp

Tool: inspect_mail_domain

Input:

{"input":"gmail.com"}

Public discovery endpoints

Docs: https://mailtype-api.onrender.com/docs
Playground: https://mailtype-api.onrender.com/play?q=gmail.com
OpenAPI 3.1: https://mailtype-api.onrender.com/openapi.json
Sources and methodology: https://mailtype-api.onrender.com/sources
Health: https://mailtype-api.onrender.com/health

Data and standards

MAILTYPE uses DNS evidence plus a maintained legally reusable disposable-domain dataset. The API exposes its methodology and source disclosure publicly. Relevant standards include RFC 5321, RFC 7505 (Null MX), RFC 7208 (SPF), RFC 7489 (DMARC), and RFC 8461 (MTA-STS).

Hard boundary

MAILTYPE does not verify that a mailbox exists, connect to recipient SMTP servers, send email, infer deliverability from opaque scores, or claim CAN_RECEIVE_MAIL=YES without explicit MX evidence. If a domain exists but explicit MX evidence is insufficient, MAILTYPE returns UNKNOWN.

Stranger Verification Standard

Our own tests, health probes, validators, uptime traffic, and known internal callers do not count as adoption. A tool call alone does not automatically become a verified stranger; outside calls remain unverified until evidence supports credible real use.

Keywords

email API · domain API · MX lookup API · disposable email domain API · SPF API · DMARC API · MTA-STS API · email infrastructure · email validation preflight · MCP server · developer API

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install MAILTYPE — Email Domain Capability Intelligence?

Does MAILTYPE — Email Domain Capability Intelligence need an API key?

What transport does MAILTYPE — Email Domain Capability Intelligence use?

When was MAILTYPE — Email Domain Capability Intelligence last checked?

Documentation

MAILTYPE

What it returns

Why MAILTYPE

REST

MCP

Public discovery endpoints

Data and standards

Hard boundary

Stranger Verification Standard

Keywords