Check’d
Start free

Product

All featuresProduction monitoringSession replayAI explain and fixImport API docsJourneys
DevelopersPricingFree site scanChangelogSign in

Check’d in your terminal, your CI and your AI assistant.

The checked CLI starts runs and fails the build when release gates fail. The MCP server lets Claude Code, Cursor and VS Code read your results and fix what broke. The SDKs watch production. All open source, all on npm.

Start freeCLI docs

MIT licensed. The CLI and MCP server work on every plan; CI API keys are on paid plans.

Four packages, MIT licensed

Read the code, file an issue, or pin a version. Each links to its npm page and its repository.

  • checkd-cli

    checked CLI · Node.js 20 or newer

    Start runs, follow them live, read findings and issues, and fail CI when release gates fail. The command is checked.

    npm install -g checkd-cli
    checkd-cli on npm Source on GitHubDocs

  • checkd-mcp

    MCP server · Node.js 20 or newer

    Lets Claude Code, Cursor and VS Code read runs, findings and issues, and start runs when you ask.

    npx -y checkd-mcp
    checkd-mcp on npm Source on GitHubDocs

  • checkd-browser

    Browser SDK · Any modern browser

    Production errors, failed requests, slow pages, breadcrumbs and opt-in session replay. No dependencies; also a script tag.

    npm install checkd-browser
    checkd-browser on npm Source on GitHubDocs

  • checkd-node

    Node.js SDK · Node.js 18 or newer

    Uncaught exceptions, unhandled rejections and custom events, with Express, Fastify and AdonisJS helpers.

    npm install checkd-node
    checkd-node on npm Source on GitHubDocs

The checked command line

Sign in by approving a code in the browser, import your API, start runs and follow them live. Results go to stdout and progress to stderr, every command takes --json, and exit codes tell CI what happened. Full CLI guide.

Install

npm install -g checkd-cli

GitHub Actions

# .github/workflows/checked.yml
name: Check’d
on: [push]
jobs:
  checked:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/setup-node@v4
        with:
          node-version: 20
      - name: Run the Check’d tests
        env:
          CHECKED_API_KEY: ${{ secrets.CHECKED_API_KEY }}
        run: npx -y checkd-cli run --project your-project-ref --depth critical --timeout 20m

Commands

  • checked login

    Sign in by approving a code in the browser (or --api-key / --with-key)

  • checked logout

    Revoke and forget the saved sign-in

  • checked whoami

    Who you are signed in as, and your workspaces

  • checked projects list

    Your projects and their last run

  • checked envs list

    A project’s environments

  • checked import <file|url>

    Import OpenAPI, Swagger, Postman, Insomnia, HAR, GraphQL or cURL; shows what it found and asks first (--yes in CI)

  • checked run

    Start a run, follow it live, exit non-zero when release gates fail

  • checked runs list | show | watch | report | results | rerun-failed | cancel

    Look into runs, re-run what failed

  • checked findings list | show

    Failed tests and scan findings with evidence and fixes

  • checked issues list | show

    The issue inbox: production errors and test findings, with the AI explanation when one exists (--explain)

  • checked scan <url>

    A website health scan

  • checked usage

    This session’s and this month’s usage

  • checked open

    Open a run or project in the browser

An MCP server for testing

Give your AI assistant the same view of your quality that you have. It can read the latest run, a failure’s exact request, response and diagnosis, the issue inbox with its AI explanations, fix the code and re-run the failed tests to confirm. MCP setup guide.
  • Runs on your machine over stdio with your key or your CLI sign-in.
  • Read-only tools are free; tools that start work use your allowance and say so first.
  • Run reports, results and findings are also readable as resources.

Claude Code

claude mcp add checked --env CHECKED_API_KEY=tfy_your_key -- npx -y checkd-mcp

Things to ask

  • What failed in the latest Check’d run, and why?
  • Show me the worst production issue and its explanation, then fix the handler.
  • I fixed it. Re-run the failed tests and tell me if the release gates pass.

SDKs and APIs

Watch production and wire Check’d into the tools you already run.

  • Browser SDK

    A script tag or checkd-browser from npm. Errors, failed requests, Web Vitals, breadcrumbs and opt-in session replay.
    Install the browser SDK

  • Node.js SDK

    checkd-node for uncaught exceptions and rejections, with Express, Fastify and AdonisJS helpers.
    Install the Node.js SDK

  • Ingest API

    Send events from any language: up to 50 per request, JSON as text/plain to skip a CORS preflight.
    Ingest API reference

Register a release from CI

curl -X POST https://getchecked.twelveai.app/api/v1/releases \
  -H "Authorization: Bearer $CHECKED_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"projectId": "shop-kqzxm", "version": "1.4.2", "environment": "production"}'

Keys

Ingest keys (ck_pub_...) can only send events and are safe in page source. Workspace API keys (tfy_...) read results, import specs and start runs in one workspace, and cannot change its settings.

Questions people ask

Open source, sign-in, CI and AI assistants.

Ask support something else
Are the packages open source?

Yes. checkd-cli, checkd-mcp, checkd-browser and checkd-node are MIT licensed, with their source on GitHub and releases on npm.

How does the CLI sign in?

checked login shows a short code and opens your browser. Check that the code matches, approve, and the terminal is signed in as you for 90 days. On servers and in CI, use a workspace API key in CHECKED_API_KEY instead.

Will the CLI fail my build?

When a run misses the project’s release gates (pass rate, critical and high defects, and any others you set), checked run exits with code 1, and with other codes for errors, timeouts and usage limits, so a pipeline can stop a bad release.

Which AI assistants work with the MCP server?

Claude Code, Cursor and VS Code, and any other client that runs MCP servers over stdio. Read-only tools are free; tools that start runs or scans use your allowance and say so, so the assistant asks first.

Is the CLI on the free plan?

Yes. Signing in with checked login and using the MCP server work on every plan. Workspace API keys for CI are on the paid plans. Everything uses the same usage as the app.

Works with the rest of Check’d

Install the CLI and run your first test

npm install -g checkd-cli, then checked login. Free plan, no card needed.

Start freeScan a site, no account needed