Enables AI agents to ensure subscription checkout and email compliance with auto-renewal laws like ROSCA and California's ARL.
Also known as checkbox-site/checkbox, checkbox, @checkbox-site/mcp
- Stars
- 0
- Tools
- 1
- Downloads, 30 days
- 3,619
- Latest version
- 1.0.10
- Last commit
- Nov 16, 2026
- License
- MIT
What is Checkbox MCP?
Checkbox enables AI agents to ensure subscription checkout and email compliance with auto-renewal laws like ROSCA and California's ARL. It exposes 1 tool, such as setup_checkbox.
Summary generated from the project's README
About Checkbox MCP server
Ensuring subscription checkout and email compliance with automatic renewal laws is the primary function of Checkbox. Developers using Claude, Cursor, or VS Code can connect their AI agents to this server to audit code against regulations like ROSCA, California's Automatic Renewal Law, and New York GBL § 527-a. The server allows agents to generate compliance plans, run synthetic test subscriptions, and verify specific tasks until a compliant status is reached.
Users can connect via a remote HTTP transport using OAuth for a simple sign-in process, or via a local stdio installation using npx. While remote connections are recommended for desktop clients, headless agents and CI environments can use API keys through authorization headers. The server provides specialized tools such as check_disclosure, check_stripe_checkout_session, check_email, and check_page_html to inspect code before deployment. All features are available for free under fair-use limits without requiring a credit card.
What you can do with it
- 1Run automated subscription testingInstruct an agent to perform synthetic test subscriptions to validate the renewal flow.
Written from the project's README. Every use case is checked against a quote from it.
How to install Checkbox MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Checkbox MCP in Claude Code
$ claude mcp add --env 'CHECKBOX_API_KEY=<YOUR_CHECKBOX_API_KEY>' checkbox -- npx -y @checkbox-site/mcpInstall Checkbox MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"checkbox": {
"command": "npx",
"args": [
"-y",
"@checkbox-site/mcp"
],
"env": {
"CHECKBOX_API_KEY": "<YOUR_CHECKBOX_API_KEY>"
}
}
}
}Install Checkbox MCP in VS Code
.vscode/mcp.json
{
"servers": {
"checkbox": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@checkbox-site/mcp"
],
"env": {
"CHECKBOX_API_KEY": "<YOUR_CHECKBOX_API_KEY>"
}
}
}
}Install Checkbox MCP in VS Code CLI
$ code --add-mcp '{"name":"checkbox","type":"stdio","command":"npx","args":["-y","@checkbox-site/mcp"],"env":{"CHECKBOX_API_KEY":"<YOUR_CHECKBOX_API_KEY>"}}'Install Checkbox MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"checkbox": {
"command": "npx",
"args": [
"-y",
"@checkbox-site/mcp"
],
"env": {
"CHECKBOX_API_KEY": "<YOUR_CHECKBOX_API_KEY>"
}
}
}
}Install Checkbox MCP in Codex
$ codex mcp add checkbox --env 'CHECKBOX_API_KEY=<YOUR_CHECKBOX_API_KEY>' -- npx -y @checkbox-site/mcpInstall Checkbox MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.checkbox] command = "npx" args = ["-y", "@checkbox-site/mcp"] [mcp_servers.checkbox.env] CHECKBOX_API_KEY = "<YOUR_CHECKBOX_API_KEY>"
Install Checkbox MCP in Gemini CLI
$ gemini mcp add -s user -e 'CHECKBOX_API_KEY=<YOUR_CHECKBOX_API_KEY>' checkbox npx -- -y @checkbox-site/mcpInstall Checkbox MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"checkbox": {
"command": "npx",
"args": [
"-y",
"@checkbox-site/mcp"
],
"env": {
"CHECKBOX_API_KEY": "<YOUR_CHECKBOX_API_KEY>"
}
}
}
}Started by HostedMCP on 16 Nov 2026
We ran this command for @checkbox-site/mcp 0.4.6 in an isolated container with no network and no keys. It answered and listed 1 tool.
Checkbox MCP tools 1
Read from the server with tools/listsetup_checkboxActionStart 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.
Configuration
CHECKBOX_API_KEYSecretOptional. Checkbox API key (ck_test_… or ck_live_…). Without it, the setup_checkbox tool returns an approval link for the human, then test-mode keys. Free at https://app.checkbox.site/sign-up
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablecheckbox-site/checkbox is public and reachablegithub.com/checkbox-site/checkbox ↗Pass
- Package names this repository as its source@checkbox-site/mcp names checkbox-site/checkbox as sourcenpmjs.com/package/@checkbox-site/mcp ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for @checkbox-site/mcpnpmjs.com/package/@checkbox-site/mcp/v/0.4.2#provenance ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-13github.com/checkbox-site/checkbox ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @checkbox-site/mcpPass
- No critical advisory in the package or its dependenciesthe package checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubCheckbox MCP server
Auto-renewal law checks (ROSCA, click-to-cancel, automatic renewal laws) for Stripe Checkout, cancellation flows and renewal reminder emails, for AI coding agents. Connect Claude, Cursor, VS Code or any MCP client to Checkbox and your agent can set up a project with one human click, check checkout code before it ships, work the compliance plan to done and run synthetic test subscriptions — against ROSCA, California's Automatic Renewal Law, New York GBL § 527-a and the other state automatic-renewal laws.
Docs: https://checkbox.site/docs/mcp · Agent index: https://checkbox.site/llms.txt · Free. Every feature. No credit card. Fair-use limits.
Connect
Remote (recommended) — Streamable HTTP at https://app.checkbox.site/mcp, nothing to install, no API key to copy:
the server implements MCP OAuth, so your client opens a Checkbox sign-in and you click Approve once.
- claude.ai / Claude Desktop: Settings → Connectors → Add custom connector →
https://app.checkbox.site/mcp→ Connect → Approve. - Claude Code:
claude mcp add --transport http checkbox https://app.checkbox.site/mcp, then/mcp→ Authenticate. - Cursor (
.cursor/mcp.json):{ "mcpServers": { "checkbox": { "url": "https://app.checkbox.site/mcp" } } }, then Connect.
API keys still work everywhere (CI, headless agents): add --header "Authorization: Bearer $CHECKBOX_SECRET_KEY"
(Claude Code) or "headers": { "Authorization": "Bearer ${env:CHECKBOX_SECRET_KEY}" } (Cursor). Agents without a
browser: https://app.checkbox.site/mcp?login=device offers setup_checkbox, which returns an approval link and then
test-mode keys.
Local (stdio) — for clients without remote MCP support:
{
"mcpServers": {
"checkbox": {
"command": "npx",
"args": ["-y", "@checkbox-site/mcp"],
"env": { "CHECKBOX_API_KEY": "ck_test_..." }
}
}
}
Package: @checkbox-site/mcp on npm (Node 20+; binary checkbox-mcp). Options:
--read-only (hides write tools; not a security boundary, the key keeps its permissions: use a read-only ckr_… key to limit it), --api-key, --api-base; environment CHECKBOX_API_KEY (falls back to CHECKBOX_SECRET_KEY),
CHECKBOX_API_BASE, CHECKBOX_MCP_READ_ONLY=true.
Tools
Start with setup_checkbox; then get_compliance_plan → apply a task → verify_task, until the checks pass (plan status compliant).
Preflight tools (check_disclosure, check_stripe_checkout_session, check_email, check_page_html,
get_notice_schedule) work on code before it is deployed. The full list, with the API operation behind each tool, is
at https://checkbox.site/docs/mcp#tools.
Every tool is a thin call to the public API (https://app.checkbox.site/v1), so keys, scopes, test/live mode and rate
limits are the API's. Write tools say so and carry readOnlyHint: false. Results are written for models and end with
the next tool to call.
Not legal advice
Rules drafted from the statute text and updated as new statutes come into effect. Automated checks, not legal advice. Every rule cites its source, so you or your lawyer can check it.
License
MIT
Checkbox MCP questions
How do I add Checkbox MCP to Claude Code?
Run claude mcp add --env 'CHECKBOX_API_KEY=<YOUR_CHECKBOX_API_KEY>' checkbox -- npx -y @checkbox-site/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Checkbox MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Checkbox MCP provide?
It exposes 1 tool, including setup_checkbox.
Is this tool providing legal advice?
No, the tool provides automated checks based on statute text, not legal advice.
How do I connect to the remote MCP server?
You can connect via HTTP using OAuth by adding the URL to your client settings and clicking Approve.
Can I use this in headless environments or CI?
Yes, you can use API keys with authorization headers for CI and headless agents.