Dsh Verify

What dsh-verify MCP server does

The dsh-verify MCP server checks whether an agent-built web application behaves as a user would expect. It opens a local application or target URL in a real browser, performs defined actions, and evaluates the resulting page. Checks can cover clicks, form input, visible text, CSS classes, computed styles, URLs, screenshots, console errors, network errors, and pixel differences.

The result is a deterministic PASS or FAIL verdict. Each run can produce a self-contained HTML report containing step-level status, selectors, details, screenshots, and highlighted image differences. Machine-readable JSON output and process exit codes are available through the command-line interface, making the same checks usable in automation.

How it works

A JSON specification defines the application target and the browser steps. It can point to a static directory with serve, or to an existing site with base. The specification also selects a browser and contains ordered actions such as navigating, clicking, filling fields, checking text, inspecting classes, capturing a style value, comparing a later style value, or taking a screenshot.

The dsh-verify MCP server exposes four tools:

• verify_spec runs a specification supplied as JSON.
• verify_url runs inline checks without requiring a specification file.
• generate_and_verify lets an AI draft a checklist after examining a page, then runs that checklist in the browser. The AI drafts the checks; the browser determines their results.
• health provides a health check for the MCP service.

Visual regression is supported through screenshot baselines, pixel-diff thresholds, and baseline updates. Specifications can select Chromium, Firefox, or WebKit. Multiple specifications can also be run from a glob when using the CLI.

Setup and configuration

Install the package through the MCP command used by a client:

claude mcp add dsh-verify -- npx -y -p dsh-verify dsh-verify-mcp

The browser runtime must be installed separately with Playwright. For Chromium, the documented setup is:

npx playwright install chromium

No environment variables are required by the documented MCP setup. A specification supplies fields such as title, serve or base, browser, and steps. The GitHub Action also accepts a specification or glob through spec, an optional URL override through url, and an output directory through out.

Tools and capabilities

Reach for the dsh-verify MCP server when an agent needs to validate behavior that static checks or self-review may miss, such as a theme toggle that changes a class but not the rendered CSS. It is framework-independent because the test contract is a JSON document rather than an SDK or configuration language.

The package also provides a CLI and a GitHub Action, so MCP-based checks can be reused by a developer or CI system. The repository documents use with Claude Code, Cursor, Copilot, Codex, and DeepSeek Harness, and describes the checks as suitable for any CI workflow.

Limitations and notes

The browser is the source of the verdict; an AI-generated checklist does not judge whether the result is correct. Browser installation is an additional setup step, and the documented MCP invocation uses a local standard-input/standard-output process. The available material does not specify a license or list required environment variables.