A
licenseNot graded
qualityD
maintenanceEnables EU AI Act compliance for AI agent systems by providing risk classification, audit trails, gap analysis, and evidence package generation.
65
MIT
HIPAA Agent
Server Details
HIPAA compliance AI agent — scan, grade, SRA, and generate compliance docs.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
get_policies1 field changed- added
Input schema / properties / notification_emailAdded value: +{ + "description": "If provided, emails all policies to this address as a formatted digest", + "type": "string" +}
1 tool update
- Added
get_blockchain_anchor
1 tool update
- Added
get_threat_intel
2 tool updates
- Added
get_model_insights - Added
get_state_coverage
1 tool update
- Added
execute_agent_baa
1 tool update
- Added
get_reputation
30 tool updates
- First observed
batch_scan - First observed
check_vendor - First observed
generate_baa - First observed
generate_sra - First observed
get_audit_log - First observed
get_breach - First observed
get_breach_probability - First observed
get_breach_score - First observed
get_compliance_delta - First observed
get_compliance_score - First observed
get_compliance_state - First observed
get_controls - First observed
get_evidence_package - First observed
get_incidents - First observed
get_internal_findings - First observed
get_internal_scan_status - First observed
get_outreach_status - First observed
get_policies - First observed
get_practice_summary - First observed
get_report - First observed
get_scan_status - First observed
get_training_status - First observed
get_vendor_baa_list - First observed
list_webhooks - First observed
log_incident - First observed
lookup_practice - First observed
scan_practice - First observed
subscribe_webhook - First observed
trigger_internal_scan - First observed
validate_workflow
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Compliance frameworks (SOC 2, ISO 27001, CMMC, NIST, more) delivered to AI agents as MCP tools.
1Pay-per-call cybersecurity for AI agents: vuln scans, threat intel, compliance, code security.
Governance maturity assessment, compliance gap analysis, and evidence-linked briefs for AI agents.
Scans schema metadata to classify PHI, score HIPAA readiness, and generate compliant migrations.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI agents to evaluate clinical AI models for adversarial robustness, privacy leakage, and standards compliance, producing a Security Posture Score.10Apache 2.0
- AlicenseAqualityCmaintenanceSecurity co-pilot for AI agents. Scans for vulnerabilities like prompt injection, infinite loops, and token bombing in AI Agents, audits MCP servers, verifies AGENTS.md governance, and generates EU AI Act compliance reports.10863Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables LLMs to perform automated compliance scanning of AWS infrastructure against PCI-DSS, CIS, and Well-Architected frameworks. It provides tools for scanning, remediation, and audit report generation.MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.7/5.0
Disambiguation4/5
Most tools have distinct purposes, such as scanning, retrieving compliance data, managing BAAs, or handling incidents. However, some overlap exists, like 'get_breach_probability' and 'get_breach_score' which both assess breach risk, potentially causing confusion. Descriptions help differentiate them, but the overlap is noticeable.
Naming Consistency5/5
Tool names follow a highly consistent verb_noun pattern throughout, using snake_case uniformly. Examples include 'scan_practice', 'get_compliance_score', and 'log_incident'. This predictability makes the set easy to navigate and understand.
Tool Count2/5
With 36 tools, the count is excessive for the HIPAA compliance domain, leading to potential bloat. While the tools cover many aspects, a more streamlined set could improve usability without sacrificing functionality, as some tools might be redundant or overly granular.
Completeness5/5
The tool set provides comprehensive coverage for HIPAA compliance management, including scanning, monitoring, reporting, incident handling, vendor management, and audit trails. There are no obvious gaps; it supports full lifecycle operations from assessment to evidence compilation.