io.github.TranQui004/signalint
NPM · SIGNALINT-MCP · SCANNED SEP 20
Local stdio MCP server for cached, loop-aware JS/TypeScript diagnostics (Oxlint, tsc, Biome).
Available components
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. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 52 of 181 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to TranQui004/signalint). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 15 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 581 tokens (~116/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
npm · signalint-mcp
claude mcp add tranqui004-signalint -- npx -y signalint-mcp
{
"mcpServers": {
"tranqui004-signalint": {
"command": "npx",
"args": [
"-y",
"signalint-mcp"
]
}
}
} {
"servers": {
"tranqui004-signalint": {
"command": "npx",
"args": [
"-y",
"signalint-mcp"
]
}
}
} codex mcp add tranqui004-signalint -- npx -y signalint-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tranqui004-signalint": {
"type": "local",
"command": [
"npx",
"-y",
"signalint-mcp"
],
"enabled": true
}
}
} openclaw mcp add tranqui004-signalint --command npx --arg -y --arg signalint-mcp
mcp_servers:
tranqui004-signalint:
command: "npx"
args: ["-y", "signalint-mcp"] {
"McpServers": {
"tranqui004-signalint": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"signalint-mcp"
]
}
}
} assistant mcp add tranqui004-signalint -t stdio -c npx -a -y signalint-mcp
{
"mcpServers": {
"tranqui004-signalint": {
"command": "npx",
"args": [
"-y",
"signalint-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 0
- Stability: 0.97 → pass security
- 19 Sept 26 0
- Stability: pass → 0.97 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +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.
- 16 Sept 26 −1
- Stability: pass → 0.93 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +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.
- 11 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/signalint-mcp@0.4.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | TranQui004/signalint |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/TranQui004/signalint/.github/workflows/release.yml@refs/tags/v0.4.2 |
| Rekor log index | 2714052449 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b03f91ab08bdf7f4837614d636db41e972291ede3ad4aad8a98c6738ecf864a05f7770b478292a47fe72ddd0dbec231c533bd19d7d4e579e57553ce5c |
Background: How many MCP packages publish verified provenance →
Dependencies 181 packages
| Packages resolved | 181 |
|---|---|
| Deprecated | 1 |
| Stale | 51 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_files ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| clusters | array | – | – |
| code | string | – | – |
| engine | string | – | – |
| engines | object | – | – |
| fileRuleChurnWarning | – | – | – |
| loopWarning | – | – | – |
| message | string | – | – |
| schemaVersion | string | – | – |
| status | string | yes | – |
| totalIssues | integer | – | – |
| truncated | boolean | – | – |
No examples provided.
check_project ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| paths | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| clusters | array | – | – |
| code | string | – | – |
| engine | string | – | – |
| engines | object | – | – |
| fileRuleChurnWarning | – | – | – |
| loopWarning | – | – | – |
| message | string | – | – |
| schemaVersion | string | – | – |
| status | string | yes | – |
| totalIssues | integer | – | – |
| truncated | boolean | – | – |
No examples provided.
get_issue_detail ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| clusterId | string | – | – |
| issueId | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | – |
| issues | array | – | – |
| message | string | – | – |
| status | string | – | – |
No examples provided.
get_loop_status ~99
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| fileChurning | boolean | yes | – |
| fileRuleChurns | array | yes | – |
| looping | boolean | yes | – |
| signatures | array | yes | – |
No examples provided.
ping ~55
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| pong | boolean | yes | True when the server is responsive. |
No examples provided.
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.