MCP server that scans web pages for WCAG accessibility issues with axe-core, so AI agents can audit and fix accessibility. By
Chrome Browser is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open InstallationWhat it does
MCP server for Chrome browser control via CDP - 通过 MCP 协议控制 Chrome 浏览器
Quickstart
# 1 — run it from where its publisher ships it
npx -y chrome-browser-mcp
# 2 — the plan is chosen at checkout, in the browser
# 3 — ask your agent something
> MCP server for Chrome browser control via CDP - 通过 MCP 协议控制 Chrome 浏览器
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Chrome Browser as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add chrome-browser-mcp -- npx -y chrome-browser-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
35 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
连接到已运行的 Chrome 浏览器(需要以 --remote-debugging-port=9222 启动)
Takes no parameters.
断开与浏览器的连接
Takes no parameters.
获取浏览器连接状态
Takes no parameters.
列出所有打开的页面
Takes no parameters.
打开新页面
Takes no parameters.
附加到指定页面
Takes no parameters.
关闭当前页面
Takes no parameters.
导航到指定 URL
Takes no parameters.
后退
Takes no parameters.
前进
Takes no parameters.
刷新页面
Takes no parameters.
获取页面 HTML
Takes no parameters.
获取页面文本内容
Takes no parameters.
获取页面完整快照(HTML、文本、DOM 结构)
Takes no parameters.
查询页面元素
Takes no parameters.
查询所有匹配的页面元素
Takes no parameters.
截取页面截图
Takes no parameters.
设置视口大小
Takes no parameters.
在页面中执行 JavaScript 代码
Takes no parameters.
运行测试代码(支持 describe/it/expect 语法)
Takes no parameters.
注入外部脚本
Takes no parameters.
注入 CSS 样式
Takes no parameters.
获取页面全局变量列表
Takes no parameters.
获取控制台消息
Takes no parameters.
获取网络请求记录
Takes no parameters.
列出已安装的扩展程序
Takes no parameters.
获取扩展程序详细信息
Takes no parameters.
启用扩展程序
Takes no parameters.
禁用扩展程序
Takes no parameters.
重新加载扩展程序
Takes no parameters.
在扩展程序上下文中执行代码
Takes no parameters.
获取扩展程序存储数据
Takes no parameters.
设置扩展程序存储数据
Takes no parameters.
设置当前活动会话
Takes no parameters.
列出所有活动会话
Takes no parameters.
- 10,000 calls a month, included
- 120 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
- 50,000 calls a month, included
- 600 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
- 250,000 calls a month, included
- 3,000 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
No call is billed on its own, and this plan carries no monthly call limit. $12 a month covers every tool at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (35 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| browser_connect | no tags | |
| browser_disconnect | no tags | |
| browser_status | no tags | |
| page_list | no tags | |
| page_open | no tags | |
| page_attach | no tags | |
| page_close | no tags | |
| page_navigate | no tags | |
| page_back | no tags | |
| page_forward | no tags | |
| page_reload | no tags | |
| page_get_html | no tags | |
| page_get_text | no tags | |
| page_get_snapshot | no tags | |
| page_query_selector | no tags | |
| page_query_selector_all | no tags | |
| page_screenshot | no tags | |
| page_set_viewport | no tags | |
| js_execute | no tags | |
| js_run_tests | no tags | |
| js_inject_script | no tags | |
| js_inject_styles | no tags | |
| js_get_globals | no tags | |
| monitor_console | no tags | |
| monitor_network | no tags | |
| extension_list | no tags | |
| extension_get_info | no tags | |
| extension_enable | no tags | |
| extension_disable | no tags | |
| extension_reload | no tags | |
| extension_execute | no tags | |
| extension_get_storage | no tags | |
| extension_set_storage | no tags | |
| session_set | no tags | |
| session_list | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 1.0.1 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
No release note was published with this version.
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Writing one takes an account with at least 50 real tool calls against Chrome Browser in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.