All servers / Legal / Checkbox MCP server
Checkbox MCP server
Checkbox MCP server: auto-renewal law and subscription compliance checks for AI agents (FTC ROSCA, California ARL, New York and other states) on Stripe Checkout
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-18 on package version 0.4.10. Package: @checkbox-site/mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (32.6 seconds including download)
- Tools offered: 1
- Last published: 2026-11-17
- Weekly downloads (npm): 3,630
- License: MIT · Direct dependencies: 3
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
setup_checkbox16 of 16 parameters describedStart 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.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.