Signalint MCP server

by TranQui004·io.github.TranQui004/signalint·v0.4.2

No reviews yet

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

A92/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A92/100

full report

Adoption

Growing

1 stars64 downloads/wk

Reviews

Write one

Nobody has reviewed Signalint yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Signalint tools (5, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

check_fileswrite action
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 pro
check_projectwrite action
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 instea
get_issue_detail
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: "stal
get_loop_status
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
ping
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.

Public scan report

scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it

no findings

Code scan49 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 16 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

Install directly

Runs npx -y signalint-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add signalint -- npx -y signalint-mcp

Add to Cursor

Signalint: common questions

Is Signalint MCP server safe?: Yes, by our scan: it is graded A (92/100). Read the Signalint safety report
How do I install Signalint?: It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does Signalint need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Signalint maintained?: The last commit was 16 days ago (2026-09-04). The latest release is v0.4.2.