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

JevSim

NPM · @HUAAUDIO/JEVSIM

Run verified iOS and Android UI workflows in one agent tool call with Jev.

Available components

0 this week 75 Trust /100

Last scanned (23 hours ago)

Scores higher than 51% of npm servers

Category Testing and QA

Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.30.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 101 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 253 tokens (~84/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 0
    • Stability: 0.97 → pass security
  • 19 Nov 26 0
    • Stability: pass → 0.97 functional
  • 13 Nov 26 0
    • Stability: 0.97 → pass security
  • 12 Nov 26 +1

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

  • 11 Nov 26 −1
    • CVE-2026-126066 affects this package: high ▼ security
    • Stability: pass → 0.93 functional
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 3 Nov 26 −1
    • Security disclosure: fail → unverified ▼ functional
    • Stability: pass → 0.93 functional
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 21 Nov 2026 · Analysed npm/@huaaudio/jevsim@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 8 findings
ID CVE Severity Vector Fix available
GHSA-22jm-h49p-29qw CVE-2026-111767 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-46jr-4wx8-v453 CVE-2026-111768 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-6qxp-vccf-f47h CVE-2026-104850 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-f897-62hf-6gxq high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-rvq5-wwqv-78pq CVE-2026-111771 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-474x-hrwr-fgx4 CVE-2026-126066 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 101 packages
Packages resolved 101
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~253 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
jevsim_inspect ~81

Read accessibility state for an explicit booted iOS simulator or connected Android device. Use simulatorId for iOS; platform android and deviceId for Android. Android first use starts an Appium session. Returned UI text may be private.

NameTypeReqDescription
deviceIdstring––
platformstring––
simulatorIdstring––

No output schema declared.

No examples provided.

jevsim_run_steps ~127

Execute up to 10 caller-planned tap/type/scroll/wait/assert steps within 60 seconds. Every action needs a deterministic expected outcome. Reserve the simulator or Android device for this call; do not use another UI tool concurrently. Returns partial progress and stops on ambiguity or failure. Never automatically replay uncertain actions.

NameTypeReqDescription
deviceIdstring––
freshnessstring––
minProbabilitynumber––
platformstring––
simulatorIdstring––
stepsarrayyes–
timeoutMsinteger––

No output schema declared.

No examples provided.

jevsim_status ~45

Check backend connection, supported capabilities, iOS simulators or Android devices, and credential presence. Defaults to iOS. No secrets returned.

NameTypeReqDescription
platformstring––

No output schema declared.

No examples provided.

Install

How do I install the JevSim MCP server?

JevSim runs locally as an npm package, launched with npx -y @huaaudio/jevsim. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @huaaudio/jevsim

# add to Claude Code
claude mcp add huaaudio-jevsim -- npx -y @huaaudio/jevsim
Common questions

What is the JevSim MCP server?

JevSim is an MCP server listed in the public MCP registry as io.github.huaaudio/jevsim. Run verified iOS and Android UI workflows in one agent tool call with Jev. This page covers its npm package (@huaaudio/jevsim).

Is the JevSim MCP server safe to use?

JevSim scores 75 out of 100 on VerifyMCP. We recorded 8 known advisories against it as of 21 November 2026. It declares no install or post-install scripts. 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 JevSim MCP server expose?

JevSim exposes 3 tools: jevsim_status, jevsim_inspect, jevsim_run_steps. Their descriptions and schemas cost roughly 253 tokens of context every time the server is loaded.

Is the JevSim MCP server still maintained?

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

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

What did VerifyMCP test on the JevSim MCP server?

VerifyMCP ran 16 checks on JevSim, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.