Remote MCP · Endpoint

Mergewell Mail Merge MCP server

No. Mergewell Mail Merge answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://mail-merge.zovo.one/mcp

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/mail-merge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
779 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Mail merge from Excel or CSV to PDF, right in the chat.
Listing
From the official MCP registry (active).
Recent checks of Mergewell Mail Merge
CheckedResultHandshake
44 minutes agoHandshake completed779 ms
3 days agoHandshake completed42 ms
13 days agoHandshake completed697 ms
13 days agoHandshake completed833 ms
15 days agoHandshake completed372 ms
15 days agoHandshake completed352 ms
17 days agoHandshake completed541 ms
18 days agoHandshake completed309 ms
18 days agoHandshake completed303 ms
20 days agoHandshake completed468 ms
22 days agoHandshake completed301 ms
25 days agoHandshake completed584 ms
27 days agoHandshake completed297 ms

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

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