signalint
Related Servers
Alternatives to signalint
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn MCP server that integrates the high-performance Oxlint linter into AI-powered editors and development tools. It enables efficient JavaScript and TypeScript code analysis and linting through the Model Context Protocol.114 npm1Apache 2.0
- AlicenseAqualityDmaintenanceA lightweight MCP server that provides 40 tools for TypeScript/JavaScript refactoring and code intelligence, directly mapping to TypeScript's tsserver protocol commands for accurate structural changes and workspace analysis.4029 npm3MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides TypeScript 7 native language server capabilities (go to definition, find references, hover types, diagnostics) to coding agents, using the Go-based tsc compiler for fast and accurate semantic analysis.366 npm1MIT
- AlicenseCqualityCmaintenanceDeterministic MCP server for semantic analysis of JavaScript/TypeScript codebases, including frameworks like Vue, Angular, React, and Node. It provides tools for type checking, code metrics, framework-specific analysis, and quality heuristics via static parsing.1001MIT
- AlicenseNot gradedqualityCmaintenanceSemantic code intelligence MCP server for TypeScript/JavaScript codebases, enabling AI agents to retrieve specific symbols, types, and relationships without reading entire files.21MIT
- AlicenseAqualityDmaintenanceA TypeScript-aware MCP server that provides coding agents with repository discovery, code intelligence, and web project context for local codebases. It enables deep symbol navigation, diagnostic reporting, and structural analysis of monorepos without requiring full IDE integration.715 npm1MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: ping for health, check_project for full scans, check_files for incremental scans, get_issue_detail for inspecting results, and get_loop_status for loop detection. Descriptions explicitly cross-reference each other (e.g., check_project vs check_files) to guide selection, leaving no meaningful overlap.
Mostly consistent verb_noun pattern with check_project, check_files, get_issue_detail, and get_loop_status. The bare 'ping' deviates slightly, but it follows standard health-check convention so it remains readable and predictable.
Five tools is well-scoped for a lint/diagnostic server, with each tool earning its place across the scan-inspect-monitor workflow. No redundant or filler tools are present.
The surface covers the core lifecycle: health check, full and incremental scans, issue detail retrieval, and loop monitoring. Minor gaps exist (e.g., no explicit tool to list all clusters or clear/reset session history), but agents can work around these via existing tools.