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.

io.github.xianguoGou/h5-devtools-mcp

NPM · H5-DEVTOOLS-MCP

Debug H5 pages inside Android app WebViews: console logs, exceptions, run JS.

Available components

+4 this week 78 Trust /100

Last scanned (22 hours ago)

Scores higher than 58% of npm servers

Category Browser Automation

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 544 tokens (~108/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +1

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

  • 31 Oct 26 +1

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

  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 +1
    • Security disclosure: fail → unverified ▼ functional
  • 27 Oct 26 +1

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

  • 26 Oct 26 +2
    • Stability: unverified → 0.17 ▲ functional
  • 22 Oct 26 +26
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.85 ▲ 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 4 Nov 2026 · Analysed npm/h5-devtools-mcp@0.1.2

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 →

Dependencies 95 packages
Packages resolved 95
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~544 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
attach ~131

Connect to a WebView page and start buffering its console output and uncaught exceptions (the last 1000 entries). Recent messages the engine still holds are replayed on attach, but attach before reproducing an issue to be sure nothing is missed. Only observes the page: it is not reloaded or modified. May be refused while Chrome DevTools (chrome://inspect) is attached to the same page; close it and retry. Calling it again for an attached page reuses the existing session.

NameTypeReqDescription
target_idstringyesTarget id from list_targets, e.g. "<serial>/<socket>/<page id>"

No output schema declared.

No examples provided.

detach ~64

Disconnect from a page and discard its buffered console entries. The page itself keeps running and is not closed; call attach again to resume capturing. Use it to stop capturing or to start over with an empty buffer.

NameTypeReqDescription
target_idstring–Defaults to the most recently attached page

No output schema declared.

No examples provided.

evaluate_js ~130

Run a JavaScript expression in an attached page and return its result. Plain objects/arrays come back as JSON (so nested Map/Set/DOM values show as {}); other values (DOM nodes, Map, Set, Error, window) as a short description. Promises are awaited. For multiple statements or await, wrap them: (async () => { ... })(). Runs with the page's full privileges, so it can read cookies/storage and change page state.

NameTypeReqDescription
expressionstringyesJavaScript expression to evaluate
target_idstring–Defaults to the most recently attached page

No output schema declared.

No examples provided.

get_console ~179

Read buffered console messages, uncaught exceptions and browser log entries from an attached page. Requires attach first; only entries captured since attach (plus what attach replayed) are available. Returns the most recent matching entries. Pass since_seq from a previous call to get only new entries.

NameTypeReqDescription
exclude_keywordsarray–Drop entries whose text or location contains any of these (case-insensitive), e.g. ["google-analytics", "doubleclick"]
keywordstring–Case-insensitive substring match on message text and location
levelsarray–Only these levels, e.g. ["warn", "error"]
limitinteger–Max entries to return (default 50)
since_seqinteger–Only entries with seq greater than this
target_idstring–Defaults to the most recently attached page

No output schema declared.

No examples provided.

list_targets ~40

List debuggable H5 pages running inside Android WebViews (and Chrome) on connected devices. Returns a target id for each page to pass to attach.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.xianguoGou/h5-devtools-mcp server?

io.github.xianguoGou/h5-devtools-mcp runs locally as an npm package, launched with npx -y h5-devtools-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · h5-devtools-mcp

# add to Claude Code
claude mcp add xianguogou-h5-devtools-mcp -- npx -y h5-devtools-mcp
Common questions

What is the io.github.xianguoGou/h5-devtools-mcp server?

io.github.xianguoGou/h5-devtools-mcp is listed in the public MCP registry as io.github.xianguoGou/h5-devtools-mcp. Debug H5 pages inside Android app WebViews: console logs, exceptions, run JS. This page covers its npm package (h5-devtools-mcp).

Is the io.github.xianguoGou/h5-devtools-mcp server safe to use?

io.github.xianguoGou/h5-devtools-mcp scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 io.github.xianguoGou/h5-devtools-mcp server expose?

io.github.xianguoGou/h5-devtools-mcp exposes 5 tools: list_targets, attach, get_console, evaluate_js, detach. Their descriptions and schemas cost roughly 544 tokens of context every time the server is loaded.

Is the io.github.xianguoGou/h5-devtools-mcp server still maintained?

io.github.xianguoGou/h5-devtools-mcp is still listed as active in the MCP registry. We last reached this channel on 4 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 io.github.xianguoGou/h5-devtools-mcp server under?

io.github.xianguoGou/h5-devtools-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.