
Signalint
io.github.TranQui004Published by GitHub account TranQui004v1.2.1Updated Oct 24, 2026
Local stdio MCP server for cached, loop-aware JS/TS diagnostics (Oxlint, tsc, Biome, ESLint).
Overview
Local MCP server that runs JS/TS linters and compilers and gives coding agents bounded, prioritized diagnostics, verification deltas and loop detection.
- What you can do
- Run project-wide or incremental checks with caching and retrieve full issue details anchored to a check ID, plus loop and churn status for the session. Read immutable diagnostic snapshots and compare a baseline against a current check to see introduced, resolved and unchanged issues. Ingest external LSP or compiler diagnostics and read buffered live diagnostics with source provenance. Stage proposed fixes in memory, apply them to disk, or discard them.
- When to use it
- Useful when an AI coding agent works in a JavaScript or TypeScript repository and you want it to see compact, prioritized lint and type errors instead of raw compiler output, to verify that an edit reduced rather than shifted problems, and to avoid repeating the same failing fix.
- Requirements
- Runs locally over stdio, typically via npx signalint-mcp. Needs Node.js 22.12.0 or newer. The project must install its own engines (typescript, oxlint, eslint and/or @biomejs/biome); none are bundled. Initial setup runs npx signalint init, which writes signalint.config.json and configures installed MCP clients. Desktop clients only.
Installation
In SourceWeft
- Open Signalint in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Signalint
[CI] [npm version] [License: MIT] [Node.js]
Signalint is a reliable, read-only-by-default diagnostic intelligence layer for AI coding agents (Claude Code, Cursor, Codex, VS Code) and CI workflows.
Instead of flooding an agent's context window with thousands of raw compiler lines, Signalint normalizes diagnostics across compilers, linters, and language servers into bounded, priority-clustered issue summaries, calculates verification deltas against explicit baselines, and detects oscillating fix loops.
Key Differentiators
- 13 Complete MCP Tools: From incremental checks and immutable snapshots to live diagnostic ingestion and journaled transactional fix application.
- Verification Deltas: Exact arithmetic on introduced, resolved, and unchanged diagnostics with semantic identity matching that survives line shifts.
- Immutable Snapshots & Concurrency Safety: Isolated in-memory snapshot store keyed by
checkIdeliminates race collisions during concurrent checks. - Monorepo-Aware Planning: Unites package manifests (
pnpm-workspace.yaml) parsed via pure-JS YAML with glob negation exclusions and TypeScript Project References, ordering checks topologically. - Multi-Source Provenance: Distinguishes compiler, linter, and editor/LSP diagnostics across JavaScript, TypeScript, Python (Ruff/Mypy), Rust (Clippy), and Go (GolangCI-Lint).
- Portable Host Hooks: Native verify-after-change adapters for Claude Code, Cursor, Codex, and VS Code.
- In-Memory Previews & In-Process Rollback: In-memory previews never touch disk; apply uses per-file adjacent temporary-file replacement, pre-write drift detection, and in-process best-effort rollback for multi-file writes (does not claim persistent crash recovery if aborted abruptly).
Quick Start
1. Requirements
- Node.js >= 22.12.0 (utilizes native
node:sqlite). - Your project installs its own diagnostic engines (
typescript,oxlint,eslint, and/or@biomejs/biome). Signalint detects project-local installations and ships no bundled engines.
2. Initialize in your repository
This detects your project's linters/compilers, generates signalint.config.json, and configures your installed MCP clients.
3. Add to MCP Clients
Add Signalint to your MCP configuration (e.g. claude_desktop_config.json, .cursor/mcp.json):
Complete MCP Tools Catalog
Signalint exposes 13 strictly typed MCP tools over stdio:
See docs/mcp-contract.md for full JSON Schemas and error codes.
CLI Commands
Signalint includes a comprehensive command-line interface:
Monorepo Support
Signalint natively understands multi-package monorepos:
- Configure
"monorepoMode": "auto"insignalint.config.jsonto detectpnpm-workspace.yamlvia pure-JS YAML parsing with glob negation exclusions (!). - Strictly differentiates local workspace packages (
workspace:*) from external npm registry dependencies. - Builds a topological dependency graph uniting package manifests and TypeScript project references.
- Caches whole-program TypeScript builds in isolated per-package directories (
.signalint/cache/tsc/<project-id>/). - Changes to a shared package automatically invalidate dependent packages while keeping independent siblings cached.
See docs/monorepo.md for configuration and architecture.
Verify-After-Change Hooks
Automate post-edit verification without creating infinite agent loops:
- Native adapters for Claude Code, Cursor, Codex, and VS Code.
- Emits bounded context into prompt windows and blocks only on unresolved syntax/type errors.
See docs/hooks.md for setup instructions.
Documentation Index
- Architecture & Subsystems
- MCP Protocol Contract & Schemas
- Host Hook Adapters Guide
- Monorepo Planning & Incremental TypeScript
- Known Limitations & Risk Register
- Wire Reduction Benchmarks
- Security & Threat Model
License
MIT © 2026 Tran Trong Qui
Source: README.md at commit 6327008
Tools
0Version history
6- v1.2.1LatestOct 11, 2026
- v1.2.0Oct 10, 2026
- v1.1.2Oct 8, 2026
- v1.1.0Oct 8, 2026
- v1.0.0Oct 6, 2026
- v0.4.2Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts