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 Weather

PYPI · IRAN-WEATHER-MCP

Read-only Iran Meteorological Org (irimo.ir): city forecasts, observations, warnings.

Available components

62 Trust /100

Last scanned (17 hours ago)

Scores higher than 54% of PyPI servers

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-weather-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 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1241 tokens (~137/item across 9 items; 9 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 89% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (14)

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

Checks we could not complete (2)

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.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

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.

  • 20 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 19 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 18 Nov 26 62

    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-weather-mcp@0.1.1

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

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 · 9 exposed · ~882 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
wx_airports ~135

Aviation forecasts (TAF) of about 29 Iranian airports with their flight category (vfr, mvfr, ifr, lifr). Without `airport` only the list with categories is returned; with it, the full TAF text of the match. TAF is the standard coded airport forecast (wind, visibility, cloud, TEMPO/BECMG changes, UTC times). `station_id` works in wx_weather for the city's ground observation.

NameTypeReqDescription
airportstring|null–ICAO code (OIII, OIMM) or part of the English name (Mashhad); empty lists all airports

No output schema declared.

No examples provided.

wx_bulletins ~95

Link to the latest official forecast bulletin (PDF): 5-day, weekly, seasonal, Tehran province or Tehran air quality. The site publishes these long-range forecasts only as PDF files, so this returns the title, publish date and the PDF link, not the text.

NameTypeReqDescription
kindstring–five_day, weekly (about 6 weeks), seasonal, tehran (province) or air_quality (Tehran)

No output schema declared.

No examples provided.

wx_cities ~67

Today's forecast (condition, max and min temperature) for the main cities (about 35), with the ids wx_weather accepts. Start here for "what is the weather in Iran today". Temperatures are in °C; `day` is the Persian date label the site shows.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

wx_observations ~51

Current temperature, humidity and wind at the ~37 stations on the national map of irimo.ir. Compact whole-country snapshot (main cities, airports, islands). For one city's full detail use wx_weather.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

wx_province ~84

Latest observations of every weather station in the province of a city. Each station has an id (usable in wx_weather), temperature in °C, humidity, wind speed and the direction it blows from. Stations without a reading show no temperature.

NameTypeReqDescription
citystringyesAny city or station of the province (تهران, مشهد) or its station id

No output schema declared.

No examples provided.

wx_road ~112

Current weather of every city along a main road, from the road-weather service of irimo.ir. One row per city in route order: time, condition, temperature, visibility, pressure, wind. If the route name is not exact, the matching routes are returned (`routes`) to pick from. Only the routes the site lists (about 400).

NameTypeReqDescription
routestringyesRoute as 'origin-destination' in Persian (تهران-مشهد, آبادان تهران) or a route id

No output schema declared.

No examples provided.

wx_warning ~89

Full text of one warning: system description, start and end time, hazard, affected area, impact, advice. `details` lists the labelled lines the site prints (Persian, as written; a warning for two systems repeats the labels). `files` holds the PDF bulletin and `map_image` the affected-area map.

NameTypeReqDescription
warning_idintegeryesWarning id from wx_warnings

No output schema declared.

No examples provided.

wx_warnings ~126

Latest official warnings of the Iran Meteorological Organization, newest first. Each has an id for wx_warning, a type, a level (yellow, orange, red) and a number. Warnings are issued per event and nothing marks them expired: check the dates in wx_warning.

NameTypeReqDescription
kindstring–Warning type: weather (rain, wind, snow, heat), marine (sea), pollution (air quality), agriculture (frost, farming)
limitinteger––
pageinteger–List page, 20 warnings per page, newest first

No output schema declared.

No examples provided.

wx_weather ~123

Current observation and 3-day forecast for one city or weather station. Current: temperature, wind, humidity, visibility, rain and min/max over the last 24 h, with the observation time and the update time (Jalali, Tehran time). Forecast: three 24 h periods with condition and min/max. Not every station has a forecast; small stations only have observations.

NameTypeReqDescription
citystringyesCity or station name in Persian (تهران, مشهد, کاشمر) or a station id from wx_cities / wx_province

No output schema declared.

No examples provided.

Install

How do I install the Iran Weather MCP server?

Iran Weather runs locally as a PyPI package, launched with uvx iran-weather-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-weather-mcp

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

What is the Iran Weather MCP server?

Iran Weather is an MCP server listed in the public MCP registry as io.github.sepehr071/iran-weather-mcp. Read-only Iran Meteorological Org (irimo.ir): city forecasts, observations, warnings. This page covers its PyPI package (iran-weather-mcp).

Is the Iran Weather MCP server safe to use?

Iran Weather scores 62 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 Weather MCP server expose?

Iran Weather exposes 9 tools: wx_cities, wx_weather, wx_province, wx_observations, wx_warnings, and 4 more. Their descriptions and schemas cost roughly 882 tokens of context every time the server is loaded.

Is the Iran Weather MCP server still maintained?

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

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

VerifyMCP ran 14 checks on Iran Weather, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about Iran Weather: Malware scan and Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.