Remote MCP · Endpoint

Slidler MCP server

No. Slidler answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://slidler.com/mcp

The last check completed an MCP handshake.

Registry name
com.slidler/carousel
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
432 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Turn a URL, YouTube video or text into a branded LinkedIn/Instagram carousel PDF. No key needed.
Website
https://slidler.com/
Listing
From the official MCP registry (active).
Recent checks of Slidler
CheckedResultHandshake
1 hour agoHandshake completed432 ms
8 days agoHandshake completed496 ms
9 days agoHandshake completed533 ms
11 days agoHandshake completed471 ms
12 days agoHandshake completed472 ms
13 days agoHandshake completed504 ms
14 days agoHandshake completed485 ms
14 days agoHandshake completed527 ms
16 days agoHandshake completed994 ms
19 days agoHandshake completed473 ms
21 days agoHandshake completed486 ms
24 days agoHandshake completed481 ms
26 days agoHandshake completed472 ms
28 days agoHandshake completed449 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Slidler and makes no claim about it beyond what these checks measured.