Productivity · Remote MCP server
MAILTYPE — Email Domain Capability Intelligence
Email-domain intelligence: MX capability, provider, disposable status, SPF, DMARC, and MTA-STS.
Visit MAILTYPE — Email Domain Capability Intelligence's website
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.GSterlingPress/mailtype- Version
- 1.0.2
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-09-13
- Updated
- 2026-09-13
- Publisher
- GSterlingPress (GitHub) · 6 servers with pages here
- Listed under
- Email MCP servers
- Website
- mailtype-api.onrender.com/docs
- Repository
- github.com/GSterlingPress/mailtype-api
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mailtype-api.onrender.com/mcp | X-API-Key (required, secret) |
How to connect MAILTYPE — Email Domain Capability Intelligence
MAILTYPE — Email Domain Capability Intelligence is a remote MCP server: there is nothing to install. Its endpoint is https://mailtype-api.onrender.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: X-API-Key (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from GSterlingPress (GitHub)
| Server | Runs |
|---|---|
| FRESH — Shared URL Freshness IntelligenceDecide whether an agent should reuse cached URL knowledge or fetch the resource again. | Remote · HTTP |
| ONCE — Exactly-Once Reliability for AI Agent ActionsPrevent duplicate AI-agent side effects with idempotency, verification, and durable receipts. | Remote · HTTP |
| POSTFACT — Resolve Ambiguous Side Effects Before RetryResolve whether an uncertain side-effecting action completed before software retries it. | Remote · HTTP |
| PREFLIGHT — URL Routing for AI AgentsChoose HTTP, browser, machine endpoint, or avoid before an agent visits an unfamiliar URL. | Remote · HTTP |
| RECOVER — Decide Safely After a Failed Machine ActionChoose the safest next action after an API, MCP, or agent failure before retrying. | Remote · HTTP |
More productivity servers
| Server | Runs |
|---|---|
| MailsinkDisposable inboxes for AI agents and CI: catch the verification email, read the OTP or link. | Local · stdio |
| mailsocketEmail inboxes for AI agents: create an inbox, then block until the OTP or magic link arrives. | Remote & Local · HTTP, stdio |
| MailteaSend email and newsletters with Mailtea over MCP, plus skills for email and website design. | Remote · HTTP |
| MailtrapSend emails and manage sending domains, suppression lists, and delivery analytics. | Local · stdio |
| MailVaktUse when email lands in spam: audits SPF, DKIM, DMARC, MX and returns the DNS records to fix it. | Remote · HTTP |
| mailverdictKeyless email checks: disposable, role, and free-provider detection, MX, and typo suggestions. | Remote · HTTP |
| Mailvett: Email Validation API for AI AgentsMailvett: validate emails. MX, provider, disposable/role/free flags, typo fix, verdict. | Remote · HTTP |
| Mailvett: Email Validation API for AI AgentsMailvett: validate emails. MX, provider, disposable/role/free flags, typo fix, verdict. | Remote · HTTP |