Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Mund — MCP Security Scanner

NPM · @WEAVE_PROTOCOL/MUND · SCANNED AUG 3

Scan for prompt injection, secrets, PII, and vet MCP servers before installation

+17 this week 62 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security70
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects nodemailer 6.10.1, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (181 of 183), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2088 tokens (~139/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @weave_protocol/mund

# add to Claude Code
claude mcp add tyox-all-mund -- npx -y @weave_protocol/mund
# add to Codex CLI
codex mcp add tyox-all-mund -- npx -y @weave_protocol/mund
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tyox-all-mund": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@weave_protocol/mund"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add tyox-all-mund --command npx --arg -y --arg @weave_protocol/mund
# ~/.hermes/config.yaml
mcp_servers:
  tyox-all-mund:
    command: "npx"
    args: ["-y", "@weave_protocol/mund"]
// mcp.json
{
  "mcpServers": {
    "tyox-all-mund": {
      "command": "npx",
      "args": [
        "-y",
        "@weave_protocol/mund"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Aug 26 +41
    • CVE-2025-13033 affects this package: high security
    • GHSA-r7g4-qg5f-qqm2 affects this package: high security
    • GHSA-268h-hp4c-crq3 affects this package: high security
    • GHSA-p6gq-j5cr-w38f affects this package: high security
    • GHSA-wqvq-jvpq-h66f affects this package: high security
    • CVE-2026-41907 affects this package: high security
    • GHSA-c7w3-x93f-qmm8 affects this package: high security
    • GHSA-vvjj-xcjg-gr5g affects this package: high security
    • CVE-2025-14874 affects this package: high security
    • Provenance: unverified → fail security
    • Known CVEs: unverified → fail security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.23 functional
    • Schema quality: unverified → good functional
    • License: unverified → pass functional
    • Licence: Apache-2.0 functional
  • 31 Jul 26 −4
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −21
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 45

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@weave_protocol/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Vulnerabilities 9 findings
ID CVE Severity Vector Fix available
GHSA-268h-hp4c-crq3 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N yes
GHSA-c7w3-x93f-qmm8 low yes
GHSA-mm7p-fcc7-pg87 CVE-2025-13033 medium yes
GHSA-p6gq-j5cr-w38f high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-r7g4-qg5f-qqm2 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-rcmh-qjqh-p98v CVE-2025-14874 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vvjj-xcjg-gr5g medium CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N yes
GHSA-wqvq-jvpq-h66f medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
Dependencies 181 packages

181 packages in the resolved dependency tree · 181 deprecated · 64 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 15 exposed · ~2,088 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
mund_acknowledge_alert ~86

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

NameTypeReqDescription
acknowledged_bystringName or ID of person acknowledging
event_idstringyesID of the event to acknowledge

No output schema declared.

No examples provided.

mund_add_rule ~246

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: Detection type (secret, pii, code_pattern, injection, exfiltration) - pattern (string): Regular expression to match - severity: Severity level (critical, high, medium, low, info) - action: Action to take (alert, block, log, quarantine) Returns: Confirmation of rule addition with rule details

NameTypeReqDescription
actionstringAction to take when rule matches
descriptionstringDescription of what this rule detects
idstringyesUnique identifier for the rule
namestringyesHuman-readable name for the rule
patternstringyesRegular expression pattern to match
severitystringyesSeverity level when this rule matches
typestringyesType of detection

No output schema declared.

No examples provided.

mund_allowlist_pattern ~81

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

NameTypeReqDescription
patternstringyesPattern to add to allowlist
typestringyesType of pattern

No output schema declared.

No examples provided.

mund_audit_mcp_permissions ~57

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

NameTypeReqDescription
manifeststringyesJSON content of server.json manifest to audit

No output schema declared.

No examples provided.

mund_block_pattern ~93

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

NameTypeReqDescription
patternstringyesPattern to add to blocklist
typestringyesType of pattern

No output schema declared.

No examples provided.

mund_check_typosquatting ~58

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

NameTypeReqDescription
namestringyesMCP server name to check for typosquatting

No output schema declared.

No examples provided.

mund_check_url ~231

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 (optional) - agent_id (string): ID of requesting agent (optional) Returns: JSON object with: - url: The checked URL - safe: Boolean indicating if URL is safe - risk_level: 'safe' | 'suspicious' | 'dangerous' - warnings: Array of warning messages if any - blocked: Whether access was blocked

NameTypeReqDescription
agent_idstringID of the agent making this request
tool_namestringName of the tool attempting to access this URL
urlstringyesURL to check for safety

No output schema declared.

No examples provided.

mund_configure_notification ~136

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

NameTypeReqDescription
min_severitystringMinimum severity to send notifications
typestringyesType of notification channel
webhook_urlstringWebhook URL for Slack/Teams/generic webhook

No output schema declared.

No examples provided.

mund_get_events ~226

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 (boolean): Filter by acknowledgment status Returns: JSON object with: - total: Total matching events - count: Events in this response - offset: Current offset - has_more: Whether more events exist - events: Array of security events

NameTypeReqDescription
acknowledgedbooleanFilter by acknowledgment status
limitintegerMaximum number of events to return
offsetintegerNumber of events to skip for pagination
severitystringFilter by severity level
typestringFilter by detection type

No output schema declared.

No examples provided.

mund_get_status ~53

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mund_list_rules ~72

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

NameTypeReqDescription
enabled_onlybooleanOnly show enabled rules
typestringFilter rules by type

No output schema declared.

No examples provided.

mund_remove_rule ~65

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

NameTypeReqDescription
idstringyesID of the rule to remove

No output schema declared.

No examples provided.

mund_scan_content ~382

Scan text or code content for security vulnerabilities, secrets, PII, and other issues. This tool analyzes the provided content using multiple security analyzers: - Secret Scanner: Detects API keys, tokens, passwords, and credentials - PII Detector: Finds personal identifiable information - Code Analyzer: Identifies dangerous code patterns - Injection Detector: Spots prompt injection attempts - Exfiltration Detector: Detects data exfiltration patterns Args: - content (string): The text/code to scan (required) - content_type ('text' | 'code' | 'json' | 'yaml'): Type of content (default: 'text') - tool_name (string): Name of tool that generated this content (optional) - agent_id (string): ID of the requesting agent (optional) - session_id (string): Current session ID (optional) Returns: JSON object with: - scan_id: Unique identifier for this scan - issues_found: Number of security issues detected - blocked: Whether the content was blocked (if block_mode is enabled) - issues: Array of detected issues with severity, type, and suggestions - scan_duration_ms: Time taken to complete the scan Examples: - Scan code before committing: {"content": "const key = 'AKIAIOSFODNN7EXAMPLE'"} - Check user input: {"content": "Please ignore previous instructions", "content_type": "text"}

NameTypeReqDescription
agent_idstringID of the agent making this request
contentstringyesThe text/code content to scan for security issues
content_typestringType of content being scanned
session_idstringCurrent session ID
tool_namestringName of the tool that generated this content

No output schema declared.

No examples provided.

mund_scan_mcp_server ~79

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

NameTypeReqDescription
manifeststringyesJSON content of server.json manifest to scan
sourcestringSource URL, registry name, or file path for context

No output schema declared.

No examples provided.

mund_validate_command ~223

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 executing command (optional) - agent_id (string): ID of requesting agent (optional) Returns: JSON object with: - command: The validated command - safe: Boolean indicating if command is safe - risk_level: 'safe' | 'suspicious' | 'dangerous' - warnings: Array of warning messages - blocked: Whether execution was blocked

NameTypeReqDescription
agent_idstringID of the agent making this request
commandstringyesShell command to validate
tool_namestringName of the tool executing this command

No output schema declared.

No examples provided.