Remote MCP · Endpoint

FlickDirect Movie MCP Server MCP server

No. FlickDirect Movie MCP Server answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://connect.flickdirect.com/mcp

The last check completed an MCP handshake.

Registry name
com.flickdirect.connect/flickdirect-connect
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
67 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Movie MCP server: movie facts, news, reviews, trivia, podcasts, videos and published provider links.
Listing
From the official MCP registry (active).
Recent checks of FlickDirect Movie MCP Server
CheckedResultHandshake
3 hours agoHandshake completed67 ms
3 days agoHandshake completed47 ms
13 days agoHandshake completed43 ms
14 days agoHandshake completed46 ms
15 days agoHandshake completed33 ms
16 days agoHandshake completed31 ms
18 days agoHandshake completed32 ms
18 days agoHandshake completed34 ms
19 days agoHandshake completed32 ms
21 days agoHandshake completed41 ms
22 days agoHandshake completed37 ms
25 days agoHandshake completed34 ms
27 days agoHandshake completed42 ms

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

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