Remote MCP · Endpoint

MP4.now MCP Server MCP server

No. MP4.now MCP Server answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://mp4.now/mcp

The last check completed an MCP handshake.

Registry name
io.github.chrisyau83/mp4-now
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
95 ms
Tools exposed
4 tools
Uptime, last 30 days
45.5% from 11 checks
Described by its publisher as
Convert MP4 video with MP3, WebM, MOV, AVI, GIF, WAV, JPG and MKV workflows.
Listing
From the official MCP registry (active).
Recent checks of MP4.now MCP Server
CheckedResultHandshake
34 minutes agoHandshake completed95 ms
3 days agoHandshake completed82 ms
13 days agoHandshake completed91 ms
13 days agoHandshake completed119 ms
15 days agoFailed - the request timed out—
16 days agoFailed - the request timed out—
17 days agoFailed - the request timed out—
18 days agoHandshake completed130 ms
18 days agoFailed - the request timed out—
20 days agoFailed - the request timed out—
22 days agoFailed - the request timed out—

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

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