Reading a PKGBUILD carefully is the one step everybody skips, and having it checked against a red-flag list plus a maintainer trust score turns that into something you actually do. The guided update prompt does the same for the other classic mistake: check critical news, verify disk space, list what is coming, and check services — in that order, before you type the upgrade command.
An unofficial community server bridging AI assistants to the Arch Linux ecosystem: the Wiki, the AUR, the official repositories, and, when you are on Arch, the local pacman database and systemd state. Search and analysis tools work on any operating system.
- Search anywhere: `search_archwiki` returns ranked Wiki results, `search_aur` sorts by relevance, votes, popularity or last modified, `get_official_package_info` covers the repositories
- Safety before install: `analyze_pkgbuild_safety` checks a PKGBUILD against 50+ red flags, `analyze_package_metadata_risk` scores trust from votes, maintainer and age, and `install_package_secure` blocks packages it judges malicious
- Maintenance on Arch: `manage_orphans` always dry-runs first, `verify_package_integrity` finds modified or missing files, `manage_install_reason` and `query_file_ownership` sort out what belongs to what
- System state: `get_system_info`, `check_disk_space`, `check_failed_services`, `get_boot_logs`, `check_database_freshness`, and `query_package_history` over the pacman log
- News that matters before an update: `get_latest_news`, `check_critical_news` for entries needing manual intervention, and `get_news_since_last_update`
- Guided prompts that chain the above: `troubleshoot_issue`, `audit_aur_package`, `analyze_dependencies` and `safe_system_update`
Python 3.11+ and uv; `uvx arch-ops-server` runs it with nothing to clone. Wiki, AUR, PKGBUILD analysis and news work on any system; the pacman, systemd and mirror tools are marked Arch-only or systemd-only and will not help elsewhere. No account and no API key.
One command — uvx arch-ops-server
