Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Cinematicket Tickets

PYPI · CINEMATICKET-MCP

Read-only Cinematicket (cinematicket.org): cinemas, films, showtimes, prices, theatre, box office.

Available components

65 Trust /100

Last scanned (13 hours ago)

Scores higher than 57% of PyPI servers

Category Entertainment and Games

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 35 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency84
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to sepehr071/cinematicket-mcp). View diagnostics → Pass
  • License check failed: the license (PolyForm-Noncommercial-1.0.0) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 3 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1072 tokens (~107/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 0
    • Malware scan: unverified → pass ▲ security
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.1.1 → 0.1.2 functional
  • 17 Nov 26 63

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed pypi/cinematicket-mcp@0.1.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo sepehr071/cinematicket-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/sepehr071/cinematicket-mcp/.github/workflows/publish.yml@refs/tags/v0.1.2
Rekor log index 3968013155
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:6f02c90b48addd33db8c4f6488bd0d96bee0f112a9e985aa5077ce49324ea0a5

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 35 packages
Packages resolved 35
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~743 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
ct_box_office ~70

Top-grossing films by total ticket sales (Toman), with audience figures, cinemas and weeks on screen.

NameTypeReqDescription
limitinteger–Max films
yearinteger|null–Release year in the Jalali calendar, e.g. 1405. Omit for all-time

No output schema declared.

No examples provided.

ct_cinema ~82

One cinema's info (address, phone, halls, rules) and its full program for a day: films, halls, times, prices (Toman).

NameTypeReqDescription
cinema_idintegeryesCinema id from ct_cinemas or ct_showtimes
datestring|null–Day as YYYY-MM-DD (Gregorian). Default: first day with sessions

No output schema declared.

No examples provided.

ct_cinemas ~69

Cinemas and venues in a city, most popular first, with rating, address, facilities and coordinates.

NameTypeReqDescription
city_idintegeryesCity id from ct_cities
limitinteger–Max cinemas
querystring|null–Only names or addresses containing this text

No output schema declared.

No examples provided.

ct_cities ~49

List the cities Cinematicket sells tickets in, with the city ids other tools take. Tehran is 235, Mashhad 204, Isfahan 266, Shiraz 63.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ct_events ~85

List theatre plays, concerts or films with sessions on sale, with rating and director. Then use ct_film or ct_showtimes with the id.

NameTypeReqDescription
kindstring–theater, concert or cinema
limitinteger–Max results
pageinteger–Page number, from 1
querystring|null–Title text to search for

No output schema declared.

No examples provided.

ct_film ~76

Cast, director, genre, rating, duration, summary and sales of one film or show, plus how widely it is screened. Sales (Toman) come from the box-office table and only exist for released films.

NameTypeReqDescription
film_idintegeryesFilm or show id from ct_now_showing, ct_search or ct_events

No output schema declared.

No examples provided.

ct_now_showing ~96

Films and shows on sale now, grouped by category, nationwide (the site's home feed). The feed is not filtered by city; use ct_showtimes with a city id to see what plays where.

NameTypeReqDescription
category_idinteger|null–Only this category id (155 Iranian film, 156 foreign film, 147 theatre, 150 concert...). Omit for all.
limitinteger–Max films per category

No output schema declared.

No examples provided.

ct_search ~48

Search films, shows and cinemas by name; returns ids for ct_film, ct_showtimes and ct_cinema.

NameTypeReqDescription
querystringyesFilm, show or cinema name (Persian)

No output schema declared.

No examples provided.

ct_showtimes ~137

Where and when a film or show plays: cinemas, halls, times and ticket prices (Toman) for one day. Read-only. Seats left are not public (the site only shows them in the seat map, which this server never opens).

NameTypeReqDescription
cinema_idinteger|null–Only this cinema
city_idinteger|null–City id from ct_cities. Omit for every city (large)
datestring|null–Day as YYYY-MM-DD (Gregorian). Default: first day with sessions
film_idintegeryesFilm or show id
limitinteger–Max cinemas

No output schema declared.

No examples provided.

ct_upcoming ~31

Films announced as coming soon, with release dates (the site's next-programs page; it is often empty).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Cinematicket Tickets MCP server?

Cinematicket Tickets runs locally as a PyPI package, launched with uvx cinematicket-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · cinematicket-mcp

# add to Claude Code
claude mcp add sepehr071-cinematicket-mcp -- uvx cinematicket-mcp
Common questions

What is the Cinematicket Tickets MCP server?

Cinematicket Tickets is an MCP server listed in the public MCP registry as io.github.sepehr071/cinematicket-mcp. Read-only Cinematicket (cinematicket.org): cinemas, films, showtimes, prices, theatre, box office. This page covers its PyPI package (cinematicket-mcp).

Is the Cinematicket Tickets MCP server safe to use?

Cinematicket Tickets scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Cinematicket Tickets MCP server expose?

Cinematicket Tickets exposes 10 tools: ct_cities, ct_now_showing, ct_film, ct_cinemas, ct_cinema, and 5 more. Their descriptions and schemas cost roughly 743 tokens of context every time the server is loaded.

Is the Cinematicket Tickets MCP server still maintained?

Cinematicket Tickets is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Cinematicket Tickets MCP server under?

Cinematicket Tickets declares the PolyForm-Noncommercial-1.0.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

What did VerifyMCP test on the Cinematicket Tickets MCP server?

VerifyMCP ran 15 checks on Cinematicket Tickets, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Cinematicket Tickets: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.