compliance-checks vs HIPAA Agent
compliance-checks is a plugin bundle for AI coding tools published by cyberagentic. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). HIPAA Agent is an MCP server published by xbt786. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: c5d5a7d No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | compliance-checks | HIPAA Agent |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (hipaaagent.ai/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/cyberagentic/compliance-checks | github.com/xbt786/hipaa-agent-ai |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 402 (2 days ago) |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
compliance-checks
EU regulatory compliance checks for businesses. Assess whether your organisation is affected by NIS-2, classify AI systems under the EU AI Act, check GDPR compliance before introducing new applications, review technical security measures (TOMs), and audit data processing agreements. Each check asks a few targeted questions and produces a structured report with a clear risk rating and actionable next steps.
HIPAA Agent
HIPAA compliance AI agent — scan, grade, SRA, and generate compliance docs.
How to run each
compliance-checks As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install compliance-checks@claude-communityHIPAA Agent As a remote MCP server
claude mcp add --transport http hipaa-agent https://hipaaagent.ai/api/mcp --header "x-api-key: <YOUR_X_API_KEY>"Requires: x-api-key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only HIPAA Agent has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: compliance-checks · What it can do: HIPAA Agent · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.