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://speedcontent.online/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
81 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 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 completed81 ms
4 days agoHandshake completed81 ms
7 days agoHandshake completed601 ms
16 days agoHandshake completed117 ms
16 days agoHandshake completed79 ms
18 days agoHandshake completed68 ms
19 days agoHandshake completed70 ms
20 days agoHandshake completed84 ms
21 days agoHandshake completed63 ms
22 days agoHandshake completed67 ms
23 days agoHandshake completed64 ms
26 days agoHandshake completed74 ms
29 days agoHandshake completed62 ms

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

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.