ISMS Copilot Docs

HIPAA applicability checker: free MCP tool

Call the HIPAA 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.

hipaa_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 HIPAA covered entity, a business associate, or outside HIPAA's direct scope (45 CFR Parts 160 and 164), 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 HIPAA applicability checker page.

Inputs

The tool's input schema, as tools/list returns it, field by field.

FieldWhat it isAllowed values
answersOne answer per question, keyed by question id. Every question needs an answer before a verdict is computed.object (fields below)
answers.handlesHealthInfoDoes your organization create, receive, maintain, or transmit health information about identifiable individuals? Health information here means information about someone's health condition, the care they receive, or payment for that care, where the person is identified or identifiable. It includes demographic details collected alongside care or coverage. Information de-identified to the 45 CFR 164.514 standard (the Safe Harbor removal of 18 identifiers, or expert determination) does not count; if you only ever handle data de-identified to that standard, answer No.yes (Yes), no (No)
answers.entityTypeWhich of these best describes your organization? This is the decisive question. HIPAA names three kinds of covered entity (providers, plans, clearinghouses) and reaches everyone else only through the business-associate definition. Pick the closest fit for the part of your business you are assessing; if your organization genuinely does several of these, run the check once per role.provider (We furnish, bill for, or are paid for health care (a hospital, clinic, physician practice, pharmacy, lab, therapy practice, dental practice, or similar).), plan (We provide or pay the cost of medical care (a health insurer, HMO, Medicare or Medicaid program, or most employer-sponsored group health plans).), clearinghouse (We process health information between providers and payers, converting it between standard and nonstandard formats (a clearinghouse or similar billing intermediary).), vendor (We provide services to health care organizations or their vendors, and those services involve their health information (software, hosting, billing, analytics, transcription, consulting, or similar).), none (None of these (for example a direct-to-consumer wellness app with no insurer or provider involved, or an employer holding its own employment records).), unsure (It is not yet clear which of these describes us.)
answers.electronicTransactionsDo you, or does a billing service or clearinghouse acting for you, transmit health information electronically in connection with a HIPAA standard transaction (such as submitting claims to insurers, checking eligibility, or requesting prior authorizations)? This is the trigger that makes a health care provider a covered entity: providers are covered only if they conduct at least one of the electronic transactions covered by the HIPAA Transactions Rule (45 CFR 160.102 and 160.103). Billing insurance electronically meets it, including when an outside billing service does the submitting for you. A practice that takes only direct payment and never bills electronically may not. Answer for the provider role; if you are not a provider, this does not change the result.yes (Yes), no (No)
answers.phiOnBehalfDo your services involve creating, receiving, maintaining, or transmitting identifiable health information on behalf of your clients? Storing or hosting the data counts even if it is encrypted and you never view it: HHS treats a cloud provider holding electronic protected health information as a business associate even in that no-view scenario. The only carve-out is the narrow conduit exception for mere transmission services with only transient access, like a telecommunications carrier. Answer for the vendor role; if you are not a vendor, this does not change the result.yes (Yes), no (No)
answers.clientTypeAre the clients whose health information you handle themselves HIPAA covered entities or business associates? Your status as a vendor derives from your clients'. Handling health information for a covered entity (a provider, plan, or clearinghouse) makes you a business associate; handling it for another business associate makes you a subcontractor business associate; handling it for organizations that are neither (for example consumer apps or employers) is generally outside HIPAA, because that information is not protected health information.covered-entity (Yes, our clients include covered entities: health care providers, health plans, or clearinghouses.), business-associate (Yes, our clients include business associates of covered entities (we act as a subcontractor in their vendor chain).), neither-unsure (No, or we are not sure of our clients' HIPAA status.)
answers.consumerHealthOfferingDo you also offer a health product or service directly to consumers, with no provider or insurer involved (for example a wellness app, fitness tracker, or direct-to-consumer health record)? Health data collected directly from consumers outside any covered-entity relationship is generally not protected health information, so HIPAA does not govern it. Instead, the FTC Health Breach Notification Rule (16 CFR Part 318) can require breach notification from vendors of personal health records, PHR related entities (including connected health apps in covered circumstances), and their third-party service providers, and the FTC Act applies to the privacy promises you make. This question never changes your HIPAA verdict; it adds the right signpost.yes (Yes), no (No)

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": "hipaa_applicability",
    "arguments": {
      "answers": {
        "handlesHealthInfo": "yes",
        "entityType": "vendor",
        "electronicTransactions": "no",
        "phiOnBehalf": "yes",
        "clientType": "covered-entity",
        "consumerHealthOffering": "no"
      }
    }
  }
}

Response

The structuredContent of the result. The result's text content says the same in plain words, with the disclaimer.

{
  "status": "result",
  "verdict": {
    "id": "business-associate",
    "reading": "Reading from fixed rules, not a legal conclusion: Your organization is likely a HIPAA business associate",
    "page_title": "Your organization is likely a HIPAA business associate",
    "summary": "On your answers your organization creates, receives, maintains, or transmits protected health information on behalf of HIPAA-regulated clients, which is the business-associate definition in 45 CFR 160.103. A written business associate agreement must be in place before that work happens, and since the HITECH Act and the 2013 Omnibus Rule you are directly liable under the Security Rule and the Breach Notification Rule, not just under the contract. The obligations block below summarizes what that means in practice.",
    "tone": "in"
  },
  "reasons": [
    {
      "code": "ba-definition",
      "text": "You indicated your organization creates, receives, maintains, or transmits identifiable health information on behalf of covered entities. That is the business-associate definition in 45 CFR 160.103. Typical examples include software and hosting vendors, billing and claims processors, analytics providers, transcription services, and consultants whose work involves protected health information."
    },
    {
      "code": "baa-required",
      "text": "A written business associate agreement with the provisions required by 45 CFR 164.502(e) and 164.504(e) must be in place before you handle protected health information for the client. In a subcontractor chain, your business-associate client must put an equivalent agreement in place with you."
    },
    {
      "code": "ba-direct-liability",
      "text": "Since the HITECH Act and the 2013 Omnibus Rule, business associates are directly liable under the Security Rule, the Breach Notification Rule, and several Privacy Rule provisions, independently of the contract. HHS can investigate and penalize a business associate directly."
    },
    {
      "code": "status-is-definitional",
      "text": "HIPAA status follows the definitions in 45 CFR 160.103, not labels or contracts: an organization is regulated because it meets a covered-entity category or performs business-associate functions. Signing, or declining to sign, a business associate agreement does not change what the organization is."
    }
  ],
  "obligations": [
    "Use and disclose protected health information only as the Privacy Rule permits or requires, applying the minimum-necessary standard; a business associate is additionally bound by the terms of its business associate agreement (45 CFR 164.502).",
    "Implement the Security Rule's administrative, physical, and technical safeguards for electronic protected health information; the Security Rule applies to covered entities and business associates alike (45 CFR 164.302 through 164.318).",
    "Conduct and document an accurate and thorough risk analysis of the risks to electronic protected health information, and manage the risks it identifies (45 CFR 164.308(a)(1)(ii)).",
    "Put a business associate agreement in place before any vendor creates, receives, maintains, or transmits protected health information on your behalf, and flow equivalent terms down to subcontractors (45 CFR 164.502(e), 164.504(e)).",
    "Notify after a breach of unsecured protected health information: a covered entity notifies the affected individuals and HHS, and for breaches affecting 500 or more people also the media; a business associate notifies the covered entity without unreasonable delay and within 60 days at the latest (45 CFR 164.400 through 164.414).",
    "Covered entities must also maintain a notice of privacy practices, designate privacy and security officials, train their workforce, and apply sanctions for violations (45 CFR 164.520, 164.530, 164.308(a)(2)).",
    "Retain the required documentation, including policies, assessments, and agreements, for six years from creation or last effective date, whichever is later (45 CFR 164.316(b), 164.530(j))."
  ],
  "answered": 6,
  "total": 6,
  "basis": [
    "45 CFR 160.103",
    "45 CFR 164.502(e)",
    "45 CFR 164.504(e)"
  ],
  "sources_checked_on": [
    {
      "source": "45 CFR 160.103, definitions: covered entity, business associate, protected health information (eCFR, current)",
      "checked_on": "2026-09-11"
    },
    {
      "source": "45 CFR 164.502(e) and 164.504(e), business associate contracts (eCFR, current)",
      "checked_on": "2026-09-11"
    },
    {
      "source": "HHS Office for Civil Rights, Covered Entities and Business Associates",
      "checked_on": "2026-09-11"
    },
    {
      "source": "HHS Office for Civil Rights, Guidance on HIPAA and Cloud Computing",
      "checked_on": "2026-09-11"
    },
    {
      "source": "Proposed HIPAA Security Rule update, 90 FR 898, January 6, 2025 (Federal Register; not final as of the date checked)",
      "checked_on": "2026-09-11"
    },
    {
      "source": "FTC Health Breach Notification Rule, 16 CFR Part 318",
      "checked_on": "2026-09-11"
    }
  ],
  "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-hipaa-applicability-checker",
    "label": "Review your own documents against this framework with ISMS Copilot"
  },
  "tool_page": "https://www.ismscopilot.com/resources/hipaa-applicability-checker"
}

What the result rests on

Every result names its basis, as identifiers only (never standard text):

  • 45 CFR 160.103
  • 45 CFR 164.502(e)
  • 45 CFR 164.504(e)

Sources the rules were checked against, with the date each was last checked:

  • 45 CFR 160.103, definitions: covered entity, business associate, protected health information (eCFR, current), checked 2026-09-11
  • 45 CFR 164.502(e) and 164.504(e), business associate contracts (eCFR, current), checked 2026-09-11
  • HHS Office for Civil Rights, Covered Entities and Business Associates, checked 2026-09-11
  • HHS Office for Civil Rights, Guidance on HIPAA and Cloud Computing, checked 2026-09-11
  • Proposed HIPAA Security Rule update, 90 FR 898, January 6, 2025 (Federal Register; not final as of the date checked), checked 2026-09-11
  • FTC Health Breach Notification Rule, 16 CFR Part 318, checked 2026-09-11

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.

On this page