# Iran Cloud Status (pypi · iran-cloud-status-mcp)

Read-only status, incidents and prices of Iranian clouds: Arvan, Hamravesh, Chabokan, Liara, more.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `iran-cloud-status-mcp`: 66/100 (this document), [markdown](https://verifymcp.io/servers/sepehr071-iran-cloud-status-mcp/iran-cloud-status-mcp.md), [page](https://verifymcp.io/servers/sepehr071-iran-cloud-status-mcp/iran-cloud-status-mcp)

## Channel facts

- Registry: `pypi`
- Package: `iran-cloud-status-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 35 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to sepehr071/iran-cloud-status-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2135 tokens (~213/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Iran Cloud Status MCP server?

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

### Claude

```bash
claude mcp add sepehr071-iran-cloud-status-mcp -- uvx iran-cloud-status-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "sepehr071-iran-cloud-status-mcp": {
      "command": "uvx",
      "args": [
        "iran-cloud-status-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sepehr071-iran-cloud-status-mcp": {
      "command": "uvx",
      "args": [
        "iran-cloud-status-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add sepehr071-iran-cloud-status-mcp -- uvx iran-cloud-status-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sepehr071-iran-cloud-status-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "iran-cloud-status-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sepehr071-iran-cloud-status-mcp --command uvx --arg iran-cloud-status-mcp
```

### Hermes

```yaml
mcp_servers:
  sepehr071-iran-cloud-status-mcp:
    command: "uvx"
    args: ["iran-cloud-status-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "sepehr071-iran-cloud-status-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "iran-cloud-status-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add sepehr071-iran-cloud-status-mcp -t stdio -c uvx -a iran-cloud-status-mcp
```

### Other

```json
{
  "mcpServers": {
    "sepehr071-iran-cloud-status-mcp": {
      "command": "uvx",
      "args": [
        "iran-cloud-status-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 66, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-04 (score 81, +1)

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

### 2026-11-02 (score 80, +1)

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

### 2026-11-01 (score 79)

First indexed and scored.

## MCP tools (10)

### `cs_status` (~144 tokens)

Cloud status now

Show the live status of every Iranian cloud provider this server reads (ArvanCloud, Hamravesh, Chabokan, ParsPack, Mihan WebHost) in one call.

Use it first for "is X down?" or "what is broken right now?". Each provider gives its overall status, which
components are not operational, open incidents and upcoming maintenance counts. ParsPack has no component
status (only announcements; status 'notice' is an announcement, not an outage). Next: cs_regions for a
per-region view, cs_components for the full component list, cs_incident or cs_incidents for the timeline,
cs_maintenance for maintenance windows.

### `cs_providers` (~56 tokens)

Providers and coverage

List the providers this server covers, what each one publishes, and which are not covered.

Use it to answer "which Iranian clouds can you check?" or to pick the right provider id for the other tools.
Makes no network calls.

### `cs_components` (~202 tokens)

Components of a provider

List one provider's status components (services, regions, clusters, servers) with their current status.

Use it for "is ArvanCloud object storage in Simin OK?" or to see what a provider monitors. Status is one of
operational, degraded, partial_outage, major_outage, maintenance. Names are as published: ArvanCloud English,
Hamravesh and Chabokan Persian, Mihan WebHost server names. Use cs_regions for one line per region.

Input parameters:

- `limit` (integer): Most components to list (Mihan WebHost has over 200).
- `only_issues` (boolean): True: list only components that are not operational.
- `provider` (string, required): arvancloud, hamravesh, chabokan, parspack or mihanwebhost.
- `query`: Only components whose name or group contains this text (case-insensitive, e.g. 'object storage' or 'registry').

### `cs_regions` (~168 tokens)

Status per region

Summarise status per region or group: component count, worst status and what is not operational.

Use it for "is anything wrong in the Simin region?" or "which ArvanCloud region has problems?". Groups are the
provider's own: ArvanCloud regions (Bamdad, Simin, Forough, Shahriar, Goethe, Qeysar, Global), Hamravesh
Kubernetes cluster vs ungrouped, Chabokan service categories, Mihan WebHost server types. Next: cs_components
for the members, cs_incidents for what happened.

Input parameters:

- `provider`: One provider; leave out for all that support this tool.
- `query`: Only regions whose name contains this text (e.g. 'simin' or 'ir-central1').

### `cs_incidents` (~245 tokens)

Incidents

List recent incidents (outages, degradations, announcements) of the Iranian cloud providers, newest first, with their latest update.

Use it for "what happened to ArvanCloud this week?" or "is the Hamravesh problem fixed?". Set updates=True for
the full investigating -> resolved timeline, or call cs_incident with an id from here. ParsPack entries are
announcements: status 'notice' while open, 'resolved' after, `components` are the affected product types.
Hamravesh history reaches back years but is paged, so large `days` values cost extra requests. For counts and
downtime see cs_reliability.

Input parameters:

- `active_only` (boolean): True: only incidents that are not resolved yet.
- `days` (integer): Only incidents that started within this many days.
- `limit` (integer): Most incidents to return, newest first.
- `provider`: One provider; leave out for all that support this tool.
- `query`: Only incidents whose title or components contain this text.
- `updates` (boolean): True: include the whole update timeline of each incident, not just the latest update.

### `cs_incident` (~156 tokens)

One incident in detail

Show one incident with its full update timeline, affected components and the status each was set to.

Use it after cs_incidents or cs_status when you need the whole story of a specific outage ("what did
ArvanCloud say about incident 88?"). ArvanCloud and Chabokan have a detail endpoint; Hamravesh and ParsPack
incidents are looked up in their published history (Hamravesh: the latest ~800 entries).

Input parameters:

- `incident_id` (string, required): The `id` from cs_incidents or cs_status (a number, or a UUID for Hamravesh).
- `provider` (string, required): arvancloud, hamravesh, chabokan or parspack.

### `cs_maintenance` (~138 tokens)

Planned maintenance

List announced maintenance windows that are upcoming or running, per provider, optionally with recent finished ones.

Use it to check whether a planned change explains a disruption (include_past=True) or to warn about an
upcoming window. Empty means nothing is announced. Times are ISO with the zone (Iran time, +03:30).

Input parameters:

- `days` (integer): With include_past: how far back to look.
- `include_past` (boolean): True: also list finished windows from the last `days` days (default: only upcoming or running).
- `provider`: One provider; leave out for all that support this tool.

### `cs_reliability` (~183 tokens)

Reliability over a period

Count incidents and add up incident time per provider over the last days, with the most affected components.

Use it to compare how reliable the providers have been ("which Iranian cloud had the fewest incidents this
month?", or with query='object storage' for one service). Counts incidents that overlap the window. Minutes
run from an incident's start (or the window start) to its resolution (to now if still open) with overlapping
incidents counted once; incident_time_percent is the share of the window with at least one incident open.
That is not an uptime percentage: none of these providers publishes uptime, and a partial incident counts fully.

Input parameters:

- `days` (integer): Look-back window in days.
- `provider`: One provider; leave out for all that support this tool.
- `query`: Only count incidents whose title or components contain this text.

### `cs_pricing` (~198 tokens)

Public cloud prices

Show a provider's public price list in Toman, read from its own pricing page.

Liara: fixed plans per product (PaaS, DBaaS, IaaS and WordPress with RAM, vCPU, disk; Email, AI, ObjectStorage
with their own columns), monthly and hourly. Hamravesh: per-unit prices (vCore, GB RAM, GB SSD) in its Iran and
Germany datacenters plus traffic, IP and monitoring fees. Chabokan: the starting price of each product. Use
cs_compare_prices to price one specific server size across providers.

Input parameters:

- `product`: Liara only: PaaS, DBaaS, IaaS, WordPress, Email, AI or ObjectStorage (default: all).
- `provider` (string, required): liara, hamravesh or chabokan. ArvanCloud prices are not readable (see cs_providers).

### `cs_compare_prices` (~164 tokens)

Compare prices for a size

Price one server size (vCPU, RAM, disk) per month at Hamravesh and Liara, cheapest first.

Hamravesh charges per unit (exact size, Iran or Germany datacenter). Liara sells fixed plans, so the answer is
the cheapest PaaS and IaaS plan that is at least as big (IaaS also pays a monthly IPv4 fee). Traffic is not
included. ArvanCloud and Chabokan are not compared: no readable plan table.

Input parameters:

- `disk_gb` (number): SSD disk in GB needed.
- `ram_gb` (number, required): RAM in GB needed, e.g. 4.
- `vcpu` (number, required): vCPU cores needed, e.g. 2.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/sepehr071-iran-cloud-status-mcp/iran-cloud-status-mcp#diagnostics

## Score history

- 2026-11-05: 66
- 2026-11-04: 81
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 79

## Common questions

### What is the Iran Cloud Status MCP server?

Iran Cloud Status is an MCP server listed in the public MCP registry as io.github.sepehr071/iran-cloud-status-mcp. Read-only status, incidents and prices of Iranian clouds: Arvan, Hamravesh, Chabokan, Liara, more. This page covers its PyPI package (iran-cloud-status-mcp).

### Is the Iran Cloud Status MCP server safe to use?

Iran Cloud Status scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Cloud Status MCP server expose?

Iran Cloud Status exposes 10 tools: cs_status, cs_providers, cs_components, cs_regions, cs_incidents, and 5 more. Their descriptions and schemas cost roughly 1,654 tokens of context every time the server is loaded.

### Is the Iran Cloud Status MCP server still maintained?

Iran Cloud Status is still listed as active in the MCP registry. We last reached this channel on 5 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 Cloud Status MCP server under?

Iran Cloud Status declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/iran-cloud-status-mcp/
- Socket report: https://socket.dev/pypi/package/iran-cloud-status-mcp
- Repository: https://github.com/sepehr071/iran-cloud-status-mcp
- Changelog RSS feed: https://verifymcp.io/servers/sepehr071-iran-cloud-status-mcp/iran-cloud-status-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/sepehr071-iran-cloud-status-mcp/iran-cloud-status-mcp.json
- HTML version of this page: https://verifymcp.io/servers/sepehr071-iran-cloud-status-mcp/iran-cloud-status-mcp