CCPA / CPRA applicability checker: free MCP tool
Call the CCPA / CPRA applicability checker from your AI as a free MCP tool, no account: the inputs, a worked request and response, and how to add the server.
ccpa_applicability is one of the 20 free GRC tools from ISMS Copilot that any AI client can call over MCP: no account, no model, one call.
Reads whether an organisation is likely a business under the CCPA as amended by the CPRA, possibly a service provider or contractor, likely exempt for a dataset, or outside the definition, with the reasons. Answer every question (the input schema lists them with their options); with any question unanswered the tool returns the open questions instead of a verdict. The verdict is a reading from fixed rules, not a legal conclusion. Returns general information from a fixed rule set; confirm against the official text.
This page is about calling the tool from an AI client: the request, the response and the setup. For the same tool on the web, with the background on the rules it applies, open the CCPA / CPRA applicability checker page.
Inputs
The tool's input schema, as tools/list returns it, field by field.
| Field | What it is | Allowed values |
|---|---|---|
answers | One answer per question, keyed by question id. Every question needs an answer before a verdict is computed. | object (fields below) |
answers.forProfit | Is your organization a for-profit entity? The CCPA definition of "business" reaches for-profit entities. Government agencies, most nonprofits, and natural persons acting in a purely personal capacity sit outside that definition, even if they handle a lot of California personal information. | yes (Yes, we are for-profit.), no (No (nonprofit, government, or similar).) |
answers.collectsCaPi | Do you collect personal information of California residents (consumers)? "Collects" is broad: you buy it, receive it, or otherwise obtain it. Personal information is information that identifies, relates to, or could reasonably be linked with a particular California consumer or household. De-identified information that meets the statute's standard does not count. | yes (Yes), no (No) |
answers.doesBusinessInCa | Do you do business in California? This is not limited to having a California office. Targeting California residents, selling into California, or otherwise intentionally interacting with the California market typically counts. A purely non-California operation with no California consumers is out. | yes (Yes), no (No) |
answers.determinesPurposes | Do you decide why and how that California personal information is processed? A "business" determines the purposes and means of the processing. A service provider or contractor processes personal information on behalf of a business under a qualifying contract and does not decide those purposes. If you only process California PI as a vendor for someone else's product, answer No. | yes (Yes, we decide the purposes and means.), no (No, we process it on a customer's behalf under a contract.) |
answers.threshold | Which of these thresholds do you meet? Pick the first that applies. You only need one. The revenue figure is worldwide gross revenue in the preceding calendar year, assessed on 1 January. It is not limited to California revenue. The dollar amount is the CPPA inflation-adjusted threshold in force since 1 January 2025 ($26,625,000). The next odd-year adjustment is due in 2027. | revenue (Annual gross revenue over $26,625,000 (the amount in force since 1 January 2025).), volume (We buy, sell, or share the personal information of 100,000 or more California consumers or households in a year.), sellshare (50% or more of our annual revenue comes from selling or sharing California personal information.), none (None of these.), unsure (We do not know yet.) |
answers.exemption | Is the California personal information you handle already governed by another US privacy statute? The CCPA has data-level exemptions, not entity-level ones. PHI a covered entity or business associate holds under HIPAA, and certain GLBA or FCRA information, can fall outside CCPA for that dataset. If you also hold ordinary commercial personal information, that remainder is still in play. | none (No. This is ordinary commercial personal information.), hipaa-only (Yes. It is only HIPAA-covered protected health information.), glba-only (Yes. It is only information subject to the Gramm-Leach-Bliley Act.), mixed (Some is exempt, some is ordinary commercial data.), unsure (We are not sure.) |
If an answer is missing
The tool never guesses an answer. A call with any field left out returns status: "needs_answers" and the open questions, each with its id, its text and its allowed values, and no result. Your AI can ask you those questions and call again.
Worked example
This request and response come from the tool itself: the catalog runs the tool's handler on this example input, and this page is generated from that catalog.
Request
A tools/call request, as your client sends it:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "ccpa_applicability",
"arguments": {
"answers": {
"forProfit": "yes",
"collectsCaPi": "yes",
"doesBusinessInCa": "yes",
"determinesPurposes": "yes",
"threshold": "revenue",
"exemption": "none"
}
}
}
}Response
The structuredContent of the result. The result's text content says the same in plain words, with the disclaimer.
{
"status": "result",
"verdict": {
"id": "likely-business",
"reading": "Reading from fixed rules, not a legal conclusion: Likely a CCPA / CPRA business",
"page_title": "Likely a CCPA / CPRA business",
"summary": "On these answers your organization meets the definition of a \"business\" in Cal. Civ. Code § 1798.140(d): for-profit, California personal information, doing business in California, deciding purposes and means, and at least one threshold. That is a structured assessment, not a determination.",
"tone": "in"
},
"reasons": [
{
"code": "revenue-threshold",
"text": "You indicated annual gross revenue over $26,625,000. That is the CPPA-adjusted amount under § 1798.199.95(d), effective 1 January 2025 (published 17 December 2024). It is worldwide revenue, not California-only. The next odd-year adjustment is due in 2027."
},
{
"code": "consumer-rights",
"text": "A business must honor consumer rights to know, delete, correct, and opt out of sale or sharing, and to limit the use of sensitive personal information, on the timelines in the statute."
},
{
"code": "notice-and-opt-out",
"text": "A business must provide a notice at collection and, if it sells or shares personal information, a \"Do Not Sell or Share My Personal Information\" mechanism, including honoring opt-out preference signals."
},
{
"code": "status-is-definitional",
"text": "CCPA status follows the statutory definition, not the label on your homepage and not whether you have already posted a privacy notice."
}
],
"obligations": [
"Provide a notice at collection that names the categories of personal information and sensitive personal information, the purposes, whether you sell or share, and the retention period (Cal. Civ. Code § 1798.100, § 1798.130).",
"Honor consumer requests to know, delete, and correct, and to opt out of sale or sharing, within the statutory timelines (§ 1798.105, § 1798.106, § 1798.110, § 1798.115, § 1798.120).",
"If you sell or share personal information, offer a \"Do Not Sell or Share My Personal Information\" link or equivalent and honor opt-out preference signals (§ 1798.135).",
"Limit use and disclosure of sensitive personal information when the consumer directs you to (§ 1798.121).",
"Put a qualifying written contract in place before a service provider or contractor processes personal information on your behalf (§ 1798.100(d)).",
"Implement reasonable security procedures and practices appropriate to the nature of the information (§ 1798.150(a)(1)).",
"Enter into the California privacy regime's administrative requirements: a privacy policy that is updated at least every 12 months, methods to submit requests, and training for people who handle requests (§ 1798.130)."
],
"answered": 6,
"total": 6,
"basis": [
"Cal. Civ. Code 1798.140",
"Cal. Civ. Code 1798.145",
"Cal. Civ. Code 1798.199.95(d)"
],
"sources_checked_on": [
{
"source": "Cal. Civ. Code § 1798.140, definitions including \"business\", \"service provider\", \"contractor\", \"sell\", and \"share\" (California Legislative Information, current)",
"checked_on": "2026-08-13"
},
{
"source": "Cal. Civ. Code § 1798.145, construction and exemptions (HIPAA, GLBA, FCRA and others)",
"checked_on": "2026-08-13"
},
{
"source": "California Privacy Protection Agency, Updated Monetary Thresholds in the CCPA (CPI adjustment to $26,625,000, effective 1 January 2025, posted 17 December 2024)",
"checked_on": "2026-08-13"
}
],
"disclaimer": "General information from a fixed rule set, not legal advice. Check the result against the official text and with a qualified professional before you act on it.",
"more": {
"url": "https://www.ismscopilot.com/mcp?ref=mcp-tool-ccpa-applicability-checker",
"label": "Review your own documents against this framework with ISMS Copilot"
},
"tool_page": "https://www.ismscopilot.com/resources/ccpa-applicability-checker"
}What the result rests on
Every result names its basis, as identifiers only (never standard text):
- Cal. Civ. Code 1798.140
- Cal. Civ. Code 1798.145
- Cal. Civ. Code 1798.199.95(d)
Sources the rules were checked against, with the date each was last checked:
- Cal. Civ. Code § 1798.140, definitions including "business", "service provider", "contractor", "sell", and "share" (California Legislative Information, current), checked 2026-08-13
- Cal. Civ. Code § 1798.145, construction and exemptions (HIPAA, GLBA, FCRA and others), checked 2026-08-13
- California Privacy Protection Agency, Updated Monetary Thresholds in the CCPA (CPI adjustment to $26,625,000, effective 1 January 2025, posted 17 December 2024), checked 2026-08-13
Add the server
claude mcp add --scope user --transport http ismscopilot-free-tools 'https://www.ismscopilot.com/api/public/tools/mcp'That is Claude Code. For claude.ai, Claude Desktop, ChatGPT, Cursor, Codex and any other client, see Add the server to your client. No sign-in, no token.
Limits
General information from a fixed rule set, not legal advice. Check the result against the official text and with a qualified professional before you act on it.
Your inputs are never logged or stored by our code. We count calls per tool (the tool name, whether it produced a result and when, nothing else). Our host keeps standard request logs (time, path, status, client address) for a short period. Do not send personal data: no tool needs any.
A fixed rule cannot read your own policies, registers or contracts. For a review of your own documents, connect ISMS Copilot, the GRC expert your AI calls.