BrowserOps MCP

Browser runs and UI verification

BrowserOps MCP captures screenshots, console failures, network failures, and visible-page assertions through an isolated hosted browser runtime.

Included with an active usage plan

Browser verification uses the frozen browser operation class. Screenshot storage and disclosed provider expenses are metered separately.

Compare usage plans

Why it exists

Capture screenshots, console failures, network failures, and visible-page assertions from an isolated browser run.

Generic terminals, provider APIs, and custom prompts can cover parts of the work, but the caller must supply permission limits, output requirements, failure handling, and usage accounting.

Connection and contract

Connect from an MCP-aware client with an account-scoped Monarchic key. The hosted route checks access, runs the named product contract, and records the operation on the account receipt.

The product-specific schema defines the inputs and outputs used by clients and downstream automation.

Current limits

BrowserOps does not bypass access controls, CAPTCHAs, or site policy. Authenticated browsing requires an approved credential flow.

Requires an authenticated, entitled account. The browser task receives only the bounded request context supplied for this call.

What you get

Capture screenshots and browser logs for UI reviews
Check visible content, console output, and network failures
Package screenshots and observations for handoff

Core use case

Capture screenshots, console failures, network failures, and visible-page assertions from an isolated browser run.

Outcomes

Turn UI claims into reviewable browser observations
Attach screenshots to design and release reviews
Catch visible regressions, console errors, and failed requests

Primary workflows

Observe a URL Verify a page Capture screenshots Inspect console and network

Concrete workflow / priced call

Open a page and return browser observations

The request, exact tool-call payload, returned output, and usage receipt are shown below.

Request

“Check the example page and return what a browser can actually observe.”

Execution

Tool call payload

{
  "tool": "browser_observe_url",
  "arguments": {
    "url": "https://example.com",
    "safety_boundaries": [
      "no credential theft",
      "no CAPTCHA bypass",
      "no stealth scraping",
      "no unrestricted automation",
      "bounded task context required"
    ]
  }
}

Starts an isolated browser task, loads one bounded URL, and returns an observation receipt with the page state and runtime failures.

Output

Representative contract excerpt

{
  "contract": "browserops.observation_receipt.v1.0",
  "url": "https://example.com/",
  "title": "Example Domain",
  "status": "observed",
  "evidence": {
    "screenshotCaptured": true,
    "consoleErrors": 0,
    "failedRequests": 0
  }
}

Usage rating

At runtime

Recorded on the operation receipt

Browser calls receive a measured runtime receipt. Allowance quantities remain unpublished until the fully allocated rate card is frozen.