PricklyMails MCP Server

by pricklymails Your server? Claim it

answering

PricklyMails is answering right now. Last checked 8 min ago.

Verify email addresses before you send: honest verdicts, no address kept, EU-hosted.

Uptime history 70 hours of history

70 hours agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

196 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

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

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add email-verification --transport http https://mcp.pricklymails.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "email-verification": {
      "url": "https://mcp.pricklymails.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.email-verification]
url = "https://mcp.pricklymails.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "email-verification": {
      "url": "https://mcp.pricklymails.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "email-verification": {
      "url": "https://mcp.pricklymails.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

URL	Transport	State	Latency	Checked
https://mcp.pricklymails.com/mcp	streamable-http	sign-in	233 ms	8 min ago

Alternatives to PricklyMails

same job, measured the same way

Easy Email Verification

by easyemailverification

Verify email addresses before you send: single, batch (50) and bulk lists (10,000).

answering

VerifyEmail

by tryverifyemail

Check whether an email address is real and will accept mail before you send to it.

answering

GBG Loqate - Reach

by gbgplc

Verify addresses, email addresses, and phone numbers with confidence scores.

11 tools answering

HonkIO

by honkio

Canadian SMS and email API for AI agents: send SMS and email, verify phones, handle CASL consent.

124 installs/wk answering

Agentboxd

by agentboxd

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

answering

Email Verifier

by pavel-tashev

Verify email addresses in bulk: syntax, domain, MX, disposable and role addresses, SPF and DMARC

answering

Skipshit

by skipshit

People and property search for Claude and ChatGPT. Phones, emails, addresses, relatives, properties.

3 tools answering

Lorem

by ryudi84

MCP server for placeholder text, fake names, emails, and addresses.

local only

PricklyMails — questions

Answers built from our own checks of this server.

Why is there no tool list for PricklyMails?

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 PricklyMails working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 196 ms. The bar chart above shows every period we have measured.

How do I connect PricklyMails?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path 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 PricklyMails?

No API key is involved. PricklyMails 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 PricklyMails?

It answers our handshake in 196 ms on average, which is faster than 63% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.