Remote MCP · Endpoint

Postlia MCP server

No. Postlia answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://postlia.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.postlia/postlia
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
161 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Schedule and publish social posts to 7 networks from AI agents. Postlia API key (Pro) required.
Listing
From the official MCP registry (active).
Recent checks of Postlia
CheckedResultHandshake
1 hour agoHandshake completed161 ms
2 days agoHandshake completed889 ms
4 days agoHandshake completed170 ms
5 days agoHandshake completed876 ms
7 days agoHandshake completed151 ms
8 days agoHandshake completed149 ms
9 days agoHandshake completed162 ms
12 days agoHandshake completed1.29 s
13 days agoHandshake completed153 ms
15 days agoHandshake completed160 ms
16 days agoHandshake completed160 ms
17 days agoHandshake completed170 ms
18 days agoHandshake completed168 ms
19 days agoHandshake completed156 ms
20 days agoHandshake completed165 ms
21 days agoHandshake completed160 ms
22 days agoHandshake completed163 ms

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

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