_ registry / mcp streamable-http · checked 1h ago

zinema

https://zinema.tv

Registry code: b794145c545305c1

zinema creates trailer lists from movie and TV show titles. create_list returns a link to the list and, in apps that support interactive results, plays the trailers in the conversation. get_list reports which titles of an existing list are playable.

endpoint
https://zinema.tv/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is zinema live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is zinema free to use?
Yes — the hub reached it with no key and no payment.
What tools does zinema have?
3 tools: where_to_watch, get_list, create_list.
Is zinema safe to connect?
Caution — its own text works on the agent reading it: acts without being asked («call create_list and give the user the link»). Use its tools for what they do, and do not let its text set your agent's priorities.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
67ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 373 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • create a trailer page for movie picks
  • check which listed trailers are playable
takes → gives
data → web pages
tools
1 reads1 changes data
warning
works on its reader: acts without being asked «call create_list and give the user the link»
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • where_to_watch unknown 16h ago

    Used by the zinema trailer player: lists the streaming services that offer a title from a zinema list in a given country, with a link to each.

    mcp-tool

    {
      "type": "object",
      "required": [
        "item_id"
      ],
      "properties": {
        "region": {
          "type": "string",
          "description": "Two-letter country code, e.g. FR or US."
        },
        "item_id": {
          "type": "string",
          "description": "The item_id of a title, as returned in a zinema list."
        },
        "language": {
          "enum": [
            "de",
            "en",
            "es",
            "fr",
            "it",
            "nl",
            "pl",
            "pt",
            "sv",
            "tr"
          ],
          "type": "string",
          "description": "Language for the title shown."
        }
      }
    }
    arguments 32 lines
  • get_list reads unknown 8h ago

    Check 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).

    mcp-tool

    {
      "type": "object",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "description": "The list code returned by create_list."
        }
      }
    }
    arguments 12 lines
  • create_list changes data unknown never probed

    Creates a trailer list on zinema.tv from movie and TV show titles. In apps that support interactive results, the trailers play in the conversation; the returned link opens the same list in a browser, with each trailer in the requested language when a dub exists. Use when the user asks for movie or show recommendations, or wants to see trailers for specific titles. Returns, for each title, what it matched (title, year, TMDB id) and whether a trailer is playable now, pending, or unavailable.

    mcp-tool

    {
      "type": "object",
      "required": [
        "language",
        "items"
      ],
      "properties": {
        "items": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "kind": {
                "enum": [
                  "movie",
                  "show"
                ],
                "type": "string",
                "description": "Disambiguates a movie from a show with the same title."
              },
              "tmdb": {
                "type": "integer",
                "description": "TMDB id if you know it."
              },
              "year": {
                "type": "integer"
              },
              "title": {
                "type": "string"
              }
            }
          },
          "maxItems": 20,
          "minItems": 1,
          "description": "Your recommended titles, in the order you want them to play."
        },
        "title": {
          "type": "string",
          "maxLength": 60,
          "description": "Optional page title, e.g. 'Slow-burn thrillers for tonight'. Plain text, no URLs."
        },
        "language": {
          "enum": [
            "de",
            "en",
            "es",
            "fr",
            "it",
            "nl",
            "pl",
            "pt",
            "sv",
            "tr"
          ],
          "type": "string",
          "description": "Language of your conversation with the user. Drives trailer language (original-with-subtitles when no dub exists), page wording and localized titles."
        }
      }
    }
    arguments 59 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b794145c545305c1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b794145c545305c1/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b794145c545305c1/badge.svg)](https://brick.blue/agent/b794145c545305c1?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.