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.15 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.4086 npm3MIT
- AlicenseNot gradedqualityBmaintenanceAn 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.31 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 gradedqualityAmaintenanceSemantic code intelligence MCP server for TypeScript/JavaScript codebases, enabling AI agents to retrieve specific symbols, types, and relationships without reading entire files.20MIT
- 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.75 npm1MIT
TDQS
Scored across 5 tools
Each tool has a clear, distinct responsibility: health check, full-project scan, incremental file scan, issue detail retrieval, and loop tracking. check_project and check_files are carefully differentiated by scope and caching semantics, with descriptions explicitly cross-referencing when to use each.
Four tools follow a clear check_/get_ verb-noun pattern, making their purpose predictable. ping is a one-word health-check exception, but it is idiomatic and does not create real inconsistency.
Five tools cover the core workflow of connecting, scanning, inspecting results, and monitoring loops without redundancy. Each tool earns its place, and the count is well within the ideal 3-15 range for a focused diagnostics server.
The toolset covers the full diagnostic lifecycle: full-project and incremental checking, issue detail retrieval, and loop detection. For a read-only lint/type diagnostics server, there are no obvious missing operations that would cause agent failures.