WEBMCP.COM

WindTunnel. An open benchmark for WebMCP.

WindTunnel compares WebMCP with other ways browser agents interact with websites.

Tasks solved
48/49
solved by every WebMCP configuration
+11.6% vs the median screen-driving agent (43 of 49)
Faster
3–5×
task completion
7.8s vs 28.1s median per task
Less cost
4–23×
per task
0.6 cents vs 5.5 cents median per task
Final score
+39%
higher median final score
91.2 vs 65.8 for screen-driving agents

Leaderboard

Rank Configuration Interface Final score Tasks solved Attempt success Median costper task Median tokensper task Median timeper task
1GPT-5.6 Luna · nativeWebMCP98.448/49143/147 (97.3%)$0.0022,5965.7s
2Gemini 3.6 Flash · nativeWebMCP94.048/49144/147 (98.0%)$0.0044,4537.2s
3Gemini 3.6 Flash · Stagehand v4WebMCP92.748/49143/147 (97.3%)$0.0044,3718.0s
4Sonnet 5 · nativeWebMCP91.248/49144/147 (98.0%)$0.0095,1726.8s
5Sonnet 5 · Stagehand v4WebMCP89.548/49144/147 (98.0%)$0.0105,1618.1s
6GPT-5.6 SOL · nativeWebMCP86.348/49142/147 (96.6%)$0.0122,5739.3s
7Claude Opus 5 · nativeWebMCP86.048/49144/147 (98.0%)$0.0144,7709.8s
8GPT-5.6 LunaComputer use75.245/49134/147 (91.2%)$0.01720,91418.3s
9GPT-5.6 LunaDOM + vision70.043/49130/147 (88.4%)$0.03329,56119.8s
10GPT-5.6 LunaAccessibility tree69.840/49119/147 (81.0%)$0.02018,51716.0s
11Gemini 3.6 FlashComputer use67.343/49130/147 (88.4%)$0.02023,85733.7s
12GPT-5.6 SOLComputer use65.846/49134/147 (91.2%)$0.06316,23527.3s
13Sonnet 5DOM + vision64.248/49145/147 (98.6%)$0.21064,42429.3s
14Sonnet 5Accessibility tree62.742/49128/147 (87.1%)$0.03810,76237.5s
15Sonnet 5Computer use57.839/49119/147 (81.0%)$0.07057,70131.7s
16Claude Opus 5Computer use56.645/49134/147 (91.2%)$0.13947,14150.4s

Final score: The final score combines attempt success rate (60%), median cost per task (20%), and median agent time per task (20%). Cost and time are log-normalized (large differences are compressed so extreme values do not dominate); higher is better. Tokens are shown separately and are not scored twice.

Methodology

We operate eight real websites across a wide range of tasks — 49 tasks, three attempts each. There are three ways to operate the website:

WEBMCP

Tool calling

The website exposes direct actions for the agent to call.

SCREENSHOTS

Computer use

The agent reads rendered images of the page and acts by coordinate.

PAGE STRUCTURE

DOM

The agent reads the page's DOM and accessibility tree.

Everything is fully reproducible — the methodology, code, task definitions, and full run transcripts are on github.com/nekuda-ai/WindTunnel.