Remote MCP · Endpoint

Samplecut MCP server

No. Samplecut answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://api.samplecut.app/mcp

The last check completed an MCP handshake.

Registry name
app.samplecut/samplecut
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
381 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Cut audio from YouTube, TikTok or Instagram links to MP3/WAV, and fetch video transcripts.
Listing
From the official MCP registry (active).
Recent checks of Samplecut
CheckedResultHandshake
44 minutes agoHandshake completed381 ms
8 days agoHandshake completed355 ms
9 days agoHandshake completed375 ms
11 days agoHandshake completed372 ms
12 days agoHandshake completed371 ms
13 days agoHandshake completed385 ms
14 days agoHandshake completed525 ms
14 days agoHandshake completed351 ms
16 days agoHandshake completed361 ms
19 days agoHandshake completed349 ms
21 days agoHandshake completed384 ms
24 days agoHandshake completed369 ms
26 days agoHandshake completed363 ms
28 days agoHandshake completed370 ms

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

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