Mund — MCP Security Scanner MCP server

Read from the package source without running it. The installed server may list more.

• mund_acknowledge_alert

  Mark a security event/alert as acknowledged. Args: - event_id (string): ID of the event to acknowledge - acknowledged_by (string): Optional name/ID of acknowledger Returns: Confirmation of acknowledgment

• mund_add_rule

  Add a custom security detection rule. Create custom rules to detect specific patterns in content. Rules use regular expressions for pattern matching and can be configured with different severity levels and actions. Args: - id (string): Unique rule identifier (lowercase, alphanumeric, underscores) - name (string): Human-readable rule name - description (string): Optional description - type: Detecti

• mund_allowlist_pattern

  Add a pattern to the allowlist. Allowlisted patterns will be ignored by detection rules. Args: - pattern (string): Pattern to allowlist - type: Type of pattern Returns: Confirmation of allowlist addition

• mund_audit_mcp_permissions

  Analyze the permission scope and capabilities of an MCP server's tools. Identifies network access, filesystem operations, command execution, and other potentially dangerous capabilities.

• mund_block_pattern

  Add a pattern to the blocklist. Blocked patterns will always be flagged regardless of other rules. Args: - pattern (string): Pattern to block - type: Type of pattern (secret, pii, code_pattern, injection, exfiltration) Returns: Confirmation of blocklist addition

• mund_check_typosquatting

  Check if an MCP server name is potentially typosquatting a known legitimate server. Compares against a list of official and common MCP servers.

• mund_check_url

  Check if a URL is safe to access. Validates URLs against known dangerous patterns including: - Data exfiltration services (webhook.site, requestbin, etc.) - IP-based URLs (often used to bypass domain filtering) - Suspicious TLDs (.tk, .ml, etc.) - Data URLs (can contain arbitrary content) Args: - url (string): The URL to check (required) - tool_name (string): Name of tool attempting access (option

• mund_configure_notification

  Configure a notification channel for security alerts. Note: Full configuration requires environment variables. This tool can update webhook URLs and minimum severity settings at runtime. Args: - type: Channel type (slack, teams, email, webhook) - webhook_url: Webhook URL (for slack, teams, webhook) - min_severity: Minimum severity to notify Returns: Confirmation of configuration

• mund_get_events

  Retrieve recent security events from the Mund monitoring system. Supports filtering and pagination for efficient event retrieval. Args: - limit (number): Maximum events to return, 1-1000 (default: 50) - offset (number): Skip this many events for pagination (default: 0) - severity ('critical' | 'high' | 'medium' | 'low' | 'info'): Filter by severity - type: Filter by detection type - acknowledged (

• mund_get_status

  Get the current status of the Mund monitoring system. Returns information about: - Active analyzers and their status - Number of rules loaded - Configured notification channels - Block mode status - Recent event statistics

• mund_list_rules

  List all configured detection rules. Args: - type: Optional filter by detection type - enabled_only: Only show enabled rules (default: false) Returns: Array of rule configurations

• mund_remove_rulewrite action

  Remove a custom detection rule by ID. Note: Built-in rules cannot be removed, only disabled. Args: - id (string): ID of the rule to remove Returns: Confirmation of rule removal

• mund_scan_content
• mund_scan_mcp_server

  Scan an MCP server manifest (server.json) for security issues before installation. Detects prompt injection in tool descriptions, typosquatting, embedded secrets, and dangerous permissions.

• mund_validate_command

  Validate a shell command for safety before execution. Checks for dangerous patterns including: - Destructive commands (rm -rf, format, etc.) - Privilege escalation (sudo, chmod 777, etc.) - Network exfiltration (curl to suspicious URLs, etc.) - Code injection (eval, exec with variables, etc.) Args: - command (string): Shell command to validate (required) - tool_name (string): Name of tool executin

• Code scan66 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 34 days ago12/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

88/100

higher than 80% of 4,460 AI and agents servers

Tools

15

the typical AI and agents server has 6

Tools that change things

7%

typical: 0%. Fewer write tools means less an agent can break

Mund — MCP Security Scanner: common questions

Is Mund — MCP Security Scanner MCP server safe?

Yes, by our scan: it is graded A (88/100). Read the Mund — MCP Security Scanner safety report

How do I install Mund — MCP Security Scanner?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Mund — MCP Security Scanner need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Mund — MCP Security Scanner maintained?

The last commit was 72 days ago (2026-08-24). The latest release is v0.1.12.

What can I use instead of Mund — MCP Security Scanner?

Servers from other publishers that do the same job: Shellward MCP server, Agent Security Scanner MCP server and HOL Guard MCP server.

How does Mund — MCP Security Scanner compare with other AI and agents MCP servers?

safety score 88/100 (higher than 80% of 4,460 AI and agents servers); tools 15 (the typical AI and agents server has 6); tools that change things 7% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.