@eslint/mcp

MCPattested
v0.3.5UnknownApache-2.0Updated 5mo agonpmGitHub

MCP server for ESLint

Model Context Protocol (MCP) server for ESLint. The ESLint MCP server is designed to be run by an IDE-based MCP client like Visual Studio Code's Copilot. The command is: You can also run the server from the ESLint CLI, such as: For further instructions please see the documentation. Apache 2.0 <!-- NOTE: This section is autogenerated. Do not manually edit.--> <!--sponsorsstart--> The following…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
24kDownloads/wk
345GitHub stars
51Forks
5mo agoLast update
Package
AuthorUnknown
LicenseApache-2.0
Version0.3.5
Sourcenpm
npm@eslint/mcp
GitHubeslint/rewrite
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · a4f71e8
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface1 tool · none privileged
Security scan✓ Cleanv0.3.7 · 3mo agoHow well does this scan work?
EvalsNone
IndexedMay 24, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

1 tool · none privileged
Statically extracted from the published packagev0.3.7 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

lint-filesNo description published

This tool published no description. Forge does not invent one.

0 of 1 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Model Context Protocol (MCP) server for ESLint. The ESLint MCP server is designed to be run by an IDE-based MCP client like Visual Studio Code's Copilot. The command is: You can also run the server from the ESLint CLI, such as: For further instructions please see the documentation. Apache 2.0 <!-- NOTE: This section is autogenerated. Do not manually edit.--> <!--sponsorsstart--> The following companies, organizations, and individuals support ESLint's ongoing maintenance and development. Be

Keywords
eslintmcp
Alternatives
Comparing tool surfaces…

Tools exposed

1 tool · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.