Remote MCP · Endpoint

SocialSeal MCP server

No. SocialSeal answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://mcp.socialseal.co/mcp

The last check completed an MCP handshake.

Registry name
com.socialseal/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
397 ms
Tools exposed
116 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Measure how findable a brand is in TikTok, Instagram, YouTube and AI search, and what to post next.
Listing
From the official MCP registry (active).
Recent checks of SocialSeal
CheckedResultHandshake
20 minutes agoHandshake completed397 ms
9 days agoHandshake completed470 ms
9 days agoHandshake completed131 ms
11 days agoHandshake completed108 ms
12 days agoHandshake completed363 ms
13 days agoHandshake completed388 ms
14 days agoHandshake completed259 ms
15 days agoHandshake completed222 ms
16 days agoHandshake completed270 ms
19 days agoHandshake completed257 ms
21 days agoHandshake completed279 ms
24 days agoHandshake completed401 ms
26 days agoHandshake completed570 ms
28 days agoHandshake completed105 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 SocialSeal and makes no claim about it beyond what these checks measured.