Remote MCP · Endpoint

PostLaunchKit MCP server

No. PostLaunchKit answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://postlaunchkit.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.teamhandyapps-oss/postlaunchkit
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
154 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Search reviewed free tools, submit for review, run launch checks, and find launch directories.
Listing
From the official MCP registry (active).
Recent checks of PostLaunchKit
CheckedResultHandshake
1 hour agoHandshake completed154 ms
1 day agoHandshake completed145 ms
2 days agoHandshake completed213 ms
2 days agoHandshake completed160 ms
4 days agoHandshake completed358 ms
7 days agoHandshake completed162 ms
9 days agoHandshake completed186 ms
12 days agoHandshake completed145 ms
14 days agoHandshake completed176 ms
16 days agoHandshake completed168 ms
18 days agoHandshake completed188 ms
20 days agoHandshake completed175 ms
22 days agoHandshake completed167 ms
24 days agoHandshake completed123 ms
25 days agoHandshake completed201 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 PostLaunchKit and makes no claim about it beyond what these checks measured.