# io.github.TranQui004/signalint (npm · signalint-mcp)

Local stdio MCP server for cached, loop-aware JS/TypeScript diagnostics (Oxlint, tsc, Biome).

- Trust score: 93/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `signalint-mcp`: 93/100 (this document), [markdown](https://verifymcp.io/servers/tranqui004-signalint/signalint-mcp.md), [page](https://verifymcp.io/servers/tranqui004-signalint/signalint-mcp)

## Channel facts

- Registry: `npm`
- Package: `signalint-mcp`
- Version: `0.4.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 52 of 181 dependencies flagged as unhealthy (1 deprecated).
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to TranQui004/signalint).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 15 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 581 tokens (~116/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.TranQui004/signalint MCP server?

io.github.TranQui004/signalint runs locally as an npm package, launched with npx -y signalint-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add tranqui004-signalint -- npx -y signalint-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "tranqui004-signalint": {
      "command": "npx",
      "args": [
        "-y",
        "signalint-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tranqui004-signalint": {
      "command": "npx",
      "args": [
        "-y",
        "signalint-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add tranqui004-signalint -- npx -y signalint-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tranqui004-signalint": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "signalint-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tranqui004-signalint --command npx --arg -y --arg signalint-mcp
```

### Hermes

```yaml
mcp_servers:
  tranqui004-signalint:
    command: "npx"
    args: ["-y", "signalint-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "tranqui004-signalint": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "signalint-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add tranqui004-signalint -t stdio -c npx -a -y signalint-mcp
```

### Other

```json
{
  "mcpServers": {
    "tranqui004-signalint": {
      "command": "npx",
      "args": [
        "-y",
        "signalint-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 93, 0)

- [security] Stability: 0.97 → pass

### 2026-09-19 (score 93, 0)

- [functional] Stability: pass → 0.97

### 2026-09-18 (score 93, 0)

- [security] Stability: 0.97 → pass

### 2026-09-17 (score 93, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 92, −1)

- [functional] Stability: pass → 0.93

### 2026-09-15 (score 93, 0)

- [security] Stability: 0.97 → pass

### 2026-09-14 (score 93, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 92, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `ping` (~55 tokens)

Checks whether the Signalint MCP server is responsive. Read-only; returns the string "pong" with no side effects. Use this to verify the server is connected before running diagnostics. Invalid arguments return an error response; no authentication is required.

Output parameters:

- `pong` (boolean): True when the server is responsive.

### `check_project` (~117 tokens)

Runs and clusters Oxlint and TypeScript (and optionally Biome) lint and type diagnostics for one or more project paths. Read-only; no files are written or modified. Paths default to the project root (".") when omitted; paths must be relative and within the project directory — absolute paths or paths outside the root return an error response. Use this for a full project scan; use check_files instead for faster incremental checks after editing specific files. Each call re-runs all enabled engines with no caching.

Input parameters:

- `paths` (array)

Output parameters:

- `clusters` (array)
- `code` (string)
- `engine` (string)
- `engines` (object)
- `fileRuleChurnWarning`
- `loopWarning`
- `message` (string)
- `schemaVersion` (string)
- `status` (string)
- `totalIssues` (integer)
- `truncated` (boolean)

### `check_files` (~184 tokens)

Runs Oxlint and TypeScript (and optionally Biome) lint and type diagnostics on a specific list of files, using per-engine content-hash caching to skip unchanged files. Read-only; no files are written or modified. Use this for incremental checks after editing specific files; use check_project for a full project scan. The files parameter expects relative file paths (not glob patterns) within the project directory — absolute paths or paths outside the root return an error response. Caching is file-content-hash-based: a file is re-checked only when its content or the engine's config file (e.g., .oxlintrc, tsconfig.json) has changed since the last call, not based on git status. TypeScript is a whole-program engine: it re-runs whenever any TypeScript file in the request has changed content.

Input parameters:

- `files` (array, required)

Output parameters:

- `clusters` (array)
- `code` (string)
- `engine` (string)
- `engines` (object)
- `fileRuleChurnWarning`
- `loopWarning`
- `message` (string)
- `schemaVersion` (string)
- `status` (string)
- `totalIssues` (integer)
- `truncated` (boolean)

### `get_issue_detail` (~126 tokens)

Returns the full issue list for either one cluster ID or one issue ID from the most recent check_project or check_files call. Read-only; no files are written or modified. Supply exactly one of clusterId or issueId — supplying both or neither returns an argument error. If the referenced cluster or issue no longer exists in the latest results (e.g., after re-running a check), returns a status: "stale" response instead of an error; call check_project or check_files again to refresh.

Input parameters:

- `clusterId` (string)
- `issueId` (string)

Output parameters:

- `code` (string)
- `issues` (array)
- `message` (string)
- `status` (string)

### `get_loop_status` (~99 tokens)

Returns all diagnostic issue signatures currently flagged as looping (repeatedly appearing and disappearing) in this server session. Read-only; no files are written or modified. Loop history is accumulated across all check_project and check_files calls in this process lifetime, and is restored from .signalint/session.jsonl on startup. Takes no parameters. Use this to identify which diagnostics an agent is oscillating on; use check_project or check_files to run fresh diagnostics.

Output parameters:

- `fileChurning` (boolean)
- `fileRuleChurns` (array)
- `looping` (boolean)
- `signatures` (array)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/tranqui004-signalint/signalint-mcp#diagnostics

## Score history

- 2026-09-20: 93
- 2026-09-19: 93
- 2026-09-18: 93
- 2026-09-17: 93
- 2026-09-16: 92
- 2026-09-15: 93
- 2026-09-14: 93
- 2026-09-13: 92
- 2026-09-12: 92
- 2026-09-11: 92
- 2026-09-10: 91
- 2026-09-09: 93
- 2026-09-08: 93
- 2026-09-07: 93
- 2026-09-06: 93
- 2026-09-05: 92
- 2026-09-04: 92
- 2026-09-03: 92
- 2026-09-02: 91
- 2026-09-01: 91
- 2026-08-31: 90
- 2026-08-30: 90
- 2026-08-29: 89
- 2026-08-28: 89
- 2026-08-27: 88
- 2026-08-26: 88
- 2026-08-25: 86
- 2026-08-24: 85
- 2026-08-23: 85
- 2026-08-22: 84

## Common questions

### What is the io.github.TranQui004/signalint MCP server?

io.github.TranQui004/signalint is an MCP server listed in the public MCP registry as io.github.TranQui004/signalint. Local stdio MCP server for cached, loop-aware JS/TypeScript diagnostics (Oxlint, tsc, Biome). This page covers its npm package (signalint-mcp).

### Is the io.github.TranQui004/signalint MCP server safe to use?

io.github.TranQui004/signalint scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.TranQui004/signalint MCP server expose?

io.github.TranQui004/signalint exposes 5 tools: ping, check_project, check_files, get_issue_detail, get_loop_status. Their descriptions and schemas cost roughly 581 tokens of context every time the server is loaded.

### Is the io.github.TranQui004/signalint MCP server still maintained?

io.github.TranQui004/signalint is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.TranQui004/signalint MCP server under?

io.github.TranQui004/signalint declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/signalint-mcp
- Socket report: https://socket.dev/npm/package/signalint-mcp
- Repository: https://github.com/TranQui004/signalint
- Changelog RSS feed: https://verifymcp.io/servers/tranqui004-signalint/signalint-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/tranqui004-signalint/signalint-mcp.json
- HTML version of this page: https://verifymcp.io/servers/tranqui004-signalint/signalint-mcp