Remote MCP · Endpoint

SocialHive MCP server

No. SocialHive answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://platform.socialhive.pro/api/mcp

The last check completed an MCP handshake.

Registry name
pro.socialhive/platform
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
577 ms
Tools exposed
24 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Social media management, multi-platform publishing, AI generation, and cross-channel analytics.
Listing
From the official MCP registry (active).
Recent checks of SocialHive
CheckedResultHandshake
1 hour agoHandshake completed577 ms
8 days agoHandshake completed151 ms
9 days agoHandshake completed166 ms
11 days agoHandshake completed146 ms
12 days agoHandshake completed140 ms
12 days agoHandshake completed182 ms
14 days agoHandshake completed152 ms
14 days agoHandshake completed629 ms
16 days agoHandshake completed222 ms
19 days agoHandshake completed169 ms
21 days agoHandshake completed150 ms
24 days agoHandshake completed177 ms
26 days agoHandshake completed153 ms
28 days agoHandshake completed166 ms

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

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