Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.FadingLight9291117/harmonyos

NPM · MCP-HARMONYOS · SCANNED AUG 3

MCP server for HarmonyOS development - interact with projects, devices, and applications

Available components

+20 this week 66 Trust /100
Trust breakdown (6 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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability57
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 237 tokens (~33/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · mcp-harmonyos

# add to Claude Code
claude mcp add fadinglight9291117-harmonyos -- npx -y mcp-harmonyos
# add to Codex CLI
codex mcp add fadinglight9291117-harmonyos -- npx -y mcp-harmonyos
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fadinglight9291117-harmonyos": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-harmonyos"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add fadinglight9291117-harmonyos --command npx --arg -y --arg mcp-harmonyos
# ~/.hermes/config.yaml
mcp_servers:
  fadinglight9291117-harmonyos:
    command: "npx"
    args: ["-y", "mcp-harmonyos"]
// mcp.json
{
  "mcpServers": {
    "fadinglight9291117-harmonyos": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-harmonyos"
      ]
    }
  }
}
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.

  • 3 Aug 26 +4
    • Stability: unverified → 0.27 functional
  • 2 Aug 26 +41
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: 100 → unverified functional
    • Schema quality: unverified → fair functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • License: unverified → pass functional
    • First check of Schema quality: unverified functional
    • Licence: MIT functional
  • 31 Jul 26 −25
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 46

    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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 96 packages

96 packages in the resolved dependency tree · 96 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 7 exposed · ~237 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.

Tool Tokens
harmonyos_check_build_outputs ~36

Check if build outputs exist and list them

NameTypeReqDescription
projectPathstringyesAbsolute path to the HarmonyOS project root

No output schema declared.

No examples provided.

harmonyos_get_app_info ~43

Get detailed information about an installed application

NameTypeReqDescription
bundleNamestringyesThe application bundle name
deviceIdstringyesThe device UDID

No output schema declared.

No examples provided.

harmonyos_get_device_info ~31

Get detailed information about a specific device

NameTypeReqDescription
deviceIdstringyesThe device UDID

No output schema declared.

No examples provided.

harmonyos_get_project_info ~40

Get HarmonyOS project information (bundleName, version, modules)

NameTypeReqDescription
projectPathstringyesAbsolute path to the HarmonyOS project root

No output schema declared.

No examples provided.

harmonyos_list_devices ~17

List all connected HarmonyOS devices

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

harmonyos_list_installed_apps ~32

List all installed applications on a device

NameTypeReqDescription
deviceIdstringyesThe device UDID

No output schema declared.

No examples provided.

harmonyos_list_modules ~38

List all modules in a HarmonyOS project with their types

NameTypeReqDescription
projectPathstringyesAbsolute path to the HarmonyOS project root

No output schema declared.

No examples provided.