Is "bwton-ecs-overall" on MCP Registry Safe to Install?

mikeeeshi · mcp · v1.0.2

Risk Assessment

Analyzed
82.03
out of 100
HIGH

9 security findings detected across all analyzers

MCP server analyzed for tool poisoning, prompt injection, and data exfiltration

Severity Breakdown

0
Critical
5
High
2
Medium
0
Low
0
Info

Finding Categories

4
Malware Signatures
1
Secrets
2
Network

YARA Rules Matched

4 rules
credential env files postinstall network communication postinstall file download postinstall system command

MCP Server Analysis

MCP servers expose tools and resources to AI assistants. Unlike browser extensions, they run as standalone processes with direct system access. Tool definitions are analyzed for prompt injection, data exfiltration, and tool poisoning patterns.

Detailed Findings

9 total

YARA Rule Matches

4 rules

Security Analysis Summary

Security Analysis Overview

bwton-ecs-overall is a mcp extension published by mikeeeshi. Version 1.0.2 has been analyzed by the Risky Plugins security platform, receiving a risk score of 82.03/100 (HIGH risk) based on 9 security findings.

Risk Assessment

This extension presents critical security risk. Severe issues were detected, potentially including malware indicators, exposed secrets, or dangerous behaviors. Installation is strongly discouraged until these issues are addressed.

Findings Breakdown

  • High: 5 finding(s)
  • Medium: 2 finding(s)

What Was Analyzed

The security assessment covers multiple analysis categories:

  • Malware Detection: YARA rule matching against 2,400+ malware signatures
  • Secret Detection: Scanning for exposed API keys, tokens, and credentials
  • Static Analysis: Code-level security analysis for common vulnerability patterns
  • Network Analysis: Detection of suspicious network communications and endpoints
  • Obfuscation Detection: Identification of code obfuscation techniques

Developer Information

bwton-ecs-overall is published by mikeeeshi on the mcp marketplace.

Recommendation

This extension is not recommended for installation without thorough manual review. Consider alternatives with lower risk scores, or contact the developer to address the identified security concerns.

Frequently Asked Questions