Remote MCP · Endpoint

Mail Security Tools MCP server

No. Mail Security Tools answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://api.mailsecuritytools.com/mcp

The last check completed an MCP handshake.

Registry name
com.mailsecuritytools.api/email-security
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
309 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
DMARC/SPF/DKIM/MX checks, email score, 100-domain bulk score, webhook watch alerts (x402 USDC).
Listing
From the official MCP registry (active).
Recent checks of Mail Security Tools
CheckedResultHandshake
13 minutes agoHandshake completed309 ms
10 days agoHandshake completed401 ms
10 days agoHandshake completed302 ms
11 days agoHandshake completed346 ms
13 days agoHandshake completed365 ms
14 days agoHandshake completed239 ms
14 days agoHandshake completed233 ms
15 days agoHandshake completed514 ms
17 days agoHandshake completed378 ms
19 days agoHandshake completed353 ms
21 days agoHandshake completed462 ms
24 days agoHandshake completed261 ms
26 days agoHandshake completed285 ms
28 days agoHandshake completed517 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Mail Security Tools and makes no claim about it beyond what these checks measured.