Remote MCP · Endpoint

Decks MCP server

No. Decks answered an MCP handshake 42 minutes ago.

Up · key neededLast checked 42 minutes ago

Server URL

https://decks.worker.mymarketing.click/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
click.mymarketing/decks
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
523 ms
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
AI presentations in your brand from a prompt, text or file; present by link, export PDF and PPTX
Listing
From the official MCP registry (active).
Recent checks of Decks
CheckedResultHandshake
42 minutes agoHandshake completed523 ms
3 days agoHandshake completed93 ms
12 days agoHandshake completed115 ms
12 days agoHandshake completed564 ms
14 days agoHandshake completed327 ms
15 days agoHandshake completed466 ms
16 days agoHandshake completed503 ms
17 days agoHandshake completed95 ms
18 days agoHandshake completed549 ms
19 days agoHandshake completed115 ms
22 days agoHandshake completed124 ms
25 days agoHandshake completed87 ms
27 days agoHandshake completed976 ms

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

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