HIPAA Agent

io.github.xbt786Published by GitHub account xbt786v2.0.0Updated Oct 24, 2026

HIPAA compliance AI agent — scan, grade, SRA, and generate compliance docs.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant run HIPAA compliance scans, grade results, perform security risk assessments, and generate compliance documents.

What you can do
This remote MCP server provides a HIPAA compliance AI agent. According to its description, it can scan systems, assign compliance grades, carry out security risk assessments (SRA), and generate compliance documentation. The manifest does not list individual tool names, so the exact tool surface is not documented here.
When to use it
Use it when you need an assistant to help assess HIPAA compliance posture, obtain a compliance grade, run a security risk assessment, or draft compliance documentation. It is aimed at teams working with protected health information or preparing for HIPAA-related review. Grade lookups are available on the free tier, while full scans and reports require a paid key.
Requirements
A remote MCP endpoint at using streamable HTTP. An API key from hipaaagent.ai/developers is required and must be sent in the x-api-key header. No packages or environment variables are declared. Network access to the remote endpoint is needed.
Before you install
The server requires a secret API key supplied in the x-api-key header; treat it as a credential and avoid exposing it in logs or shared configuration. The description states that a free tier only allows grade lookups, while a paid key is required for full scans and reports, so costs may apply. Compliance scans and generated documents may involve sensitive organizational or health-related data being sent to a third-party remote service.

Installation

In SourceWeft

  1. Open HIPAA Agent in the dashboard and add it to a workspace.
  2. Connect x-api-key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.xbt786%2Fhipaa-agent/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "hipaa-agent": {
      "type": "http",
      "url": "https://hipaaagent.ai/api/mcp",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.