Remote MCP · Endpoint

WhichPost MCP server

No. WhichPost answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://whichpost.app/mcp

The last check completed an MCP handshake.

Registry name
app.whichpost/whichpost
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.10 s
Tools exposed
18 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Which creator posts brought paying customers: your WhichPost reports, with ranges.
Listing
From the official MCP registry (active).
Recent checks of WhichPost
CheckedResultHandshake
8 hours agoHandshake completed1.10 s
10 days agoHandshake completed111 ms
11 days agoHandshake completed213 ms
11 days agoHandshake completed112 ms
13 days agoHandshake completed116 ms
15 days agoHandshake completed126 ms
15 days agoHandshake completed103 ms
16 days agoHandshake completed226 ms
17 days agoHandshake completed114 ms
19 days agoHandshake completed104 ms
22 days agoHandshake completed108 ms
24 days agoHandshake completed101 ms
26 days agoHandshake completed131 ms
29 days agoHandshake completed94 ms

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

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