Remote MCP · Endpoint

Magic Envelope MCP server

No. Magic Envelope answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://magic-envelope.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.magic-envelope/invitations
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
104 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Create and send invitations and letters in a sealed envelope, one personal link per guest.
Listing
From the official MCP registry (active).
Recent checks of Magic Envelope
CheckedResultHandshake
6 hours agoHandshake completed104 ms
3 days agoHandshake completed232 ms
12 days agoHandshake completed78 ms
13 days agoHandshake completed67 ms
14 days agoHandshake completed1.28 s
15 days agoHandshake completed78 ms
16 days agoHandshake completed129 ms
17 days agoHandshake completed102 ms
18 days agoHandshake completed66 ms
20 days agoHandshake completed64 ms
22 days agoHandshake completed80 ms
25 days agoHandshake completed117 ms
27 days agoHandshake completed75 ms
29 days agoHandshake completed96 ms

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

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 Magic Envelope and makes no claim about it beyond what these checks measured.