Browser Use
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Description from the maker (original English)
Read any page past its anti-bot wall, crawl sites, search without an API key, solve captchas locally
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"svipall": {
"command": "npx",
"args": [
"-y",
"svipall"
]
}
}
}Run this in your terminal
claude mcp add svipall -- npx -y svipallPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"svipall": {
"command": "npx",
"args": [
"-y",
"svipall"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"svipall": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"svipall"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified against the domain svipall.ilien.dev (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.3.1) reached the registry 37 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker, Rust on your computer.
In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A different face at every gate.
Web reading for your AI agent, running on your own machine.
An MCP server and CLI, in Rust, that extracts web pages into Markdown,
crawls sites within configured limits, searches without an API key,
and attempts supported challenges, then says plainly which ones it could not.
Install · Use cases · Proof · Tools · Captcha · REST API · Compare · FAQ
Replayed from real runs on one machine. How it was recorded, and the raw captures .
Everything runs locally. There are no third-party API keys, no paid captcha services and no telemetry. Web requests reach the sites you visit, and results reach the agent or client you connect.
Svipall fetches and renders pages locally, extracts their content, and reports detected challenges and extraction-quality labels. Some sites still block it, and an apparently successful response can contain incomplete records or a page shell. The published comparisons therefore audit useful content separately from HTTP status and the tool's own verdict.
| What goes wrong | Svipall |
|---|---|
Your agent reads a "checking your browser" screen and summarises it as the article. It was a 200, so nothing flagged it | Twelve wall kinds, each naming the move it implies. Detected blocks carry an explicit verdict; classification is heuristic details |
| You crawl 5,000 pages and can't tell which are worth keeping | Assessed pages carry quality and duplicate observations, and quality labels never discard a page details |
| One page = 300,000 tokens of raw HTML. The fixes are four manual jobs you now own | Clean Markdown by default; opt into tables as rows, out_file to disk, or capture of the site's own JSON API details |
| You want to attempt a supported captcha without a paid solver | Fifteen widget families and eleven answer modalities, all local, optional vision models depending on the build, and a human dashboard for unresolved challenges details |
It records successful visits, failures, incomplete extraction and rejected changes. Historical benchmark logs and the current comparison use different scoring rules and configurations; the results section distinguishes them.
Rust · MCP + CLI + REST · no Node, no Python, no API key · local storage and processing
[Install it](#install)
The comparison table describes other projects' documented scope.
Every channel below installs the latest release, built from the tree this README describes. svipall doctor reports what an installed build can do on the machine it is on.
The README factual audit records the source checks, documentation corrections and limits of this review.
Choose agent-assisted setup, the Claude Code plugin, or a manual installation.
Paste this into Claude Code, Cursor, Codex, opencode, or anything else that can run a command:
Install and configure Svipall by following the instructions here:
https://raw.githubusercontent.com/ilien-dev/svipall/main/docs/install.md
That page guides an agent through platform detection and verification, then asks which integration you want: CLI + Skill (recommended, lower context use) or MCP + Skill (the full MCP tool surface). It also asks whether to configure every project or only the current one, and verifies the chosen result instead of treating a skill as MCP registration. When Svipall already exists, it shows the installed and latest versions and asks whether to update the shared user installation or keep the current version before it writes the integration. Completion depends on the agent, client configuration and available permissions.
/plugin marketplace add ilien-dev/svipall
/plugin install svipall@svipall /svipall:setup
/svipall:setup installs the binary if it is missing, checks the server answers, and offers to make Svipall the way Claude reaches the web in every project. It asks before each of those. /svipall:doctor reports the installation's capabilities. /svipall:update shows the installed and latest releases, then updates the binaries only if you choose to. /svipall:uninstall offers removal of setup's registration, memory and strict-mode changes. Removing the binary and the data are separate choices.
One line, with no toolchain and nothing to compile:
curl -fsSL https://raw.githubusercontent.com/ilien-dev/svipall/main/install.sh | sh # macOS, Linux
irm https://raw.githubusercontent.com/ilien-dev/svipall/main/install.ps1 | iex # Windows
Or a package manager, or the container image:
brew install ilien-dev/svipall/svipall # macOS, Linux
scoop bucket add svipall https://github.com/ilien-dev/scoop-svipall && scoop install svipall docker pull ghcr.io/ilien-dev/svipall:latest # or :slim, the http tier only; see container notes npx --yes svipall doctor # if node is already there cargo install svipall # from source; add svipall models install for the models
The installers verify checksums where they can, and a mismatch stops the install. A missing checksum file, entry or hashing utility only warns, so a successful exit is not by itself proof the archive was verified: read the output. If the destination already contains another version, the installer states that the binaries are shared by every harness and asks before replacing them.
When a newer release exists, Svipall says so once per session. One command updates both binaries with the channel that installed them and refreshes the skills you copied by hand:
svipall update # --check only compares versions
Then close every session that uses Svipall and open it again. An agent can do the same from docs/update.md.
Platform builds, what ships where, building from source and wiring it into any MCP client are all in docs/install.md. If you have never installed anything from a terminal, GET-STARTED.md is this section with nothing assumed.
There is no key to paste and no account to create.
*"Read this page and summarise the pricing."*
*"Crawl these docs and write me an
llms.txt."*
*"Watch this listing and tell me when the price moves."*
*"Get me every row of that table as CSV."*
The assistant can choose among the exposed tools. Supported challenges that need a pair of eyes go to a human dashboard at http://localhost:8787/human.
svipall fetch https://example.com/article
svipall fetch https://shop.example/item --query "shipping costs" svipall fetch https://docs.example/api --schema auto # rows from a listing you've never seen svipall crawl https://docs.example/ --pages 50 --out pages.csv svipall search "rust async runtime" --engine all svipall snapshot https://news.ycombinator.com # the page as roles and refs, not markup svipall serve --port 8788 # the same server as a local REST API
Completed data commands print one JSON object to stdout and diagnostics to stderr, so the output can be piped to jq. serve is a long-running server, and help is written to stderr.
A historical run of svipall fetch https://example.com, with the content string cut short. Current automatic fetches also report identity_used, and the fallback fields described below when they have something to report:
{
"attempts": ["http: 200 (170ms) OK"], "chars": 167, "content": "# Example Domain\n\nThis domain is for use in documentation examples…", "final_url": "https://example.com/", "optimization": "ordinary", "quality": "thin", "quality_reasons": ["thin_text"], "status": 200, "tier_used": "http", "title": "Example Domain", "tokens_estimated": 42, "url": "https://example.com" }
tier_used says how hard it had to try and quality says what actually arrived. When a page does not arrive, the same object carries blocked_reason, wall_kind, wall_vendor, wall_evidence and a note telling your agent what to do next. Straight from a committed benchmark record:
{ "wall_kind": "vendor", "wall_vendor": "kpsdk.io", "wall_evidence": "header x-kpsdk-ct" }
A detected block carries a verdict alongside the returned content. A clear verdict still needs a content check, because the classifier cannot show that the requested records arrived intact.
| You want to… | It looks like this |
|---|---|
| Read one page cleanly | web_fetch → Markdown with heuristic boilerplate removal and sanitization; query= ranks text by lexical relevance |
| Turn a listing into rows | schema: "auto" reads the page's own repeated structure, names the columns and hands back typed rows, with no model and no API call, in one parse |
| Pull a data table | tables=true → typed rows; out_file: rows.csv writes them to disk so thousands of rows never touch your context |
| Read what a video says | web_video → captions and chapters as one [m:ss] timeline, from a watch page, a page that embeds a player, tracks or the stream manifest |
| Skip the scraping entirely | web_capture returns the JSON the page fetched while loading, usually the site's real API, with ?page=2 waiting for you |
| Turn a docs site into a corpus | web_crawl with llms.txt output, near-duplicate labels, resumable frontier and lexical saturation stopping, subject to page/t
Only the beginning is shown; read the rest in the repo