
zinema MCP server
Which MCP servers are zinema's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-16
- Registry nametv.zinema/zinemaverified in the MCP registry
The registry name sits under zinema.tv. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-16
- Tools2
- Server calls itselfzinema
- Server version0.1
- Protocol version2025-06-18
On 2026-10-16 the server answered initialize and tools/list without a sign-in. First answer in 168 ms.
- Its tools do none of the product's use cases we checked: browse trailers and cinema showtimes in one feed; play films from a personal Plex or Jellyfin server.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score72 of 100answers 100 · does the job 0 · definitions 100 · context 100 · connects 100
- What an agent can do with it0 of 2 use cases
- Answered100% of days17 of 17 daily checks
- Median first answer495 ms
- Space in an agent's context≈ 593 tokensthe definitions of all its tools (3), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- not sure · find films to watch across streaming services and cinemas
- cannot · browse trailers and cinema showtimes in one feed
- cannot · play films from a personal Plex or Jellyfin server
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
create_listTurn your movie/TV recommendations into a playable trailer page on zinema.tv and share the link with the user. Each title plays as a full trailer the user can scroll, like a personal cinema session. Links are permanent and free. Returns…
get_listCheck a zinema list you created earlier: which titles play now. A title that was 'pending' may have become 'playable' (its trailer gets acquired automatically) or 'no_trailer' (none exists anywhere).
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"zinema": {
"type": "http",
"url": "https://zinema.tv/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http zinema https://zinema.tv/mcpclaude.ai, ChatGPT and other clients: add https://zinema.tv/mcp as a custom connector in the settings.
OpenAPI spec
164 paths, read 2026-10-16. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.