Summary
The validation step is the whole point — search results here are candidates, not answers.
search_movie says plainly that what it returns is unverified, and validate_video_url exists because a good share of those links will not play. Batch validation is what makes that workable: hand it every candidate at once instead of opening ten tabs to find the one that works.
What it is
An MCP server that searches multiple video sources for films and TV episodes, returns candidate links with title and quality, and then verifies which of those links are playable.
What you get
- search_movie — search by title, with a type for film or series and a season and episode for the latter; results come back as unverified candidates with titles, links and quality
- validate_video_url — check whether a playback page actually plays, one URL or a batch of them at once
- They are meant to be chained: search returns candidates, validation tells you which survive
Requirements
Node. Runs over stdio for MCP clients, or as a server-sent-events endpoint for web use. No account and no key.
Setup effort
One command — npx @acwink/movies-search-mcp