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.bytedance/mcp-server-browser

NPM · @AGENT-INFRA/MCP-SERVER-BROWSER

MCP server for browser use access

0 this week 58 Trust /100

Last scanned (18 hours ago)

Scores higher than 29% 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 Security50
  • No malware found by supply-chain analysis.Pass
  • Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency34
Schema Quality & AI Usability43
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 884 tokens (~40/item across 22 items; 21 tools + 1 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 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
  • Structured output schemas are declared (14% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "browser_evaluate" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • Malware scan
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (3)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Known CVEs in Supply Chain SecurityKnown CVEs could not be checked: the version this server declares is not published in its registry.
  • Install scripts in Supply Chain SecurityInstall-script risk not yet assessed.
  • Dependency health in Supply Chain SecurityDependency health could not be checked: the version this server declares is not published in its registry.

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.

  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 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.

  • 8 Nov 26 −1
    • Stability: pass → 0.87 functional
  • 2 Nov 26 0
    • Stability: 0.97 → pass security
  • 1 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.

  • 31 Oct 26 −1
    • 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/@agent-infra/mcp-server-browser@latest

Provenance Version not published

The package exists but this version is not published, so there is no artifact to attest.

Result Version not published
Ecosystem npm

Background: How many MCP packages publish verified provenance →

MCP tools · 21 exposed · ~878 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
browser_click ~62

Click an element on the page, before using the tool, use `browser_get_clickable_elements` to get the index of the element, but not call `browser_get_clickable_elements` multiple times

NameTypeReqDescription
indexnumber–Index of the element to click

No output schema declared.

No examples provided.

browser_close ~24

Close the browser when the task is done and the browser is not needed anymore

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

browser_close_tab ~14

Close the current tab

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

browser_evaluate ~36

Execute JavaScript in the browser console

NameTypeReqDescription
scriptstringyesJavaScript code to execute, () => { /* code */ }

No output schema declared.

No examples provided.

browser_form_input_fill ~95

Fill out an input field, before using the tool, Either 'index' or 'selector' must be provided

NameTypeReqDescription
clearboolean–Whether to clear existing text before filling
indexnumber–Index of the element to fill
selectorstring–CSS selector for input field, priority use index, if index is not provided, use selector
valuestringyesValue to fill

No output schema declared.

No examples provided.

browser_get_clickable_elements ~32

Get the clickable or hoverable or selectable elements on the current page, don't call this tool multiple times

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

browser_get_download_list ~17

Get the list of downloaded files

Input schema present but exposes no named parameters.

NameTypeReqDescription
listarrayyes–

No examples provided.

browser_get_markdown ~19

Get the markdown content of the current page

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

browser_get_text ~18

Get the text content of the current page

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

browser_go_back ~16

Go back to the previous page

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

browser_go_forward ~16

Go forward to the next page

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

browser_hover ~53

Hover an element on the page, Either 'index' or 'selector' must be provided

NameTypeReqDescription
indexnumber–Index of the element to hover
selectorstring–CSS selector for element to hover

No output schema declared.

No examples provided.

browser_navigate ~21

Navigate to a URL

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

browser_new_tab ~28

Open a new tab

NameTypeReqDescription
urlstringyesURL to open in the new tab

No output schema declared.

No examples provided.

browser_press_key ~145

Press a key on the keyboard

NameTypeReqDescription
keystringyesName of the key to press or a character to generate, such as Enter, Tab, Escape, Backspace, Delete, Insert, F1, F2, F3, F4, F5, F6, F7, F8, F9, F10, F11, F12, ArrowLeft, ArrowRight, ArrowUp, ArrowDow…

No output schema declared.

No examples provided.

browser_read_links ~17

Get all links on the current page

Input schema present but exposes no named parameters.

NameTypeReqDescription
linksarrayyes–

No examples provided.

browser_screenshot ~113

Take a screenshot of the current page or a specific element

NameTypeReqDescription
fullPageboolean–Full page screenshot (default: false)
heightnumber–Height in pixels (default: viewport height)
highlightboolean–Highlight the element
indexnumber–index of the element to screenshot
namestring–Name for the screenshot
selectorstring–CSS selector for element to screenshot
widthnumber–Width in pixels (default: viewport width)

No output schema declared.

No examples provided.

browser_scroll ~45

Scroll the page

NameTypeReqDescription
amountnumber–Pixels to scroll (positive for down, negative for up), if the amount is not provided, scroll to the bottom of the page

No output schema declared.

No examples provided.

browser_select ~65

Select an element on the page with index, Either 'index' or 'selector' must be provided

NameTypeReqDescription
indexnumber–Index of the element to select
selectorstring–CSS selector for element to select
valuestringyesValue to select

No output schema declared.

No examples provided.

browser_switch_tab ~27

Switch to a specific tab

NameTypeReqDescription
indexnumberyesTab index to switch to

No output schema declared.

No examples provided.

browser_tab_list ~15

Get the list of tabs

Input schema present but exposes no named parameters.

NameTypeReqDescription
tabListarrayyes–

No examples provided.

Install

How do I install the io.github.bytedance/mcp-server-browser server?

io.github.bytedance/mcp-server-browser runs locally as an npm package, launched with npx -y @agent-infra/mcp-server-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 · @agent-infra/mcp-server-browser

# add to Claude Code
claude mcp add bytedance-mcp-server-browser -- npx -y @agent-infra/mcp-server-browser
Common questions

What is the io.github.bytedance/mcp-server-browser server?

io.github.bytedance/mcp-server-browser is listed in the public MCP registry as io.github.bytedance/mcp-server-browser. MCP server for browser use access. This page covers its npm package (@agent-infra/mcp-server-browser).

Is the io.github.bytedance/mcp-server-browser server safe to use?

io.github.bytedance/mcp-server-browser scores 58 out of 100 on VerifyMCP. 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.bytedance/mcp-server-browser server expose?

io.github.bytedance/mcp-server-browser exposes 21 tools: browser_navigate, browser_go_back, browser_go_forward, browser_form_input_fill, browser_get_markdown, and 16 more. Their descriptions and schemas cost roughly 878 tokens of context every time the server is loaded.

Is the io.github.bytedance/mcp-server-browser server still maintained?

io.github.bytedance/mcp-server-browser 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 did VerifyMCP test on the io.github.bytedance/mcp-server-browser server?

VerifyMCP ran 13 checks on io.github.bytedance/mcp-server-browser, covering Malware scan, Source repository, Provenance, License and 9 more. 3 items could not be completed, a gap on our side rather than a finding about io.github.bytedance/mcp-server-browser: Known CVEs, Install scripts and Dependency health. 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.