Remote MCP · Endpoint

Clypmint MCP server

No. Clypmint answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://clypmint.com/mcp

The last check completed an MCP handshake.

Registry name
com.clypmint/clypmint
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
90 ms
Tools exposed
63 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Edit videos with AI: cuts, captions, B-roll and motion in a style you pick or copy from any video.
Listing
From the official MCP registry (active).
Recent checks of Clypmint
CheckedResultHandshake
44 minutes agoHandshake completed90 ms
3 days agoHandshake completed74 ms
13 days agoHandshake completed85 ms
13 days agoHandshake completed134 ms
15 days agoHandshake completed132 ms
15 days agoHandshake completed95 ms
17 days agoHandshake completed66 ms
18 days agoHandshake completed71 ms
18 days agoHandshake completed88 ms
20 days agoHandshake completed75 ms
22 days agoHandshake completed74 ms
25 days agoHandshake completed67 ms
27 days agoHandshake completed72 ms
29 days agoHandshake completed259 ms

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

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