Skip to main content
Glama
eludden35

HIPAA Guardian MCP Server

getSecureCodingChecklist

Generate secure coding checklists to help developers implement HIPAA-compliant practices when building healthcare applications that handle protected health information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
schemaYes

Implementation Reference

  • The async handler function for the 'getSecureCodingChecklist' tool, which returns a static markdown checklist for HIPAA-compliant secure coding practices.
        async () => {
            return {
                content: [{
                    type: 'text',
                    text: `
    # HIPAA Secure SDLC Checklist
    
    1.  **Data Minimization:** Does this feature only collect the minimum necessary PHI to function?
    2.  **Input Validation:** Are all inputs that could potentially contain PHI (e.g., text fields, file uploads) properly validated and sanitized to prevent injection attacks?
    3.  **Authentication & Authorization:** Is every endpoint that touches PHI protected with authentication? Does the code check if the authenticated user is authorized to access the specific record they are requesting?
    4.  **Secure Data Transmission:** Is all data, especially PHI, transmitted using strong, modern TLS (1.2+)?
    5.  **Secure Data Storage:** Is sensitive data encrypted at rest? Are you using platform-recommended secure storage APIs for tokens and keys?
    6.  **Audit Logging:** Does the code generate a detailed, immutable audit log for any action that creates, reads, updates, or deletes PHI? The log must include user ID, timestamp, and action taken.
    7.  **Error Handling & Information Disclosure:** Do error messages avoid revealing sensitive information (e.g., "User 'john.doe@email.com' not found" is a disclosure; "Invalid username or password" is not).
    8.  **Dependency Scanning:** Are you regularly scanning third-party libraries for known vulnerabilities?
    `
                }]
            };
        }
  • server.ts:233-258 (registration)
    The registration of the 'getSecureCodingChecklist' tool using server.tool(), including schema (empty input) and inline handler.
    server.tool(
        'getSecureCodingChecklist',
        {
            description: 'Provides a checklist for developers to ensure HIPAA compliance throughout the Software Development Lifecycle (SDLC).',
            schema: z.object({}),
        },
        async () => {
            return {
                content: [{
                    type: 'text',
                    text: `
    # HIPAA Secure SDLC Checklist
    
    1.  **Data Minimization:** Does this feature only collect the minimum necessary PHI to function?
    2.  **Input Validation:** Are all inputs that could potentially contain PHI (e.g., text fields, file uploads) properly validated and sanitized to prevent injection attacks?
    3.  **Authentication & Authorization:** Is every endpoint that touches PHI protected with authentication? Does the code check if the authenticated user is authorized to access the specific record they are requesting?
    4.  **Secure Data Transmission:** Is all data, especially PHI, transmitted using strong, modern TLS (1.2+)?
    5.  **Secure Data Storage:** Is sensitive data encrypted at rest? Are you using platform-recommended secure storage APIs for tokens and keys?
    6.  **Audit Logging:** Does the code generate a detailed, immutable audit log for any action that creates, reads, updates, or deletes PHI? The log must include user ID, timestamp, and action taken.
    7.  **Error Handling & Information Disclosure:** Do error messages avoid revealing sensitive information (e.g., "User 'john.doe@email.com' not found" is a disclosure; "Invalid username or password" is not).
    8.  **Dependency Scanning:** Are you regularly scanning third-party libraries for known vulnerabilities?
    `
                }]
            };
        }
    );
  • The Zod schema for the tool, which accepts no input parameters.
    schema: z.object({}),
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/eludden35/hipaa-guardian-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server