Remote MCP · Endpoint

PostalForm MCP server

No. PostalForm answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://postalform.com/mcp

The last check completed an MCP handshake.

Registry name
com.postalform/postalform
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
97 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Create mail drafts, upload PDFs, browse forms, track orders, and pay via MPP or x402.
Listing
From the official MCP registry (active).
Recent checks of PostalForm
CheckedResultHandshake
2 hours agoHandshake completed97 ms
2 days agoHandshake completed124 ms
4 days agoHandshake completed88 ms
6 days agoHandshake completed543 ms
8 days agoHandshake completed103 ms
10 days agoHandshake completed103 ms
12 days agoHandshake completed48 ms
13 days agoHandshake completed289 ms
14 days agoHandshake completed612 ms
16 days agoHandshake completed49 ms
18 days agoHandshake completed65 ms
20 days agoHandshake completed47 ms
21 days agoHandshake completed47 ms
23 days agoHandshake completed59 ms
24 days agoHandshake completed60 ms

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

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