Remote MCP · Endpoint

convert.express MCP server

No. convert.express answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://convert.express/mcp

The last check completed an MCP handshake.

Registry name
express.convert/transcribe
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
319 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Transcribe audio and video to text, SRT or VTT. Summaries, translation. Optional OAuth sign-in.
Listing
From the official MCP registry (active).
Recent checks of convert.express
CheckedResultHandshake
1 hour agoHandshake completed319 ms
9 days agoHandshake completed308 ms
9 days agoHandshake completed312 ms
11 days agoHandshake completed368 ms
12 days agoHandshake completed389 ms
13 days agoHandshake completed319 ms
14 days agoHandshake completed305 ms
14 days agoHandshake completed322 ms
16 days agoHandshake completed311 ms
19 days agoHandshake completed313 ms
21 days agoHandshake completed304 ms
24 days agoHandshake completed315 ms
26 days agoHandshake completed309 ms
28 days agoHandshake completed304 ms

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

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