Remote MCP · Endpoint

Clypmint MCP server

No. Clypmint answered an MCP handshake 4 hours ago.

UpLast checked 4 hours 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
74 ms
Tools exposed
45 tools
Uptime, last 30 days
100% from 13 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.
Website
https://clypmint.com/developers
Listing
From the official MCP registry (active).
Recent checks of Clypmint
CheckedResultHandshake
4 hours agoHandshake completed74 ms
2 days agoHandshake completed67 ms
5 days agoHandshake completed72 ms
7 days agoHandshake completed259 ms
9 days agoHandshake completed87 ms
11 days agoHandshake completed72 ms
13 days agoHandshake completed81 ms
15 days agoHandshake completed77 ms
17 days agoHandshake completed64 ms
18 days agoHandshake completed75 ms
20 days agoHandshake completed64 ms
21 days agoHandshake completed64 ms
23 days agoHandshake completed77 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.

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