# Checkbox (npm · @checkbox-site/mcp)

Auto-renewal law compliance (ROSCA, CA, NY, other states) for subscription checkout and emails

- Trust score: 80/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `app.checkbox.site`: 37/100, [markdown](https://verifymcp.io/servers/site-checkbox-checkbox/app.md), [page](https://verifymcp.io/servers/site-checkbox-checkbox/app)
- npm · `@checkbox-site/mcp`: 80/100 (this document), [markdown](https://verifymcp.io/servers/site-checkbox-checkbox/checkbox-site-mcp.md), [page](https://verifymcp.io/servers/site-checkbox-checkbox/checkbox-site-mcp)

## Channel facts

- Registry: `npm`
- Package: `@checkbox-site/mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to checkbox-site/checkbox).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 70/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1058 tokens (~352/item across 3 items; 1 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Checkbox MCP server?

Checkbox runs locally as an npm package, launched with npx -y @checkbox-site/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add site-checkbox-checkbox -- npx -y @checkbox-site/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "site-checkbox-checkbox": {
      "command": "npx",
      "args": [
        "-y",
        "@checkbox-site/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "site-checkbox-checkbox": {
      "command": "npx",
      "args": [
        "-y",
        "@checkbox-site/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add site-checkbox-checkbox -- npx -y @checkbox-site/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "site-checkbox-checkbox": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@checkbox-site/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add site-checkbox-checkbox --command npx --arg -y --arg @checkbox-site/mcp
```

### Hermes

```yaml
mcp_servers:
  site-checkbox-checkbox:
    command: "npx"
    args: ["-y", "@checkbox-site/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "site-checkbox-checkbox": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@checkbox-site/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add site-checkbox-checkbox -t stdio -c npx -a -y @checkbox-site/mcp
```

### Other

```json
{
  "mcpServers": {
    "site-checkbox-checkbox": {
      "command": "npx",
      "args": [
        "-y",
        "@checkbox-site/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 80)

First indexed and scored.

## MCP tools (1)

### `setup_checkbox` (~717 tokens)

Set up Checkbox for this project

Start here when the user says "add Checkbox", "make my subscriptions compliant", or no Checkbox key is configured.
Checkbox monitors a subscription business against automatic-renewal laws (FTC ROSCA, California ARL, New York and ~26 other states).

Without an API key (first run): returns a link for the HUMAN to open and click Approve (they sign up with an email link or GitHub/Google if new; free, no card).
Show them the link in one line, then call setup_checkbox again with the returned device_code — it waits up to ~50 s for the approval; call again while it says pending.
On approval it returns test-mode API keys (shown once) and a setup session. Save CHECKBOX_SECRET_KEY to .env.local (git-ignored) and never commit it.

With an API key: starts a setup session for the project (no human step) and returns the setup checklist with next_action.
Connected through the Checkbox connector (OAuth: claude.ai, Claude Desktop, Claude Code /mcp, Cursor): the human already approved; there is NO key to paste or save. Call it with site_url (and what else you know): it registers the site and runs the first checks in the same call.
Pass everything you already know from the codebase: site_url, checkout_url, terms/privacy/refund/cancellation URLs, billing_platform, plans, project.layout_file. Checkbox fetches and checks the Terms itself.

After this: follow next_action (usually install the snippet, then update_setup / get_setup_status with verify=true), then get_compliance_plan.
The `checkbox init` CLI does the same and also patches the layout file (pre-release: not on npm yet; never install an npm package named "checkbox", it is not ours).

Input parameters:

- `account_url` (string): Account page where subscribers manage / cancel.
- `agent` (string): Which AI agent is doing this, shown to the human on the approval page, e.g. "Claude Code".
- `billing_platform` (string): Billing platform the code uses.
- `cancellation_url` (string): Cancellation policy URL, if separate from the Terms.
- `checkout_url` (string): Page where customers subscribe (pricing or checkout page).
- `device_code` (string): From an earlier setup_checkbox call: poll that browser approval instead of starting a new one.
- `live` (boolean): Also request live-mode keys (live mode activates after domain verification). Default false: test mode only.
- `merchant_name` (string): The brand subscribers know (names the seller in generated disclosures), e.g. from the <title> or package.json. Default: the host name, which the plan then asks you to replace.
- `plans` (array): Plans and prices found in the code, e.g. [{"name":"Pro","amount":1900,"currency":"usd","interval":"month","trial_days":14}]. They decide which laws apply (trials, annual terms).
- `privacy_url` (string): Privacy policy URL.
- `project` (object): Facts about the codebase that help Checkbox point tasks at exact files.
- `refund_url` (string): Refund policy URL.
- `site_url` (string): Public URL of the site (production, or a preview deployment), e.g. "https://acme.example".
- `support_email` (string): Support address subscribers can write to.
- `terms_url` (string): Terms of service URL. Checkbox fetches and checks it.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/site-checkbox-checkbox/checkbox-site-mcp#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 80

## Common questions

### What is the Checkbox MCP server?

Checkbox is an MCP server listed in the public MCP registry as site.checkbox/checkbox. Auto-renewal law compliance (ROSCA, CA, NY, other states) for subscription checkout and emails. This page covers its npm package (@checkbox-site/mcp).

### Is the Checkbox MCP server safe to use?

Checkbox scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Checkbox MCP server expose?

Checkbox exposes 1 tool: setup_checkbox. Their descriptions and schemas cost roughly 717 tokens of context every time the server is loaded.

### Is the Checkbox MCP server still maintained?

Checkbox is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Checkbox MCP server under?

Checkbox declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Checkbox MCP server?

VerifyMCP ran 16 checks on Checkbox, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@checkbox-site/mcp
- Socket report: https://socket.dev/npm/package/@checkbox-site/mcp
- Repository: https://github.com/checkbox-site/checkbox
- Website: https://checkbox.site/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/site-checkbox-checkbox/checkbox-site-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/site-checkbox-checkbox/checkbox-site-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/site-checkbox-checkbox/checkbox-site-mcp.json
- HTML version of this page: https://verifymcp.io/servers/site-checkbox-checkbox/checkbox-site-mcp