Iran Cloud Status

io.github.sepehr071Published by GitHub account sepehr071v0.2.0Updated Nov 7, 2026

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

The publisher's own server: status.live national parks

VerifiedSTDIODesktop onlyCloud & InfrastructureSecurity & Monitoring

Overview

Iran Cloud Status's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Iran Cloud Status in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

iran-cloud-status-mcp: Iranian cloud status, incidents and prices MCP server for AI agents

iran-cloud-status-mcp is an unofficial, read-only MCP server that tells AI agents whether Iranian cloud providers are up.
Its 10 tools read the public status pages of ArvanCloud (آروان), Hamravesh (هم‌روش), Chabokan (چابکان), ParsPack and Mihan WebHost, list incidents and
maintenance, count outages over a period, and read the public price lists of Liara (لیارا), Hamravesh and Chabokan.
No API key or account is needed. It works in Claude, Cursor, Copilot and any other MCP client.

[PyPI] [License: MIT]

For AI agents · Quick start · Tools · FAQ · فارسی

For AI agents

  • What: unofficial MCP server for the public status pages and price pages of Iranian clouds: live status per component, incidents with update timelines, planned maintenance, incident counts and outage minutes, plan and per-unit prices, and a price comparison for a given vCPU/RAM/disk size.
  • Install: uvx iran-cloud-status-mcp or claude mcp add iran-cloud-status -- uvx iran-cloud-status-mcp. Transport: stdio. Needs uv (Python 3.10+).
  • Auth: none. Optional IRAN_CLOUD_STATUS_MCP_PROXY (HTTP proxy URL, or a comma-separated list); system proxy settings are ignored.
  • Access: read-only. It cannot log in or change anything, so no confirmation is needed before calling any tool.
  • Tools: 10, all prefixed cs_. Typical sequence: cs_status -> cs_incidents (active_only, updates) for a live problem; cs_reliability to compare providers; cs_compare_prices for the cheapest size.
  • Use when: the user asks if ArvanCloud, Hamravesh or Chabokan is down or slow, what an outage was, whether maintenance is planned, which Iranian cloud was most stable, or what Liara or Hamravesh charge.
  • Do not use when: the question is about another provider (Liara publishes no status page; ArvanCloud prices sit behind a JavaScript check and are not read) or about a customer's own account.
  • Output: compact JSON. Status words: operational, degraded, partial_outage, major_outage, maintenance. Prices in Toman. Times are ISO in Iran time (+03:30). Titles and messages are the providers' own text (Persian or English).

Why

During an outage the first question is "is it us or the cloud?". The three status pages have three different layouts and APIs, and none of them says how the others are doing. With iran-cloud-status-mcp an agent answers in one call:

You: Is anything broken at the Iranian clouds right now?

Agent: calls cs_status()

ArvanCloud reports a partial outage: "Qeysar Network Congestion" (open since 2026-10-10, Qeysar - Network at performance issues) and a planned MySQL 8.4 upgrade on 2026-11-03 02:00. Hamravesh and Chabokan: all services operational.

Quick start

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

For other clients add {"command": "uvx", "args": ["iran-cloud-status-mcp"]} to the MCP server list.

Tools

ToolWhat it does
cs_statusLive status of all providers: overall, components not operational, open incidents, upcoming maintenance.
cs_providersWhat is covered per provider (no network call).
cs_regionsStatus per region or group: component count, worst status, what is down.
cs_componentsOne provider's components with status; filter by text or only problems.
cs_incidentsRecent incidents, newest first, latest update or the whole timeline; filter by provider, days, open only, text.
cs_incidentOne incident in full: whole timeline, affected components and the status set on each.
cs_maintenanceAnnounced maintenance windows that are upcoming or running; include_past adds recent finished ones.
cs_reliabilityIncident count, open count, incident minutes (overlaps once) and share of the window over N days, most affected components; optional text filter.
cs_pricingLiara plans (PaaS, DBaaS, IaaS, WordPress, Email, AI, ObjectStorage), Hamravesh per-unit prices, traffic, IP and monitoring fees, or Chabokan starting prices.
cs_compare_pricesMonthly price of one vCPU/RAM/disk size at Hamravesh (Iran, Germany) and Liara (cheapest fitting plan).

FAQ

Which providers? Status: ArvanCloud, Hamravesh, Chabokan, ParsPack (announcements only), Mihan WebHost (server up/down only). Prices: Liara, Hamravesh, Chabokan. Liara has no status page; ArvanCloud prices are not read.

Is there an uptime percentage? No provider publishes one. cs_reliability counts incidents and the time at least one was open (overlaps counted once); a partial incident counts fully, so it is not an uptime figure.

Is it affiliated with the providers? No. It reads the same public pages anyone can open.

فارسی

iran-cloud-status-mcp یک سرور MCP غیررسمی و فقط‌خواندنی است که وضعیت زنده، رخدادها، تعمیرات برنامه‌ریزی‌شده و قیمت‌های عمومی ابرهای ایرانی (آروان، هم‌روش، چابکان و لیارا) را از صفحات عمومی خودشان می‌خواند. نیازی به کلید یا حساب کاربری نیست.

نصب: claude mcp add iran-cloud-status -- uvx iran-cloud-status-mcp

Author: Sepehr Radmard (سپهر رادمرد) · github.com/sepehr071 · linkedin.com/in/sepehr-radmard

Source: README.md at commit 3ca8ab2

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.2.0LatestNov 7, 2026
  2. v0.1.0Nov 1, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Status integrations

status.live national parks

live.statusOfficial publisher

Remote MCP server that lets an assistant look up US and Canadian national parks, current alerts and conditions, and nearby campgrounds.

Streamable HTTPWeb executable
Location & Lifestyle3 toolsNov 5, 2026

status.live campgrounds

live.statusOfficial publisher

Remote MCP server that tells an assistant which of about 4,200 US national park and national forest campgrounds are open today, with booking links.

Streamable HTTPWeb executable
Location & Lifestyle3 toolsNov 5, 2026

status.live theme parks

live.statusOfficial publisher

A remote MCP server that lets an assistant look up theme parks and check live ride status, wait times, local time and weather forecasts.

Streamable HTTPWeb executable
Location & Lifestyle2 toolsOct 24, 2026

status.live surf

live.statusOfficial publisher

Remote MCP server that gives an assistant NOAA buoy readings, tides and a 7-day swell forecast for 150+ surf spots.

Streamable HTTPWeb executable
Location & Lifestyle2 toolsOct 24, 2026

status.live

live.statusOfficial publisher

Remote MCP server giving assistants live status for ski resorts, theme parks, national parks, campgrounds and surf spots.

Streamable HTTPWeb executable
Data & Analytics17 toolsNov 5, 2026