Atlas / MCP servers / emiryasar / Code Analyzer

Code AnalyzerBLOCK

mcp/emiryasar/code-analyzer-1

A Model Context Protocol (MCP) server implementation for comprehensive code analysis. This tool integrates with Claude Desktop to provide code analysis capabilities through natural language interactions.

Verdict
BLOCK
Grade
D
Trust score
69 /100
Exposed tools
18 17r · 1w · 0d
Transport
stdio
License
MIT
Stars
39
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

The main purpose of the MCP tool is to adapt changes to the project intelligently. For instance, when a code modification or structural adjustment is needed, it aims to ensure that other related usages are also updated accordingly.

Currently, the project has a lot of bugs, and the tools are not functioning as expected sometimes. Due to work commitments, I can’t dedicate much time to it, but I’ll try to fix the issues and bring it to a working state whenever I find the time.

⚠️ WARNING: BACKUP RECOMMENDED This tool performs file operations that could potentially modify or delete files. Always backup your codebase before using any modification features.

Overview

The Model Context Protocol (MCP) Code Analyzer is a comprehensive code analysis and management tool that integrates with Claude Desktop. It analyzes code at both project and file levels, providing insights for needed changes and project understanding.

Prerequisites

  • Python 3.10 or later
  • Windows (Linux/MacOS support not yet tested)

Installation

# Clone the repository
git clone https://github.com/[your-username]/mcp-code-analyzer.git
cd mcp-code-analyzer

# Install dependencies and package
pip install -e .

Claude Desktop Integration

Configuration

  1. Access Claude Desktop config:
Win + R → %AppData%\Claude\
  1. Create/edit claude_desktop_config.json:
{
"globalShortcut": "Ctrl+Space",
"mcpServers": {
"code-analyzer": {
"command": "python",
"args": [
"-m",
"mcp_code_analyzer",
"--analyze-paths",
"C:\\Projects\\path1"
],
"type": "module"
}
}
}

Path Configuration

  • Multiple project paths can be specified in configuration
  • Additional paths or files can be analyzed via chat messages
  • No limit on number of analyzable paths/files

🛠️ Tools and Status

Working Tools

  • ✅ Project Analysis
Read from source at commit 57336eda3f59OBSERVED · 2026-10-08
Advertisement
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code
claude mcp add mcp-code-analyzer -- uvx mcp-code-analyzer
claude-desktop
{
  "mcpServers": {
    "mcp-code-analyzer": {
      "command": "uvx",
      "args": [
        "mcp-code-analyzer"
      ]
    }
  }
}
03

Exposed tools (18)

17 read · 1 write · 0 destructive.

ToolRiskDescription
analyze_code_structurereadAnalyze code structure and architecture
analyze_importswriteAnalyze import statements and dependencies
analyze_project_statisticsreadProject-wide statistics and metrics
analyze_project_structurereadDirectory structure and organization analysis with tree view
analyze_project_technologyreadDetect and analyze used technologies and frameworks
check_syntaxreadAdvanced syntax checking and analysis
code_modifierreadSafe code modification with impact analysis
file_operationsreadFile operations with MCP support
find_code_patternsreadDetect code patterns and anti-patterns
find_pattern_usagesreadFind pattern occurrences and analyze usage
find_referencesreadFind code references
manage_changesreadManage code changes and their application
preview_changesreadPreview code changes
search_codereadSearch code with pattern matching
search_contentreadSearch within file contents
search_filesreadAdvanced file search capabilities
validate_codereadValidate code quality and standards
version_controlreadAdvanced version control and history management
04

Trust audit

BLOCKgrade D · trust 69/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codeFAIL
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
declared (1 observation(s))
Network
none-observed
Shell
declared (3 observation(s))
Dependencies
not all pinned
Secrets in source
none-found

Findings (5)

HIGHCode injection · code.eval_exec · CWE-78, CWE-94, CWE-95
mcp_code_analyzer/tools/analysis_tools.py:1177
r"eval\(": "Use of eval() is dangerous",
Why it matters. evaluates text as code
Fix. remove; use a parser or a dispatch table
HIGHCode injection · code.eval_exec · CWE-78, CWE-94, CWE-95
mcp_code_analyzer/tools/analysis_tools.py:1178
r"exec\(": "Use of exec() is dangerous",
Why it matters. evaluates text as code
Fix. remove; use a parser or a dispatch table
LOWInsecure crypto · crypto.weak_hash · CWE-327, CWE-338
mcp_code_analyzer/tools/search_tools.py:697
return hashlib.md5(content.encode()).hexdigest()
LOWInsecure crypto · crypto.weak_hash · CWE-327, CWE-338
mcp_code_analyzer/tools/version_manager.py:394
return hashlib.md5(unique_data.encode()).hexdigest()[:12]
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
requirements.txt
chardet, astroid, pydantic, radon, networkx, mcp
Why it matters. 6 requirement(s) not pinned with ==
Fix. pin exact versions

Gates applied: no_behavioural_pass.

Audited 2026-10-08 · audit v0.4.1 · source sha 57336eda3f59full audit observations/trust-audit/mcp-server/emiryasar__code-analyzer-1.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-0857336eda3f59BLOCKD69first audit
06

Questions

What is the Code Analyzer MCP server?

A Model Context Protocol (MCP) server implementation for comprehensive code analysis. This tool integrates with Claude Desktop to provide code analysis capabilities through natural language interactions.

What tools does Code Analyzer expose?

18 in total: 17 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is Code Analyzer safe to connect to an agent?

No — not without reading the findings first. The audit graded it D (69/100) and found 2 critical or high issues in the source. Each one is listed on this page with the file and line it is on.

What credentials does Code Analyzer need?

No credential environment variables were found in its source, so it appears to need none.

How does Code Analyzer run?

It speaks stdio, so it runs as a local process your client starts. It is published on PyPI as mcp-code-analyzer.

How current is this page?

The grade is for one exact copy of the source (57336eda3f59), read on 2026-10-08. The repository is watched and re-audited when it changes.

Advertisement