mcpbeat Sign in

mailfloss MCP Server

by mailfloss Your server? Claim it
answering

mailfloss is answering right now. Last checked 9 min ago.

Email verification for AI agents: verify addresses and lists, check credits, manage integrations.

Uptime history 12 days of history · worst day 98%
12 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
753 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check mailfloss every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add mailfloss --transport http https://api.mailfloss.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.mailfloss.com/mcp
~/.codex/config.toml
[mcp_servers.mailfloss]
url = "https://api.mailfloss.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mailfloss": {
      "url": "https://api.mailfloss.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mailfloss": {
      "type": "http",
      "url": "https://api.mailfloss.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://api.mailfloss.com/mcp streamable-http sign-in 674 ms 9 min ago

Alternatives to mailfloss

same job, measured the same way
ListCheckup
by listcheckup

Email verification for AI agents: check addresses and lists, priced before credits are spent.

answering
Agentboxd
by agentboxd

Real email inboxes for AI agents: create addresses, send, wait for mail and verification codes.

answering
BillionVerify
by billionverify

Email verification for AI agents: verify single or bulk emails, check credits and history.

39 installs/wk 11 tools answering
Verifai — Email Verification & Domain Intelligence
by zikriz

Email verification and domain intelligence for AI agents. MX, RDAP, SSL checks. 25 free credits.

7 tools answering
ClearBounce Email Verification
by clearbounce

Verify email addresses in real time and find business email addresses with live mailbox checks.

6 tools answering
Agenticmail
by agenticmail

Real email and SMS for AI agents — send mail, receive verification codes, drive a real inbox.

357 installs/wk local only
Mailfornet
by mailfornet

Disposable email inboxes for AI agents: create an address, wait for the OTP or verify link.

answering
SMTPing Email Verification
by smtping

Verify email addresses, clean lists and check spamtrap, disposable, spambot and complainer lists.

272 installs/wk answering

mailfloss — questions

Answers built from our own checks of this server.

Why is there no tool list for mailfloss?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is mailfloss working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 753 ms. The bar chart above shows every period we have measured.
How do I connect mailfloss?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to mailfloss?
No API key is involved. mailfloss answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is mailfloss?
It answers our handshake in 753 ms on average, which is faster than 11% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.