Remote MCP · Endpoint

BetterPost MCP server

No. BetterPost answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://betterpost.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.betterpost/server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
107 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Finds timely sources across news, social, and the web and writes posts worth publishing.
Listing
From the official MCP registry (active).
Recent checks of BetterPost
CheckedResultHandshake
10 hours agoHandshake completed107 ms
2 days agoHandshake completed117 ms
4 days agoHandshake completed91 ms
5 days agoHandshake completed88 ms
7 days agoHandshake completed145 ms
8 days agoHandshake completed87 ms
9 days agoHandshake completed89 ms
12 days agoHandshake completed111 ms
13 days agoHandshake completed82 ms
15 days agoHandshake completed97 ms
16 days agoHandshake completed110 ms
17 days agoHandshake completed82 ms
18 days agoHandshake completed91 ms
19 days agoHandshake completed75 ms
20 days agoHandshake completed109 ms
21 days agoHandshake completed81 ms
23 days agoHandshake completed97 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 BetterPost and makes no claim about it beyond what these checks measured.