6Frame Verify

What the 6Frame Verify MCP server does

The 6Frame Verify MCP server checks a website before launch by opening it in Chromium at desktop and mobile sizes. A Quick Check covers one page, while a Full Check can cover up to 10 pages. Reports include findings, screenshots, and specific suggested fixes.

Checks can identify an HTTP failure, broken links, missing or unsuitable title and meta description content, missing H1 elements, Open Graph preview issues, mobile viewport problems, horizontal overflow, browser console errors, slow loading, missing image alt text, and favicon issues. The service is available through MCP and REST. A browser-based option is also available at siteverify.dev for human users.

How it works

Connect an MCP client to https://siteverify.dev/mcp using Streamable HTTP. Discovery and several account or pricing operations work without a key. The keyless tools are verify_get_capabilities, verify_quote, and verify_signup; the signup operation can create a key without requiring an email address.

Authenticated access uses a bearer token with the fv_live_ prefix. With a key, an agent can call verify_check_site, verify_get_job, verify_get_report, verify_get_credits, and verify_buy_credits. A check uses the daily free Quick Check when available, then a prepaid credit. If neither applies, the service returns a Stripe checkout link, and the check begins after payment is confirmed.

The 6Frame Verify MCP server also exposes a REST API. A client can create a key at /v1/keys and submit a check to /v1/checks. OpenAPI discovery is available at /.well-known/openapi.json, with /openapi.json as an alias. MCP server metadata is published through the server-card endpoints.

Setup and configuration

For hosted use, configure the MCP endpoint and authorization header in the client. The README provides this connection shape:

{
  "mcpServers": {
    "6frame-verify": {
      "url": "https://siteverify.dev/mcp",
      "headers": { "Authorization": "Bearer fv_live_..." }
    }
  }
}

A free API key provides one free Quick Check per day. Paid usage includes a $3 Quick Check for one page and a $12 Full Check for up to 10 pages. Credit packages are also available. The repository's local development setup requires a copied .env file, PostgreSQL, Redis, Stripe configuration, a report-signing private key, and an API encryption key, followed by dependency installation and database migration.

Tools and capabilities

• Discover available capabilities without authentication.
• Create an API key through verify_signup.
• Request a quote before ordering a check.
• Start site verification with verify_check_site.
• Retrieve job status and completed reports.
• Inspect or purchase credits.
• Access reports containing screenshots and exact fixes.
• Use REST, MCP, or the documented OpenAPI schema.

The 6Frame Verify MCP server uses a queued browser-worker model for verification. Its repository includes a Next.js web and API application, an isolated Playwright Chromium worker, shared schemas, evaluator packages, and PostgreSQL migrations.

Limitations and notes

The service is priced per check unless the daily free allowance or prepaid credits apply. Quick Check covers one page; Full Check covers up to 10 pages. Paid MCP tools require a bearer key, while the documented discovery and signup operations do not.

The README does not name a specific MCP desktop client or editor. Any client must support Streamable HTTP and bearer headers to use the hosted MCP endpoint in the documented configuration. The repository is licensed under MIT.