YanceLint MCP Server
Related Servers
Alternatives to YanceLint MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables real-time code analysis for JavaScript, TypeScript, and Python through Claude Desktop and other MCP clients, detecting bugs, code smells, and security vulnerabilities with automated quick fixes.794 npm4MIT
- AlicenseNot gradedqualityDmaintenanceCode linting and style checking tools for AI agents, exposed as an MCP server. Supports style checks, naming conventions, complexity analysis, dead code detection, and import analysis.25 npmMIT
- AlicenseAqualityFmaintenanceBridges Claude Code to Language Server Protocol (LSP) servers to enable semantic code intelligence features like navigation, refactoring, and real-time diagnostics. It supports multiple languages including TypeScript, Python, and Rust with multi-root workspace capabilities.191,373 npm21MIT
- AlicenseAqualityAmaintenanceEnables AI assistants and developers to analyze code for language-specific best practices and idiomatic patterns across programming languages, CI automation, and configuration formats.162MIT
- AlicenseBqualityDmaintenanceA multi-language code analysis server that helps LLMs or humans automatically lint, type-check, and improve code with minimal installation friction, currently supporting Python with plans for other languages.13MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server that provides clj-kondo linting capabilities for Clojure/ClojureScript/EDN files, useful for environments like Claude code and desktop that lack built-in linting.14 npm4MIT
TDQS
Scored across 3 tools
Each tool has a distinct purpose: check_health verifies server status and lists scanners, get_file_violations returns violations for a specific file, and get_project_summary provides aggregated totals. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case (check_health, get_file_violations, get_project_summary), with clear and predictable naming.
The server has 3 tools, which is reasonable for a focused linting service. While slightly lean, the tools cover the core functionality without unnecessary redundancy.
The set covers health checking, file-level violation retrieval, and project summary. Missing explicit support for per-tool configuration or detailed project-wide results, but the core use cases are addressed.