@checkbox-site/mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Contacts while installing and starting: nothing
Its tool definitions changed since version 0.3.0. If you approved the earlier ones, read them again.
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @checkbox-site/mcp@0.4.6
Installing a package runs its code. Use a sandbox for anything you have not read.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
setup_checkbox site_url, checkout_url, account_url, terms_url, privacy_url, refund_url, cancellation_url, support_email, merchant_name, billing_platform, plans, project, device_code, live, agent, verbose
Start here when the user says "add Checkbox", "make my subscriptions compliant", or the project is not connected yet. Checkbox checks a subscription business against auto-renewal laws (federal law, 27 states, DC and NYC). Connected through the Checkbox connector (OAuth): the human already approved in the browser; there is NO key to ask for, 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 what you know from the codebase: site_url, checkout_url, terms/privacy/refund/cancellation URLs, billing_platform, plans, framework, project.layout_file. Checkbox fetches and checks the Terms itself. Without OAuth or a key: it returns a link for the HUMAN to open and click Approve (free, no card). Show it in one line, then call again with the returned device_code (waits ~50 s; again while pending). The stdio server then saves the key to the git-ignored .env.local; the remote one returns it once: save it there, never commit it or ask for a pasted key. After this: follow next_action (usually verify the domain and install the snippet, then get_setup_status with verify=true), then get_compliance_plan.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=20 |
| Source | github.com/checkbox-site/checkbox |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-smgt1KZtN/WkmN53X4mkdMas5kVWpX+g9Wq2+HHHqeCIHblJCydfKSyKKr+1aR8NbZFtjboxJzUB62Rjxg8ToA== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 0.4.6 | 2026-11-16 | Starts with no setup | 1 |
| 0.3.0 | 2026-11-12 | Starts with no setup | 1 |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40checkbox-site/mcp)
New version out? Ask for a fresh report.