Productivity · Remote MCP server
emailverifier.dev
Verify emails and domains for routing, disposable providers, role accounts, and SMTP risk.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.usamaejaz/emailverifier- Version
- 1.0.0
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-08-26
- Updated
- 2026-08-26
- Publisher
- usamaejaz (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/usamaejaz) · how
- Listed under
- Email MCP servers
- Website
- emailverifier.dev/docs/mcp
- Repository
- github.com/usamaejaz/emailverifier.dev
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://emailverifier.dev/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect emailverifier.dev
emailverifier.dev is a remote MCP server: there is nothing to install. Its endpoint is https://emailverifier.dev/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.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. 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
Site checks
The website's own root, emailverifier.dev, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More from usamaejaz (GitHub)
| Server | Runs |
|---|---|
| JustBloggedCreate, edit, organize, publish, and configure JustBlogged blogs from MCP clients. | Remote · HTTPLive check: ✓ handshake |
More productivity servers
| Server | Runs |
|---|---|
| Emailfinder MCPFind verified professional emails by name, domain, LinkedIn, or role. | Local · stdio |
| EmailMCPAI agent email - 23 tools free to read inbox, 28 paid to send. $9.99/mo. Token auto-provisioned. | Remote · HTTPLive check: ✓ handshake |
| emailmdRender markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| eMailPlane MailEmail for AI agents: send, receive, threads, templates, domains and mailboxes on your own server. | Remote · HTTP |
| EmbossTurn any PDF form into a fillable one, fill it from data or documents, verify it, and fax it. | Remote · HTTPLive check: sign-in required |
| emergencescience MCPPost bounties, solve tasks, earn credits on Emergence Science - the agent economy. | Local · stdio |
| emprego.com job searchSearch live job openings in many countries and languages, and read a full job ad. | Remote · HTTPLive check: ✓ handshake |
| EmptyInboxZero-config disposable email inboxes for AI agents: create, read mail, await verify codes. | Local · stdio |