Iran Cloud Status

io.github.sepehr071由 GitHub 账号 sepehr071 发布v0.2.0更新于 Nov 7, 2026

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

发布方自己的服务:status.live national parks

概览

Iran Cloud Status 的本地 MCP 服务;无需登录;STDIO。

暂无 AI 概览:以下信息来自注册中心条目和服务本身。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Iran Cloud Status,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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

来源:README.md,提交 3ca8ab2

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

2
  1. v0.2.0最新Nov 7, 2026
  2. v0.1.0Nov 1, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Status 集成