Configure MCP server with HHS HIPAA Breach Portal — Healthcare Data Breach Tracker
The configuration above connects to the hosted Apify MCP server with the HHS HIPAA Breach Portal — Healthcare Data Breach Tracker Actor already loaded. It uses OAuth, so your client opens a browser window to sign you in to Apify on first use. No API token is needed. Clients without OAuth support can authenticate with an Authorization: Bearer header carrying an API token from API & Integrations in Apify Console.
Get a ready-to-use configuration for your MCP client with the HHS HIPAA Breach Portal — Healthcare Data Breach Tracker Actor preconfigured at https://mcp.apify.com/?tools=fetch-actor-details,samwise.agency/hhs-hipaa-breach-portal.
You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.