WaveXisMCP
Infrastructure · tested 2026-08-14 · by the Hlido desk, not the vendor
In short: 220 browser-automation tools with the documentation to match — installation, architecture, security, rate limiting, benchmarks and a comparison table that names its main rival and concedes where it loses.
Quick answer
WaveXisMCP scores 81/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-08-14). STEADY and near the top of the band because nearly everything a buyer needs is published and checkable: version, architecture, security page, rate limiting, benchmarks, full tool reference, changelog and an honest compet Pricing: Open source (free entry point documented).
WaveXisMCP is the best-documented tool in this batch by a wide margin. The docs site carries installation, quick start, configuration, architecture, capability tiers, HTTP transport, Docker, stealth mode, resources and prompts, rate limiting, security, troubleshooting, benchmarks, a full tool reference organised into 13 tiers, a cookbook of worked recipes, tutorials, a Python API reference, contributing guidance and a changelog. The version (v1.6.24) is displayed in the header. That is a reference surface a buyer or an agent can genuinely evaluate against, and it is why this review carries high confidence where most of its peers carry low. The product position is also concrete: 100% Python with no Node.js dependency and no Chromium download, driving your existing Chrome or Edge over CDP or BiDi. The docs include a direct comparison table against Playwright MCP that names the trade-offs rather than only the wins — unusual candour. The honest caveat is the tool count itself: 220 tools across 13 tiers is a very large surface to expose to an LLM, and tool-definition volume is a real cost in agent context budgets. The capability-tier structure appears designed to address exactly that, but the docs describe the tiers as an organising principle without quantifying the context saving. A worked example of a tier-limited configuration and its token cost would close the last gap on an otherwise exemplary surface.
Why STEADY
STEADY and near the top of the band because nearly everything a buyer needs is published and checkable: version, architecture, security page, rate limiting, benchmarks, full tool reference, changelog and an honest competitive comparison. Held out of the highest band because the very large tool surface (220) creates an agent context cost that the documentation organises for but does not quantify, and because the benchmarks and stealth-mode features are presented without independent corroboration.
What we saw
4 screenshots captured by the Hlido engine during the reviewed run (run-8414d0a4cf0f6981-mathiaspaulenko-github-io). Our own captures — not vendor marketing material.
What it does well
- Documentation depth is exceptional — installation through architecture, security, rate limiting, benchmarks and a full tool reference
- Version displayed prominently (v1.6.24) with a maintained changelog
- Publishes a direct comparison against Playwright MCP that concedes trade-offs instead of only claiming wins
- Clear technical position: no Node.js, no Chromium download, drives the browser you already have
- Capability tiers give a real mechanism for limiting the exposed tool surface
- Dedicated security and rate-limiting pages — rare for an open-source MCP server
What it fails at
- 220 tools is a large definition payload for an LLM context, and the docs do not quantify what tier-limiting actually saves
- Benchmarks are self-published with no independent corroboration
- 'Stealth mode' is documented as a feature without discussing the acceptable-use questions it raises
- Requires an existing Chrome or Edge install, which constrains headless and container deployments in ways not fully drawn out
- No hosted or managed option; all operational burden sits with the user
Red flags
- 'Stealth mode' is a documented feature for evading bot detection. It is disclosed openly, but the docs do not address the terms-of-service and acceptable-use questions that follow from using it.
- Benchmarks are published by the maintainer with no third-party verification, so they should be read as vendor claims.
Best for
- Python teams wanting browser automation for LLMs without adding a Node.js toolchain
- Users who need deep browser capability (video, vision, a11y, DevTools, network) from one server
- Engineers who evaluate on documentation quality — there is more here than almost any peer publishes
- Deployments where driving an existing managed Chrome/Edge install is preferable to bundling Chromium
Not recommended for
- Context-constrained agent setups that cannot afford a large tool-definition payload without careful tier configuration
- Environments where no Chrome or Edge install exists and cannot be provisioned
- Teams wanting a hosted service rather than a self-operated server
Pricing & access
- ModelOpen source
- Free entry pointYes — a free tier or open-source edition is documented
Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-11.
Compared to
-
Microsoft Playwright MCP
python-native-and-tool-depth
Playwright MCP is first-party, TypeScript, and bundles its own browser; WaveXisMCP is Python-native, uses your existing browser and exposes far more tools. The project publishes this comparison itself and is fair about it. Choose on language and tool-depth needs.
-
Periscope MCP (Segentic Lab)
published-documentation
Periscope shares the Python-native browser-QA idea but publishes almost nothing; WaveXisMCP publishes almost everything. Same family, opposite ends of assessability.
-
Browser Use
autonomy-vs-control
browser-use aims at autonomous task completion; WaveXisMCP is a tool surface the model orchestrates itself. Choose browser-use for 'do this task', WaveXisMCP for precise programmatic control.
Agent relevance
API MCP SDK Behavioral-testable
Agentic-Commerce Readiness 62/100 · INTEGRABLE
Independent readiness for agent delegation & transaction. How it’s scored · check live
MCP server with 220 documented tools in 13 capability tiers, an HTTP transport alongside stdio, a documented Python API and named client support (Claude Desktop, Cursor, Windsurf, VS Code). The published tool reference means an agent can reason about capability before connecting; tier selection is the lever for keeping the definition payload manageable.
Agent-friendly score: 9/10
Score over time
The longitudinal record — every point is the score as published on that date. Raw series.
Evidence
- Homepage publicly accessible and value proposition clearly stated — source (2026-08-14) verified
- Pricing page discoverable in 2 clicks from homepage — source (2026-08-14)
- Documentation or live demo accessible without login — source (2026-08-14) verified
- Integration list or supported frameworks documented — source (2026-08-14) verified
- Authentication / data handling claims publicly stated — source (2026-08-14) verified
scorecard.json · transparency passport · registry · methodology
Embed this trust badge
Markdown
[](https://hlido.eu/check/?agent=mathiaspaulenko-wavexis-mcp)HTML
<a href="https://hlido.eu/check/?agent=mathiaspaulenko-wavexis-mcp"><img src="https://hlido.eu/badge/mathiaspaulenko-wavexis-mcp.svg" alt="Hlido trust score"></a>