Remote MCP · Endpoint

Postmark MCP server

No. Postmark answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/postmark/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/postmark
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
385 ms
Tools exposed
54 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Postmark MCP.
Listing
From the official MCP registry (active).
Recent checks of Postmark
CheckedResultHandshake
1 hour agoHandshake completed385 ms
1 day agoHandshake completed340 ms
2 days agoHandshake completed71 ms
3 days agoHandshake completed95 ms
4 days agoHandshake completed108 ms
5 days agoHandshake completed671 ms
6 days agoHandshake completed144 ms
9 days agoHandshake completed143 ms
12 days agoHandshake completed60 ms
14 days agoHandshake completed63 ms
16 days agoHandshake completed72 ms
18 days agoHandshake completed318 ms
21 days agoHandshake completed88 ms
23 days agoHandshake completed61 ms
25 days agoHandshake completed50 ms
26 days agoHandshake completed72 ms
28 days agoHandshake completed68 ms
29 days agoHandshake completed204 ms

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

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