Operative AI - WebAgentEval Agent
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"iflow-mcp-operative-sh-web-eval-agent","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# ⚠️ PROJECT HAS BEEN SUNSET ⚠️ ## This project has been discontinued. We're building something new at [withrefresh.com](https://withrefresh.com) --- # 🚀 operative.sh web-eval-agent MCP Server > *Let the coding agent debug itself, you've got better things to do.*  ## 🔥 Supercharge Your Debugging [operative.sh](https://www.operative.sh/mcp)'s MCP Server launches a browser-use powered agent to autonomously execute and debug web apps directly in your code editor. ## ⚡ Features - 🌐 **Navigate your webapp** using BrowserUse (2x faster with operative backend) - 📊 **Capture network traffic** - requests are intelligently filtered and returned into the context window - 🚨 **Collect console errors** - captures logs & errors - 🤖 **Autonomous debugging** - the Cursor agent calls the web QA agent mcp server to test if the code it wrote works as epected end-to-end. ## 🧰 MCP Tool Reference | Tool | Purpose | |------|---------| | `web_eval_agent` | 🤖 Automated UX evaluator that drives the browser, captures screenshots, console & network logs, and returns a rich UX report. | | `setup_browser_state` | 🔒 Opens an interactive (non-headless) browser so you can sign in once; the saved cookies/local-storage are reused by subsequent `web_eval_agent` runs. | **Key arguments** * `web_eval_agent` * `url` **(required)** – address of the running app (e.g. `http://localhost:3000`) * `task` **(required)** – natural-language description of what to test ("run through the signup flow and note any UX issues") * `headless_browser` *(optional, default `false`)* – set to `true` to hide the browser window * `setup_browser_state` * `url` *(optional)* – page to open first (handy to land directly on a login screen) You can trigger these tools straight from your IDE chat, for example: ```bash Evaluate my app at http://localhost:3000 – run web_eval_agent with the task "Try the full signup flow and report UX issues". ``` ## 🏁 Quick Start ### Easy Setup wit…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.