mcp-server-analyzer
by Anselmoo
README.md
# MCP Server Analyzer for Python 🐍🔍
<!-- mcp-name: io.github.Anselmoo/mcp-server-analyzer -->
[](https://safeskill.dev/scan/anselmoo-mcp-server-analyzer)
[](https://github.com/anselmoo/mcp-server-analyzer/actions/workflows/ci-cd.yml)
[](https://badge.fury.io/py/mcp-server-analyzer)
[](https://www.python.org/downloads/)
[](https://github.com/anselmoo/mcp-server-analyzer/pkgs/container/mcp-server-analyzer)
[](https://opensource.org/licenses/MIT)
[](https://codecov.io/gh/anselmoo/mcp-server-analyzer)
[](https://agentseal.org/mcp/mcp-server-analyzer)
[](https://anselmoo.github.io/mcp-server-analyzer/)
A powerful [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server that provides comprehensive Python code analysis using [**Ruff**](https://docs.astral.sh/ruff/) for linting, [**ty**](https://docs.astral.sh/ty/) for type checking, and [**Vulture**](https://github.com/jendrikseipp/vulture) for dead code detection. Perfect for AI assistants, IDEs, and automated code review workflows.
## 🚀 Quick Start
### VS Code Integration (One-Click Install)
For quick installation, use one of the one-click install buttons below...
[](https://insiders.vscode.dev/redirect/mcp/install?name=analyzer&config=%7B%22command%22%3A%22uvx%22%2C%22args%22%3A%5B%22mcp-server-analyzer%22%5D%7D) [](https://insiders.vscode.dev/redirect/mcp/install?name=analyzer&config=%7B%22command%22%3A%22uvx%22%2C%22args%22%3A%5B%22mcp-server-analyzer%22%5D%7D&quality=insiders)
[](https://insiders.vscode.dev/redirect/mcp/install?name=analyzer&config=%7B%22command%22%3A%22docker%22%2C%22args%22%3A%5B%22run%22%2C%22-i%22%2C%22--rm%22%2C%22ghcr.io%2Fanselmoo%2Fmcp-server-analyzer%22%5D%7D) [](https://insiders.vscode.dev/redirect/mcp/install?name=analyzer&config=%7B%22command%22%3A%22docker%22%2C%22args%22%3A%5B%22run%22%2C%22-i%22%2C%22--rm%22%2C%22ghcr.io%2Fanselmoo%2Fmcp-server-analyzer%22%5D%7D&quality=insiders)
For manual installation, add the following JSON block to your User Settings (JSON) file in VS Code. You can do this by pressing `Ctrl + Shift + P` and typing `Preferences: Open User Settings (JSON)`.
Optionally, you can add it to a file called `.vscode/mcp.json` in your workspace. This will allow you to share the configuration with others.
> Note that the `mcp` key is needed when using the `mcp.json` file.
**Using uvx (recommended):**
```json
{
"mcp": {
"servers": {
"analyzer": {
"command": "uvx",
"args": ["mcp-server-analyzer"]
}
}
}
}
```
**Using Docker:**
```json
{
"mcp": {
"servers": {
"analyzer": {
"command": "docker",
"args": ["run", "-i", "--rm", "ghcr.io/anselmoo/mcp-server-analyzer"]
}
}
}
}
```
### Universal Installation
```bash
# Install with uvx (recommended)
uvx install mcp-server-analyzer
# Install with pip
pip install mcp-server-analyzer
# Run with Docker
docker run ghcr.io/anselmoo/mcp-server-analyzer:latest
# Install from source
git clone https://github.com/anselmoo/mcp-server-analyzer.git
cd mcp-server-analyzer
uv sync --dev
uv run mcp-server-analyzer
```
## 📋 Features
- **🔍 RUFF Analysis**: Comprehensive Python linting with auto-fixes
- **🧠 ty Type Checking**: Fast Python type analysis with rule-based diagnostics
- **🧹 Dead Code Detection**: Find unused imports, functions, and variables with VULTURE
- **⚡ Biome JS/TS Analysis**: Fast linting and formatting for JavaScript and TypeScript
- **📊 Quality Scoring**: Combined analysis with quality metrics
- **🚀 FastMCP Framework**: High-performance MCP server implementation
- **🐳 Docker Ready**: Multi-architecture containers with security signing
- **🔒 Secure**: All releases signed with Sigstore for supply chain security
## 📈 Analysis Examples
### RUFF Linting Preview
See comprehensive linting analysis examples: **[📋 RUFF Analysis Preview](examples/preview-ruff.md)**
### VULTURE Dead Code Detection Preview
Explore dead code detection capabilities: **[🧹 VULTURE Analysis Preview](examples/preview-vulture.md)**
## 🛠️ Available Tools
| Tool | Description | Use Case |
| --------------- | ------------------------------------- | ------------------------------------ |
| `ruff-check` | Lint Python code with RUFF | Style violations, potential errors |
| `ruff-format` | Format Python code with RUFF | Code formatting and consistency |
| `ruff-check-ci` | CI/CD optimized RUFF output | GitHub Actions, GitLab CI |
| `ty-check` | Type-check Python code with ty | Type safety, incorrect return values |
| `vulture-scan` | Dead code detection | Unused imports, functions, variables |
| `biome-check` | Lint JS/TS code with Biome | Style violations, potential errors |
| `biome-format` | Format JS/TS code with Biome | Code formatting and consistency |
| `analyze-code` | Combined Ruff + ty + Vulture analysis | Complete code quality assessment |
## 🔧 Configuration
### Claude Desktop
Add to your `claude_desktop_config.json`:
```json
{
"mcpServers": {
"analyzer": {
"command": "uvx",
"args": ["mcp-server-analyzer"]
}
}
}
```
### Zed
Add to your Zed settings.json:
```json
"context_servers": {
"analyzer": {
"command": "uvx",
"args": ["mcp-server-analyzer"]
}
}
```
### Claude Code (project-level)
Place `.mcp.json` at your project root:
```json
{
"mcpServers": {
"analyzer": {
"command": "uvx",
"args": ["mcp-server-analyzer"]
}
}
}
```
## 🧪 Development
### Prerequisites
- Python 3.13+
- [uv](https://docs.astral.sh/uv/) (recommended) or pip
- Node.js 22+ (for Biome JS/TS analysis)
- [Docker](https://docker.com) (optional)
### Setup
```bash
# Clone repository
git clone https://github.com/anselmoo/mcp-server-analyzer.git
cd mcp-server-analyzer
# Install Python dependencies
uv sync --dev
# Install Biome (JS/TS analyzer)
npm ci
# Run tests
uv run pytest
# Run type checks
uv run ty check src tests
# Run pre-commit hooks
uv tool run pre-commit run --all-files
# Build Docker image
docker build -t mcp-server-analyzer .
```
### Testing
```bash
# Run all tests
uv run pytest tests/ -v
# Run with coverage
uv run pytest --cov=src/mcp_server_analyzer --cov-report=html
# Test specific functionality
uv run pytest tests/test_server.py::TestAnalyzers::test_ruff_with_sample_code
```
## 📊 Quality Metrics
The server provides quality scoring based on:
- **Ruff Issues**: Style violations, potential bugs, complexity metrics
- **ty Diagnostics**: Static typing errors and warnings
- **Dead Code Detection**: Unused imports, functions, variables
- **Combined Score**: Weighted quality assessment (0-100)
## 🔒 Security
- **Signed Releases**: All releases signed with [Sigstore](https://sigstore.dev/)
- **Container Signing**: Docker images signed with [Cosign](https://docs.sigstore.dev/cosign/overview/)
- **Trusted Publishing**: PyPI releases use GitHub OIDC trusted publishing
- **Vulnerability Scanning**: Automated security scanning in CI/CD
- **Supply Chain Security**: SLSA Build Level 3 compliance
- **Security Policy**: See [SECURITY.md](SECURITY.md) for vulnerability reporting
## 🔍 Data Handling & Transparency
- **In-memory only**: Code passed to tools is written to a temporary file, analyzed, and the file is deleted immediately — nothing is persisted between calls.
- **No network calls**: The server makes no outbound network connections during analysis.
- **No telemetry**: No usage data, analytics, or crash reports are collected.
- **Subprocess isolation**: ruff, ty, and vulture are invoked with fixed argument lists — no shell expansion or arbitrary command execution.
## 📚 Documentation
- **[Full Documentation](https://anselmoo.github.io/mcp-server-analyzer/)** - GitHub Pages docs
- **[Tools Reference](https://anselmoo.github.io/mcp-server-analyzer/tools/)** - Detailed tool parameters and return types
- **[MCP Specification](https://modelcontextprotocol.io/)** - Learn about Model Context Protocol
- **[FastMCP Framework](https://gofastmcp.com/)** - High-performance MCP implementation
- **[Ruff Documentation](https://docs.astral.sh/ruff/)** - Python linter and formatter
- **[ty Documentation](https://docs.astral.sh/ty/)** - Python type checker and language server
- **[Vulture Documentation](https://github.com/jendrikseipp/vulture)** - Dead code finder
## 🤝 Contributing
Contributions are welcome! Please see [CONTRIBUTING.md](CONTRIBUTING.md) for details.
1. Fork the repository
2. Create a feature branch (`git checkout -b feature/amazing-feature`)
3. Commit your changes using [Conventional Commits](https://www.conventionalcommits.org/)
4. Push to the branch (`git push origin feature/amazing-feature`)
5. Open a Pull Request
## 📝 License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
## 🙏 Acknowledgments
- [Astral](https://astral.sh/) for RUFF and uv
- [Jendrik Seipp](https://github.com/jendrikseipp) for VULTURE
- [Model Context Protocol](https://modelcontextprotocol.io/) team
- [FastMCP](https://gofastmcp.com/) framework
---
**Made with ❤️ for better Python code quality**
TDQS
B3.4/5.0
Scored across 8 tools
Disambiguation4/5
Most tools are clearly distinct by language and action (format, lint, type-check, dead-code scan). The only real ambiguity is ruff-check vs. ruff-check-ci, which differ only in CI-specific output formatting.
Naming Consistency4/5
Names generally follow a consistent 'tool-action' hyphenated pattern (ruff-format, biome-check, vulture-scan). analyze-code breaks the pattern slightly by leading with the action rather than the tool.
Tool Count4/5
Eight tools is a reasonable size for a code-analysis server. The count is slightly padded by ruff-check-ci and the combined analyze-code, which overlap with existing tools, but the overall scope remains manageable.
Completeness3/5
Python coverage is strong: format, lint, type-check, dead-code, and a combined analysis. JavaScript/TypeScript support is thinner, with only formatting and linting and no type-checking or dead-code detection, leaving a notable gap for a general analyzer.
Maintenance
ActivityMaintained
ResponsivenessSlow