Remote MCP · Endpoint

goodrecmovies MCP server

No. goodrecmovies answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://goodrecmovies.com/mcp

The last check completed an MCP handshake.

Registry name
com.goodrecmovies/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
571 ms
Tools exposed
4 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Movie and series ranking as MCP tools: top titles, search, lookup by IMDb id. Free, no key.
Listing
From the official MCP registry (active).
Recent checks of goodrecmovies
CheckedResultHandshake
4 hours agoHandshake completed571 ms
2 days agoHandshake completed609 ms
4 days agoHandshake completed588 ms
6 days agoHandshake completed600 ms
8 days agoHandshake completed609 ms
10 days agoHandshake completed786 ms
12 days agoHandshake completed806 ms
13 days agoHandshake completed1.03 s
14 days agoHandshake completed1.20 s
16 days agoFailed - the server returned an HTTP error—
18 days agoHandshake completed136 ms
20 days agoHandshake completed768 ms
21 days agoHandshake completed122 ms
23 days agoHandshake completed192 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 goodrecmovies and makes no claim about it beyond what these checks measured.