Remote MCP · Endpoint

SpeedContent Social MCP server

No. SpeedContent Social answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://generatecontentwithaiservice-g5zrtckfda-ue.a.run.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.seotrader/speedcontent-social
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
89 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Generate platform-native social posts that are humanized, AI-detection scored and illustrated.
Listing
From the official MCP registry (active).
Recent checks of SpeedContent Social
CheckedResultHandshake
1 hour agoHandshake completed89 ms
2 days agoHandshake completed108 ms
5 days agoHandshake completed101 ms
7 days agoHandshake completed95 ms
9 days agoHandshake completed47 ms
11 days agoHandshake completed108 ms
13 days agoHandshake completed40 ms
15 days agoHandshake completed216 ms
17 days agoHandshake completed98 ms
18 days agoHandshake completed97 ms
19 days agoHandshake completed97 ms
20 days agoHandshake completed95 ms
23 days agoHandshake completed98 ms
25 days agoHandshake completed96 ms

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

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