Remote MCP · Endpoint

Moonscroll MCP server

No. Moonscroll answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://api.moonscroll.ai/mcp

The last check completed an MCP handshake.

Registry name
io.github.thefedoration/moonscroll
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
222 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Short Form Video Insights for Instagram, TikTok, Shorts
Listing
From the official MCP registry (active).
Recent checks of Moonscroll
CheckedResultHandshake
43 minutes agoHandshake completed222 ms
3 days agoHandshake completed188 ms
12 days agoHandshake completed304 ms
13 days agoHandshake completed149 ms
14 days agoHandshake completed363 ms
15 days agoHandshake completed314 ms
16 days agoHandshake completed314 ms
17 days agoHandshake completed357 ms
18 days agoHandshake completed284 ms
19 days agoHandshake completed511 ms
22 days agoHandshake completed328 ms
25 days agoHandshake completed282 ms
27 days agoHandshake completed195 ms
29 days agoHandshake completed492 ms

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