Asterisk Security Server

Scans individual code snippets for security vulnerabilities. This tool should be used when the user asks to scan or generate a specific snippet, implement a change, feature, etc. or specifically mentions to make sure that it's secure. Args: code_snippet: The code snippet to analyze for security vulnerabilities Returns: Markdown-formatted security analysis report

Scans the entire codebase for security vulnerabilities. If the user asks to scan the entire codebase for security issues, this tool should be used. Provide absolute file paths to the files you want to scan. The MCP server will read the file contents from your local machine and send them to the API server for analysis. Args: file_paths: List of absolute paths to the files to analyze Returns: Markdown-formatted security analysis report with line numbers

Verifies if code changes made thus far introduce any security vulnerabilities. If the user asks to verify or check for security issues after a long chat or interaction, this tool should be used to pass in code changes made during the chat. Each change should include the absolute file path and the modified code snippet. Args: changes: List of dictionaries with 'file_path' (absolute) and 'code_snippet' (changed code) Returns: Markdown-formatted security verification report

Opens the settings UI when the user enters "/asterisk". This tool should only be called when the user enters "/asterisk" in the chat. It opens a beautiful yet minimal settings UI that looks good in every operating system. The UI lets users configure Asterisk MCP without using CLI flags. Args: command: The command entered by the user (must be "/asterisk") Returns: A message indicating the settings UI was opened