Remote MCP · Endpoint

3LT Mail & Fax MCP server

No. 3LT Mail & Fax answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://3lgrouptechnology.com/mcp

The last check completed an MCP handshake.

Registry name
com.3lgrouptechnology/3lt-letter-mail
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
335 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Letters + faxes for AI assistants in one MCP service. Letters from $1.97 all-in; faxes from $0.57.
Listing
From the official MCP registry (active).
Recent checks of 3LT Mail & Fax
CheckedResultHandshake
44 minutes agoHandshake completed335 ms
3 days agoHandshake completed331 ms
13 days agoHandshake completed338 ms
13 days agoHandshake completed334 ms
15 days agoHandshake completed339 ms
15 days agoHandshake completed339 ms
17 days agoHandshake completed339 ms
18 days agoHandshake completed335 ms
18 days agoHandshake completed458 ms
20 days agoHandshake completed340 ms
22 days agoHandshake completed371 ms
25 days agoHandshake completed373 ms
27 days agoHandshake completed345 ms
29 days agoHandshake completed375 ms

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

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 3LT Mail & Fax and makes no claim about it beyond what these checks measured.