Checkbox
NPM · @CHECKBOX-SITE/MCP · 2 COMPONENTS
Auto-renewal law compliance (ROSCA, CA, NY, other states) for subscription checkout and emails
Available components
Last scanned (6 hours ago)
Scores higher than 65% of npm servers
Category E-commerce
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to checkbox-site/checkbox). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 80
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@checkbox-site/mcp@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | checkbox-site/checkbox |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/checkbox-site/checkbox/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3650806605 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:df321783371be4c3efd783b1bfd2a338e4b11cc057005789250bd50f71c84d650c5700e0bb46341db80a227b4135952d04d361688660d9aeb0a5b0c8f |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
setup_checkbox Set up Checkbox for this project ~717
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
npm · @checkbox-site/mcp
claude mcp add site-checkbox-checkbox -- npx -y @checkbox-site/mcp
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.