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.Glittering/ai-browser

NPM · @GLITTERING0717/AI-BROWSER

Visible Electron browser driven by a semantic accessibility tree: 17 MCP tools, no screenshots.

+24 this week 71 Trust /100

Last scanned (10 minutes ago)

Scores higher than 40% 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 Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects electron 33.4.11, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 61 of 158 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2061 tokens (~121/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability check failed: the tool surface changed between 1.2.1 and 2.5.2: 4 tool removals, 0 breaking changes, 4 additions. See how to fix → Fail
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 96% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 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.

  • 5 Nov 26 +1
    • CVE-2026-34764 affects this package: high ▼ security
    • CVE-2026-34771 affects this package: high ▼ security
    • CVE-2026-34765 affects this package: high ▼ security
    • CVE-2026-70612 affects this package: high ▼ security
    • CVE-2026-113797 affects this package: high ▼ security
    • CVE-2026-34774 affects this package: high ▼ security
    • CVE-2026-114124 affects this package: high ▼ security
    • CVE-2026-70607 affects this package: high ▼ security
    • CVE-2026-102674 affects this package: high ▼ security
    • CVE-2026-114121 affects this package: high ▼ security
    • CVE-2025-55305 affects this package: high ▼ security
    • CVE-2026-70611 affects this package: high ▼ security
    • CVE-2026-70610 affects this package: high ▼ security
    • CVE-2026-70600 affects this package: high ▼ security
    • CVE-2026-34768 affects this package: high ▼ security
    • CVE-2026-113798 affects this package: high ▼ security
    • CVE-2026-34767 affects this package: high ▼ security
    • CVE-2026-34777 affects this package: high ▼ security
    • CVE-2026-102673 affects this package: high ▼ security
    • CVE-2026-34779 affects this package: high ▼ security
    • CVE-2026-34773 affects this package: high ▼ security
    • CVE-2026-34781 affects this package: high ▼ security
    • CVE-2026-70597 affects this package: high ▼ security
    • CVE-2026-113800 affects this package: high ▼ security
    • CVE-2026-34778 affects this package: high ▼ security
    • CVE-2026-70601 affects this package: high ▼ security
    • CVE-2026-70602 affects this package: high ▼ security
    • CVE-2026-114122 affects this package: high ▼ security
    • CVE-2026-102676 affects this package: high ▼ security
    • CVE-2026-70604 affects this package: high ▼ security
    • CVE-2026-34769 affects this package: high ▼ security
    • CVE-2026-34770 affects this package: high ▼ security
    • CVE-2026-34776 affects this package: high ▼ security
    • CVE-2026-34772 affects this package: high ▼ security
    • CVE-2026-70598 affects this package: high ▼ security
    • CVE-2026-34775 affects this package: high ▼ security
    • CVE-2026-70608 affects this package: high ▼ security
    • CVE-2026-113796 affects this package: high ▼ security
    • CVE-2026-70609 affects this package: high ▼ security
    • CVE-2026-70605 affects this package: high ▼ security
    • CVE-2026-102672 affects this package: high ▼ security
    • CVE-2026-115570 affects this package: high ▼ security
    • CVE-2026-102675 affects this package: high ▼ security
    • CVE-2026-34766 affects this package: high ▼ security
    • CVE-2026-70599 affects this package: high ▼ security
    • CVE-2026-70603 affects this package: high ▼ security
  • 4 Nov 26 0
    • CVE-2026-34764 affects this package: high ▼ security
    • CVE-2026-34771 affects this package: high ▼ security
    • CVE-2026-34765 affects this package: high ▼ security
    • CVE-2026-70612 affects this package: high ▼ security
    • CVE-2026-113797 affects this package: high ▼ security
    • CVE-2026-34774 affects this package: high ▼ security
    • CVE-2026-114124 affects this package: high ▼ security
    • CVE-2026-70607 affects this package: high ▼ security
    • CVE-2026-102674 affects this package: high ▼ security
    • CVE-2026-114121 affects this package: high ▼ security
    • CVE-2025-55305 affects this package: high ▼ security
    • CVE-2026-70611 affects this package: high ▼ security
    • CVE-2026-70610 affects this package: high ▼ security
    • CVE-2026-70600 affects this package: high ▼ security
    • CVE-2026-34768 affects this package: high ▼ security
    • CVE-2026-113798 affects this package: high ▼ security
    • CVE-2026-34767 affects this package: high ▼ security
    • CVE-2026-34777 affects this package: high ▼ security
    • CVE-2026-102673 affects this package: high ▼ security
    • CVE-2026-34779 affects this package: high ▼ security
    • CVE-2026-34773 affects this package: high ▼ security
    • CVE-2026-34781 affects this package: high ▼ security
    • CVE-2026-70597 affects this package: high ▼ security
    • CVE-2026-113800 affects this package: high ▼ security
    • CVE-2026-34778 affects this package: high ▼ security
    • CVE-2026-70601 affects this package: high ▼ security
    • CVE-2026-70602 affects this package: high ▼ security
    • CVE-2026-114122 affects this package: high ▼ security
    • CVE-2026-102676 affects this package: high ▼ security
    • CVE-2026-70604 affects this package: high ▼ security
    • CVE-2026-34769 affects this package: high ▼ security
    • CVE-2026-34770 affects this package: high ▼ security
    • CVE-2026-34776 affects this package: high ▼ security
    • CVE-2026-34772 affects this package: high ▼ security
    • CVE-2026-70598 affects this package: high ▼ security
    • CVE-2026-34775 affects this package: high ▼ security
    • CVE-2026-70608 affects this package: high ▼ security
    • CVE-2026-113796 affects this package: high ▼ security
    • CVE-2026-70609 affects this package: high ▼ security
    • CVE-2026-70605 affects this package: high ▼ security
    • CVE-2026-102672 affects this package: high ▼ security
    • CVE-2026-115570 affects this package: high ▼ security
    • CVE-2026-102675 affects this package: high ▼ security
    • CVE-2026-34766 affects this package: high ▼ security
    • CVE-2026-70599 affects this package: high ▼ security
    • CVE-2026-70603 affects this package: high ▼ security
  • 3 Nov 26 +1
    • CVE-2026-34764 affects this package: high ▼ security
    • CVE-2026-34771 affects this package: high ▼ security
    • CVE-2026-34765 affects this package: high ▼ security
    • CVE-2026-70612 affects this package: high ▼ security
    • CVE-2026-113797 affects this package: high ▼ security
    • CVE-2026-34774 affects this package: high ▼ security
    • CVE-2026-114124 affects this package: high ▼ security
    • CVE-2026-70607 affects this package: high ▼ security
    • CVE-2026-102674 affects this package: high ▼ security
    • CVE-2026-114121 affects this package: high ▼ security
    • CVE-2025-55305 affects this package: high ▼ security
    • CVE-2026-70611 affects this package: high ▼ security
    • CVE-2026-70610 affects this package: high ▼ security
    • CVE-2026-70600 affects this package: high ▼ security
    • CVE-2026-34768 affects this package: high ▼ security
    • CVE-2026-113798 affects this package: high ▼ security
    • CVE-2026-34767 affects this package: high ▼ security
    • CVE-2026-34777 affects this package: high ▼ security
    • CVE-2026-102673 affects this package: high ▼ security
    • CVE-2026-34779 affects this package: high ▼ security
    • CVE-2026-34773 affects this package: high ▼ security
    • CVE-2026-34781 affects this package: high ▼ security
    • CVE-2026-70597 affects this package: high ▼ security
    • CVE-2026-113800 affects this package: high ▼ security
    • CVE-2026-34778 affects this package: high ▼ security
    • CVE-2026-70601 affects this package: high ▼ security
    • CVE-2026-70602 affects this package: high ▼ security
    • CVE-2026-114122 affects this package: high ▼ security
    • CVE-2026-102676 affects this package: high ▼ security
    • CVE-2026-70604 affects this package: high ▼ security
    • CVE-2026-34769 affects this package: high ▼ security
    • CVE-2026-34770 affects this package: high ▼ security
    • CVE-2026-34776 affects this package: high ▼ security
    • CVE-2026-34772 affects this package: high ▼ security
    • CVE-2026-70598 affects this package: high ▼ security
    • CVE-2026-34775 affects this package: high ▼ security
    • CVE-2026-70608 affects this package: high ▼ security
    • CVE-2026-113796 affects this package: high ▼ security
    • CVE-2026-70609 affects this package: high ▼ security
    • CVE-2026-70605 affects this package: high ▼ security
    • CVE-2026-102672 affects this package: high ▼ security
    • CVE-2026-115570 affects this package: high ▼ security
    • CVE-2026-102675 affects this package: high ▼ security
    • CVE-2026-34766 affects this package: high ▼ security
    • CVE-2026-70599 affects this package: high ▼ security
    • CVE-2026-70603 affects this package: high ▼ security
  • 2 Nov 26 0
    • CVE-2026-34764 affects this package: high ▼ security
    • CVE-2026-34771 affects this package: high ▼ security
    • CVE-2026-34765 affects this package: high ▼ security
    • CVE-2026-70612 affects this package: high ▼ security
    • CVE-2026-113797 affects this package: high ▼ security
    • CVE-2026-34774 affects this package: high ▼ security
    • CVE-2026-114124 affects this package: high ▼ security
    • CVE-2026-70607 affects this package: high ▼ security
    • CVE-2026-102674 affects this package: high ▼ security
    • CVE-2026-114121 affects this package: high ▼ security
    • CVE-2025-55305 affects this package: high ▼ security
    • CVE-2026-70611 affects this package: high ▼ security
    • CVE-2026-70610 affects this package: high ▼ security
    • CVE-2026-70600 affects this package: high ▼ security
    • CVE-2026-34768 affects this package: high ▼ security
    • CVE-2026-113798 affects this package: high ▼ security
    • CVE-2026-34767 affects this package: high ▼ security
    • CVE-2026-34777 affects this package: high ▼ security
    • CVE-2026-102673 affects this package: high ▼ security
    • CVE-2026-34779 affects this package: high ▼ security
    • CVE-2026-34773 affects this package: high ▼ security
    • CVE-2026-34781 affects this package: high ▼ security
    • CVE-2026-70597 affects this package: high ▼ security
    • CVE-2026-113800 affects this package: high ▼ security
    • CVE-2026-34778 affects this package: high ▼ security
    • CVE-2026-70601 affects this package: high ▼ security
    • CVE-2026-70602 affects this package: high ▼ security
    • CVE-2026-114122 affects this package: high ▼ security
    • CVE-2026-102676 affects this package: high ▼ security
    • CVE-2026-70604 affects this package: high ▼ security
    • CVE-2026-34769 affects this package: high ▼ security
    • CVE-2026-34770 affects this package: high ▼ security
    • CVE-2026-34776 affects this package: high ▼ security
    • CVE-2026-34772 affects this package: high ▼ security
    • CVE-2026-70598 affects this package: high ▼ security
    • CVE-2026-34775 affects this package: high ▼ security
    • CVE-2026-70608 affects this package: high ▼ security
    • CVE-2026-113796 affects this package: high ▼ security
    • CVE-2026-70609 affects this package: high ▼ security
    • CVE-2026-70605 affects this package: high ▼ security
    • CVE-2026-102672 affects this package: high ▼ security
    • CVE-2026-115570 affects this package: high ▼ security
    • CVE-2026-102675 affects this package: high ▼ security
    • CVE-2026-34766 affects this package: high ▼ security
    • CVE-2026-70599 affects this package: high ▼ security
    • CVE-2026-70603 affects this package: high ▼ security
  • 1 Nov 26 +21

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • CVE-2026-34764 affects this package: high ▼ security
    • CVE-2026-34771 affects this package: high ▼ security
    • CVE-2026-34765 affects this package: high ▼ security
    • CVE-2026-70612 affects this package: high ▼ security
    • CVE-2026-113797 affects this package: high ▼ security
    • CVE-2026-34774 affects this package: high ▼ security
    • CVE-2026-114124 affects this package: high ▼ security
    • CVE-2026-70607 affects this package: high ▼ security
    • CVE-2026-102674 affects this package: high ▼ security
    • CVE-2026-114121 affects this package: high ▼ security
    • CVE-2025-55305 affects this package: high ▼ security
    • CVE-2026-70611 affects this package: high ▼ security
    • CVE-2026-70610 affects this package: high ▼ security
  • 31 Oct 26 −5

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 30 Oct 26 +6

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 29 Oct 26 −5

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

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 5 Nov 2026 · Analysed npm/@glittering0717/ai-browser@2.5.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 →

Vulnerabilities 48 findings
ID CVE Severity Vector Fix available
GHSA-2p8c-gr87-2676 CVE-2026-113796 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N yes
GHSA-3c8v-cfp5-9885 CVE-2026-34776 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:L yes
GHSA-3qxv-5xgr-q7w9 CVE-2026-114122 low CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:L yes
GHSA-4f78-qhmw-8j8m CVE-2026-70609 medium CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N yes
GHSA-4p4r-m79c-wq3v CVE-2026-34767 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:N yes
GHSA-532v-xpq5-8h95 CVE-2026-34774 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-5c9j-mhmv-5xgx CVE-2026-70603 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N yes
GHSA-5rqw-r77c-jp79 CVE-2026-34779 medium CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L yes
GHSA-8337-3p73-46f4 CVE-2026-34771 high CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H yes
GHSA-8x5q-pvf5-64mp CVE-2026-34764 low CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L yes
GHSA-9899-m83m-qhpj CVE-2026-34766 low CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N yes
GHSA-98mx-cjp9-gchm CVE-2026-113797 low CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N yes
GHSA-997q-gvvc-jwmx CVE-2026-114121 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N yes
GHSA-9f4c-93c8-jc8g CVE-2026-70608 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N yes
GHSA-9pf5-hg6p-4pwp CVE-2026-70599 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-9qh4-3jw8-366w CVE-2026-102676 high CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H yes
GHSA-9w97-2464-8783 CVE-2026-34772 medium CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:L yes
GHSA-9wfr-w7mm-pc7f CVE-2026-34769 high CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H yes
GHSA-f2r8-jv7c-xqmp CVE-2026-70611 medium CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N yes
GHSA-f37v-82c4-4x64 CVE-2026-34781 low CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L yes
GHSA-f3pv-wv63-48x8 CVE-2026-34765 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L yes
GHSA-ff2p-hmqr-hxm4 CVE-2026-70610 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N yes
GHSA-fw47-9c62-h3vw CVE-2026-113800 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N yes
GHSA-gr2m-v5gq-v685 CVE-2026-102674 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N yes
GHSA-h3v5-h239-pg29 CVE-2026-114124 low CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:L yes
GHSA-h7rp-cf8h-j98x CVE-2026-70601 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N yes
GHSA-hq2x-r82h-9wj4 CVE-2026-102673 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N yes
GHSA-j84w-jfhq-vhvj CVE-2026-102675 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N yes
GHSA-jfqx-fxh3-c62j CVE-2026-34768 low CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L yes
GHSA-jjp3-mq3x-295m CVE-2026-34770 high CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H yes
GHSA-jm7p-cc5g-qwxx CVE-2026-70597 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-jr5w-w6x2-84p9 CVE-2026-115570 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-m55f-7gqj-fr98 CVE-2026-70602 medium CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:N yes
GHSA-mwmh-mq4g-g6gr CVE-2026-34773 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N yes
GHSA-p2rr-rvmm-c5fp CVE-2026-70612 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N yes
GHSA-pfmc-3mgc-p6fp CVE-2026-70598 low CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:L yes
GHSA-r5p7-gp4j-qhrx CVE-2026-34777 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N yes
GHSA-v3j7-r9gq-3gjw CVE-2026-70604 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N yes
GHSA-v64r-4m7r-3mvq CVE-2026-70605 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-v93f-fgjr-hjrj CVE-2026-70607 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N yes
GHSA-vmqv-hx8q-j7mg CVE-2025-55305 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:L yes
GHSA-vv43-5jgx-7qv8 CVE-2026-102672 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H yes
GHSA-x562-297c-g43g CVE-2026-113798 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L yes
GHSA-x8rc-wpg4-grpf CVE-2026-70600 low CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N yes
GHSA-xj5x-m3f3-5x3h CVE-2026-34778 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N yes
GHSA-xwr5-m59h-vwqr CVE-2026-34775 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N yes
GHSA-7pqw-9j4j-h8q3 CVE-2026-19693 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H no
GHSA-jmr9-qjv8-65gv CVE-2026-56876 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N no

Background: What a vulnerability scan can and cannot prove →

Dependencies 158 packages
Packages resolved 158
Deprecated 1
Stale 61
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 17 exposed · ~2,061 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
browse_act ~348

Act on a data-ai-id element. type appends at caret, setContent replaces all. page_changed:false = dispatched but page unchanged (wrapper).

NameTypeReqDescription
actionstringyesVerb. Verb-specific params live in the group of the same name.
clickobject–click only.
dragobject–drag only. from/to = points, dx/dy = relative, target_to = drop onto an element.
filestring–upload: absolute path. target may be the input, the trigger, or a CSS selector.
htmlstring–paste: HTML, preferred (keeps headings/bold). landed_chars:null = unreadable.
pressobject–press only. Keys go to the current focus, so target is optional.
readobject–get_value only — read-only: does not focus the element or fire input events.
tabinteger–Tab id; omit → session default.
targetstring–data-ai-id from the tree (e.g. e:button-12) — NOT the visible label. Optional for press; drag may use drag.from; upload also takes a CSS selector.
textstring–type: appended at the caret. setContent: replaces all. paste: plain fallback when html is absent.
timeout_msinteger–Deadline ms (default 15000, 1s..300s). On timeout: success=false, timed_out=true, may have partially applied.
valuestring–Option value for a <select>.
wheelobject–wheel only. Lands on target, or the viewport centre when target is omitted.

No output schema declared.

No examples provided.

browse_auth_state ~64

Is this tab still logged in, or bounced to a login wall? auth_wall.detected=true means stop debugging and re-authenticate first. logged_in is heuristic; auth_wall is the signal to trust.

NameTypeReqDescription
tabinteger–Tab id; omit → session default.

No output schema declared.

No examples provided.

browse_canvas ~165

Read <canvas> via captured draw calls (not pixels): list, read texts/regions, configure, or capture a PNG fallback. 2D text comes from fillText, so no OCR; WebGL is opaque.

NameTypeReqDescription
canvas_idstring–read/capture: id from list.
clearboolean–configure: drop retained calls.
limitinteger–read: page size (default 200, max 1000).
modestring–configure: recording mode.
operationstringyesOperation.
since_seqinteger–read: cursor from pagination.next_seq.
tabinteger–Tab id; omit → session default.
viewstring–read: summary (default) or raw draw calls.

No output schema declared.

No examples provided.

browse_capabilities ~106

Probe how to operate a page: DOM vs canvas, iframes, app objects on window, JSON endpoints, plus a plan. deep=true also probes closure-hidden models (canvas editors that report none).

NameTypeReqDescription
deepboolean–Probe closure-hidden models too.
include_networkboolean–Include observed JSON-ish endpoints (default true).
network_limitinteger–How many captured requests to scan.
tabinteger–Tab id; omit → session default.

No output schema declared.

No examples provided.

browse_diff ~173

Prove an action changed the page: snapshot a baseline, then diff to get added/removed/changed paths with before/after values. Success is not evidence.

NameTypeReqDescription
forgetboolean–diff: drop the stored baseline when done.
jsstring–JSON-serializable expression to capture. Omit for a site-agnostic DOM summary (role/label/value/disabled/size per element).
labelstring–snapshot: a note for your own bookkeeping.
operationstringyesOperation.
rearmboolean–diff: make the current state the new baseline, so you can loop "assert no change" over many steps.
snapshotstring–diff: the id returned by snapshot.
tabinteger–Tab id; omit → session default.

No output schema declared.

No examples provided.

browse_downloads ~54

List a tab's downloads with on-disk paths. Downloads are async: poll this after clicking export/download instead of expecting the path in the click response.

NameTypeReqDescription
tabinteger–Tab id; omit → session default.

No output schema declared.

No examples provided.

browse_errors ~95

Read the main-process error log: uncaught exceptions, crashes, failed navigations, RPC errors. Each entry includes recent calls as context. Returns the on-disk JSONL path.

NameTypeReqDescription
kindstring–Filter by kind: uncaught_exception / unhandled_rejection / render_process_gone / child_process_gone / nav_fail / ws_error.
limitinteger–Max entries to return (default 50).

No output schema declared.

No examples provided.

browse_evaluate ~129

Run a JS expression in the page context and return its value. Promises are awaited (async IIFEs return their resolved value, not {}).

NameTypeReqDescription
frame_refstring–Run inside this cross-process frame (an axf-... id from the tree). Pass it explicitly when touching iframe content: building the selector by string concatenation defeats the automatic route and the t…
jsstringyesPage-context JS expression (not statements). Max 5000 chars. Promises are awaited.
tabinteger–Tab id; omit → session default.

No output schema declared.

No examples provided.

browse_get_tree ~111

Return the page semantic tree (roles, labels, actions, bounds). Root adds editors (primary) when 2+ editable.

NameTypeReqDescription
axboolean–Use the AX read layer (links carry url).
focused_onlyboolean–Return only the focused element subtree.
modestring–Return only new/hidden interactive nodes since last read.
subsetstring–Prune layout-only branches (token saver).
tabinteger–Tab id; omit → session default.

No output schema declared.

No examples provided.

browse_navigate ~123

Navigate your tab to a URL. Returns at the requested milestone (default: DOM ready) — it does not wait for load, which SPAs often never fire.

NameTypeReqDescription
tabinteger–Tab id; omit → session default.
urlstringyesURL to navigate to.
wait_untilstring–How far to wait. commit = navigation committed (fastest, content may not be painted); domcontentloaded = DOM ready (default, safe for SPAs); load = also subresources (can hang forever on pages that n…

No output schema declared.

No examples provided.

browse_network ~130

Query captured HTTP requests: list/get/clear/configure. Captures headers and POST bodies; sensitive headers redacted. Each op reads its own group: filters / include / body_offset / configure.

NameTypeReqDescription
body_offsetobject–get only — paginate a large body.
configureobject–configure only.
filtersobject–list only.
includeobject–get only — what to bring back.
network_idstring–get: id from list.
operationstringyesOperation.
tabinteger–Tab id; omit → session default.

No output schema declared.

No examples provided.

browse_quit ~21

Gracefully shut down the AI Browser (releases resources).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

browse_repaint ~51

Force the compositor to redraw a tab's BrowserView when the window shows a stale page; returns repaint_count so the repaint is provable.

NameTypeReqDescription
tabinteger–Tab id; omit → session default.

No output schema declared.

No examples provided.

browse_screenshot ~180

Screenshot the viewport (base64). Use FIRST when an action misbehaves: the tree cannot show overlays, canvas, occlusion or glitches. Warns about visible password inputs.

NameTypeReqDescription
clipobject–Capture a rectangle in CSS pixels: {x, y, width, height, scale?}. Use to zoom into one element when the viewport shot is too small to read.
formatstring–Image format. Default png. jpeg at quality 85 is ~5x smaller — prefer it for long pages.
fullPageboolean–Capture the full scrollable page, not just the viewport. Cannot be combined with clip.
qualitynumber–0-100, jpeg/webp only (ignored for png). Default 85 for jpeg.
tabinteger–Tab id; omit → session default.

No output schema declared.

No examples provided.

browse_scroll ~65

Scroll the page or an element into view.

NameTypeReqDescription
amountinteger–Pixels (ignored if target set).
directionstring––
tabinteger–Tab id; omit → session default.
targetstring–data-ai-id to scroll into view.

No output schema declared.

No examples provided.

browse_tabs ~154

Tabs: list/new/close/switch/window. Yours are grouped and capped. switch = default; add show:true. new never steals the view unless show:true. window = hide/show.

NameTypeReqDescription
opstringyeslist = every tab; new = open; close = close; switch = default; window = hide/show.
showboolean–new: bring it to the front (default: background); switch: same (default: false).
tabinteger–close / switch: the target tab id; omit → session default.
urlstring–new: open at this URL (default about:blank).
visibleboolean–window: true = show, false = hide.

No output schema declared.

No examples provided.

browse_wait ~92

Poll the page until a condition holds or timeout. Conditions: button_enabled, modal_appeared, text_contains, url_contains.

NameTypeReqDescription
conditionstringyes–
tabinteger–Tab id; omit → session default.
targetstring–Button label (button_enabled).
textstring–Text/URL fragment (text_contains / url_contains).
timeout_msinteger––

No output schema declared.

No examples provided.

Install

How do I install the io.github.Glittering/ai-browser MCP server?

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

npm · @glittering0717/ai-browser

# add to Claude Code
claude mcp add glittering-ai-browser -- npx -y @glittering0717/ai-browser
Common questions

What is the io.github.Glittering/ai-browser MCP server?

io.github.Glittering/ai-browser is an MCP server listed in the public MCP registry as io.github.Glittering/ai-browser. Visible Electron browser driven by a semantic accessibility tree: 17 MCP tools, no screenshots. This page covers its npm package (@glittering0717/ai-browser).

Is the io.github.Glittering/ai-browser MCP server safe to use?

io.github.Glittering/ai-browser scores 71 out of 100 on VerifyMCP. We recorded 48 known advisories against it as of 5 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.Glittering/ai-browser MCP server expose?

io.github.Glittering/ai-browser exposes 17 tools: browse_navigate, browse_get_tree, browse_act, browse_evaluate, browse_scroll, and 12 more. Their descriptions and schemas cost roughly 2,061 tokens of context every time the server is loaded.

Is the io.github.Glittering/ai-browser MCP server still maintained?

io.github.Glittering/ai-browser is still listed as active in the MCP registry. We last reached this channel on 5 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.Glittering/ai-browser MCP server under?

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