Remote MCP · Endpoint

Weftly MCP server

No. Weftly answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://api.weftly.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.weftly/weftly
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
367 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Find & cut horizontal and vertical video clips (Shorts/Reels), transcribe & summarize. Pay per job.
Listing
From the official MCP registry (active).
Recent checks of Weftly
CheckedResultHandshake
6 hours agoHandshake completed367 ms
2 days agoHandshake completed308 ms
4 days agoHandshake completed425 ms
5 days agoHandshake completed315 ms
7 days agoHandshake completed335 ms
8 days agoHandshake completed600 ms
9 days agoHandshake completed301 ms
12 days agoHandshake completed524 ms
13 days agoHandshake completed284 ms
15 days agoHandshake completed408 ms
16 days agoHandshake completed282 ms
17 days agoHandshake completed368 ms
18 days agoHandshake completed60 ms
19 days agoHandshake completed281 ms
20 days agoHandshake completed51 ms
21 days agoHandshake completed37 ms
23 days agoHandshake completed364 ms

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

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