Remote MCP · Endpoint

Post Kit MCP server

No. Post Kit answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://postkit.openkrill.app/mcp

The last check completed an MCP handshake.

Registry name
app.openkrill/postkit
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
138 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Posts, video scripts, TikTok slide images, and a launch clip from your page.
Listing
From the official MCP registry (active).
Recent checks of Post Kit
CheckedResultHandshake
2 hours agoHandshake completed138 ms
1 day agoHandshake completed217 ms
4 days agoHandshake completed5.66 s
6 days agoHandshake completed147 ms
9 days agoHandshake completed335 ms
11 days agoHandshake completed187 ms
13 days agoHandshake completed170 ms
15 days agoHandshake completed304 ms
17 days agoHandshake completed58 ms
19 days agoHandshake completed40 ms
21 days agoHandshake completed62 ms
22 days agoHandshake completed94 ms
24 days agoHandshake completed294 ms
25 days agoHandshake completed35 ms
27 days agoHandshake completed59 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 Post Kit and makes no claim about it beyond what these checks measured.