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.

Iran Bus Tickets

PYPI · IRAN-BUS-MCP

Read-only Iranian bus tickets (Safar724): trips, Toman prices, free seats, cheapest ticket.

Available components

63 Trust /100

Last scanned (11 hours ago)

Scores higher than 55% of PyPI servers

Category E-commerce

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/iran-bus-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 Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 957 tokens (~191/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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.

  • 20 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 19 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 18 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.1.1 → 0.1.2 functional
  • 17 Nov 26 61

    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/iran-bus-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/iran-bus-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/sepehr071/iran-bus-mcp/.github/workflows/publish.yml@refs/tags/v0.1.2
Rekor log index 3968021237
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:94790c54f0aa740965b9f97f47b39542c835a0a2711195b4a04b36c26491d9e6

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 · 5 exposed · ~657 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
bus_cheapest ~173

Cheapest bus trips between two cities on one day, merged across providers and sorted by price in Toman. Each trip carries its `provider`. A provider that failed is listed under `errors`.

NameTypeReqDescription
datestringyesTravel day: Jalali 1405/08/28 or Gregorian 2026-11-19, or today / tomorrow (Tehran time).
destinationstringyesDestination city, Persian or English, e.g. اصفهان, Isfahan.
limitinteger–How many trips.
originstringyesOrigin city, Persian or English, e.g. تهران, Tehran, or a bus_cities code.
providerstring–all, or one ticket site.
vip_onlyboolean–Only trips whose bus type says VIP.

No output schema declared.

No examples provided.

bus_cities ~71

Look up cities (name, code, province) that tickets can be bought for; use it to spell a city exactly.

NameTypeReqDescription
providerstring–all, or one ticket site.
querystringyesPart of a city name, Persian or English, e.g. اصف, shir.

No output schema declared.

No examples provided.

bus_search ~201

List bus trips between two cities on one day: time, company, bus type, price in Toman, free seats, terminals. One block per provider with the trip count and the price range. Trips with no free seat are left out. The trip id feeds bus_trip.

NameTypeReqDescription
datestringyesTravel day: Jalali 1405/08/28 or Gregorian 2026-11-19, or today / tomorrow (Tehran time).
destinationstringyesDestination city, Persian or English, e.g. اصفهان, Isfahan.
limitinteger–Trips per provider.
originstringyesOrigin city, Persian or English, e.g. تهران, Tehran, or a bus_cities code.
providerstring–all, or one ticket site.
sortstring–Order of the trips.
vip_onlyboolean–Only trips whose bus type says VIP.

No output schema declared.

No examples provided.

bus_terminals ~128

List the departure and arrival terminals that have trips on a route and the companies running them.

NameTypeReqDescription
datestringyesTravel day: Jalali 1405/08/28 or Gregorian 2026-11-19, or today / tomorrow (Tehran time).
destinationstringyesDestination city, Persian or English, e.g. اصفهان, Isfahan.
originstringyesOrigin city, Persian or English, e.g. تهران, Tehran, or a bus_cities code.
providerstring–all, or one ticket site.

No output schema declared.

No examples provided.

bus_trip ~84

Seat map summary and refund penalties of one trip: free seat numbers, seats taken by men or women.

NameTypeReqDescription
destinationstringyesDestination city, Persian or English, e.g. اصفهان, Isfahan.
providerstring–The provider the trip id came from.
trip_idintegeryesTrip id from bus_search or bus_cheapest.

No output schema declared.

No examples provided.

Install

How do I install the Iran Bus Tickets MCP server?

Iran Bus Tickets runs locally as a PyPI package, launched with uvx iran-bus-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 · iran-bus-mcp

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

What is the Iran Bus Tickets MCP server?

Iran Bus Tickets is an MCP server listed in the public MCP registry as io.github.sepehr071/iran-bus-mcp. Read-only Iranian bus tickets (Safar724): trips, Toman prices, free seats, cheapest ticket. This page covers its PyPI package (iran-bus-mcp).

Is the Iran Bus Tickets MCP server safe to use?

Iran Bus Tickets scores 63 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 Iran Bus Tickets MCP server expose?

Iran Bus Tickets exposes 5 tools: bus_cities, bus_search, bus_cheapest, bus_terminals, bus_trip. Their descriptions and schemas cost roughly 657 tokens of context every time the server is loaded.

Is the Iran Bus Tickets MCP server still maintained?

Iran Bus 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 Iran Bus Tickets MCP server under?

Iran Bus 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 Iran Bus Tickets MCP server?

VerifyMCP ran 15 checks on Iran Bus 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 Iran Bus 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.