Remote MCP · Endpoint

MailFerret MCP server

No. MailFerret answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://mailferret.appin60.com/mcp

The last check completed an MCP handshake.

Registry name
com.appin60.mailferret/mailferret
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
357 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find and verify work emails with live SMTP checks and catch-all detection. Free 10 calls/day.
Listing
From the official MCP registry (active).
Recent checks of MailFerret
CheckedResultHandshake
20 minutes agoHandshake completed357 ms
9 days agoHandshake completed339 ms
9 days agoHandshake completed338 ms
11 days agoHandshake completed349 ms
12 days agoHandshake completed386 ms
13 days agoHandshake completed368 ms
14 days agoHandshake completed351 ms
15 days agoHandshake completed362 ms
16 days agoHandshake completed323 ms
19 days agoHandshake completed413 ms
21 days agoHandshake completed347 ms
24 days agoHandshake completed357 ms
26 days agoHandshake completed702 ms
28 days agoHandshake completed606 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 MailFerret and makes no claim about it beyond what these checks measured.