{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm-eslint-mcp","slug":"eslint-mcp","name":"@eslint/mcp","type":"mcp","url":"https://github.com/eslint/rewrite/tree/main/packages/mcp#readme","page_url":"https://unfragile.ai/eslint-mcp","categories":["mcp-servers"],"tags":["eslint","mcp"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm-eslint-mcp__cap_0","uri":"capability://tool.use.integration.mcp.based.eslint.rule.execution.and.linting.orchestration","name":"mcp-based eslint rule execution and linting orchestration","description":"Exposes ESLint's linting engine as an MCP server, allowing remote clients (Claude, other LLM agents, or tools) to invoke ESLint rule checking and code analysis over the MCP protocol. The server wraps ESLint's core linting API and translates rule violations into structured MCP resource/tool responses, enabling stateless, request-response linting without direct filesystem access from the client.","intents":["I want Claude or an AI agent to lint my code without running ESLint locally in my IDE","I need to integrate ESLint checks into an MCP-aware development tool or agent workflow","I want to expose ESLint as a remote service that multiple clients can query for linting results","I need to run ESLint rules as part of an AI-assisted code review or refactoring pipeline"],"best_for":["AI agent developers building code-aware workflows with Claude or other LLM clients","Teams using MCP-compatible tools (Claude Desktop, custom MCP clients) who want centralized linting","Developers building multi-tool development environments where ESLint must be accessible over MCP"],"limitations":["Requires a running MCP server process — adds deployment complexity vs. direct ESLint npm module usage","Network latency between MCP client and server adds overhead compared to in-process linting","Configuration must be accessible to the server process; client cannot dynamically inject ESLint configs","No built-in caching of lint results — each request re-runs the full linting pass","Limited to ESLint's rule set; custom rules must be installed in the server's environment"],"requires":["Node.js 18+ (ESLint 9.x requirement)","ESLint 9.x installed in the MCP server environment","@eslint/mcp npm package","MCP-compatible client (Claude Desktop, custom MCP client library, or agent framework with MCP support)","Valid ESLint configuration file (.eslintrc.js, eslint.config.js, or package.json eslintConfig) in the server's working directory"],"input_types":["code (JavaScript, TypeScript, JSX, TSX as strings or file paths)","ESLint configuration (via .eslintrc or eslint.config.js)","rule options and severity levels"],"output_types":["structured linting results (violations, warnings, errors with line/column positions)","rule metadata (rule name, description, documentation URL)","fix suggestions (when ESLint rules provide auto-fix capabilities)"],"categories":["tool-use-integration","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-eslint-mcp__cap_1","uri":"capability://memory.knowledge.eslint.rule.metadata.and.documentation.retrieval","name":"eslint rule metadata and documentation retrieval","description":"Exposes ESLint rule definitions, descriptions, and documentation links as MCP resources or tools, allowing clients to query rule metadata without parsing ESLint's internal rule registry. The server introspects the loaded ESLint ruleset and surfaces rule names, descriptions, categories, and documentation URLs for use in AI-assisted code review or rule recommendation workflows.","intents":["I want to show Claude the available ESLint rules and their purposes before asking it to fix violations","I need to look up what a specific ESLint rule does and why it was triggered","I want an AI agent to understand the intent behind ESLint rules to provide better explanations to developers"],"best_for":["AI agents providing code review explanations or rule-based refactoring guidance","Interactive tools that need to display ESLint rule documentation to users","Developers building custom linting workflows that require rule context"],"limitations":["Metadata is static per server startup — changes to ESLint rules require server restart","Only exposes rules loaded in the server's ESLint environment; custom rules must be installed server-side","No filtering or search capability — client must handle rule discovery logic"],"requires":["Node.js 18+","ESLint 9.x with rule definitions loaded","@eslint/mcp npm package"],"input_types":["rule name (string)","optional filter criteria (category, severity)"],"output_types":["rule metadata (name, description, category, documentation URL)","rule configuration options (schema, defaults)","fix availability flag"],"categories":["memory-knowledge","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-eslint-mcp__cap_2","uri":"capability://code.generation.editing.automatic.eslint.fix.application.and.suggestion.generation","name":"automatic eslint fix application and suggestion generation","description":"Invokes ESLint's built-in auto-fix mechanism to automatically correct code violations where rules provide fix implementations. The server applies fixes to code strings or files, returns the corrected code, and optionally provides structured fix suggestions (before/after diffs, rule applied, confidence level) for client-side review or approval workflows.","intents":["I want Claude to automatically fix ESLint violations in my code and show me what changed","I need to apply ESLint fixes as part of an AI-assisted code refactoring pipeline","I want to preview what ESLint fixes would do before applying them to my codebase"],"best_for":["AI agents performing automated code cleanup or style normalization","Interactive code editors integrating ESLint fixes into LLM-assisted workflows","CI/CD pipelines using AI agents to auto-fix linting issues before commit"],"limitations":["Only rules with fix implementations can be auto-fixed; many rules only report violations without fixes","Fixes are applied in a single pass — some violations may require multiple passes to fully resolve","No rollback mechanism — if a fix introduces new violations, client must handle recovery","Fix suggestions are deterministic but may not match developer intent; human review is recommended"],"requires":["Node.js 18+","ESLint 9.x with rules that support auto-fix","@eslint/mcp npm package","Code input as string or file path"],"input_types":["code (JavaScript, TypeScript, JSX, TSX as strings)","ESLint configuration specifying which rules to apply"],"output_types":["fixed code (string)","fix summary (rules applied, number of fixes, before/after diffs)","remaining violations (if any rules cannot be auto-fixed)"],"categories":["code-generation-editing","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-eslint-mcp__cap_3","uri":"capability://data.processing.analysis.multi.file.batch.linting.with.aggregated.results","name":"multi-file batch linting with aggregated results","description":"Accepts multiple code files or file paths in a single MCP request and returns aggregated linting results across all files. The server batches ESLint invocations, deduplicates configuration loading, and returns structured results grouped by file, enabling efficient bulk code analysis for large codebases or multi-file refactoring workflows.","intents":["I want to lint an entire directory or project and get a summary of all violations","I need to check multiple files for linting issues as part of an AI-assisted code review","I want to identify which files have the most linting violations to prioritize fixes"],"best_for":["AI agents analyzing or refactoring multiple files in a single workflow","Batch code quality assessment tools or dashboards","CI/CD pipelines checking multiple files for linting compliance"],"limitations":["Batch size is limited by MCP message size and server memory — very large batches may timeout or fail","Results are not cached — re-linting the same files requires re-running the full analysis","No incremental linting — all files are re-linted even if only one changed","Aggregation is simple (grouped by file) — no cross-file analysis or dependency tracking"],"requires":["Node.js 18+","ESLint 9.x","@eslint/mcp npm package","File paths or code strings for multiple files"],"input_types":["array of code files (strings or file paths)","ESLint configuration"],"output_types":["aggregated linting results (violations grouped by file)","summary statistics (total violations, files with errors, etc.)","per-file violation counts and severity breakdown"],"categories":["data-processing-analysis","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-eslint-mcp__cap_4","uri":"capability://memory.knowledge.eslint.configuration.discovery.and.validation","name":"eslint configuration discovery and validation","description":"Automatically discovers and loads ESLint configuration files (.eslintrc.js, eslint.config.js, or package.json eslintConfig) from the server's working directory and validates the configuration for syntax errors or invalid rule options. The server exposes the loaded configuration as MCP resources, allowing clients to query which rules are enabled, their severity levels, and any configuration errors.","intents":["I want to know which ESLint rules are active in my project before linting","I need to verify that my ESLint configuration is valid and won't cause linting failures","I want to understand the rule severity levels (error vs. warning) in my project"],"best_for":["Developers debugging ESLint configuration issues","AI agents that need to understand the active rule set before providing recommendations","Tools that display ESLint configuration to users for validation or modification"],"limitations":["Configuration is loaded at server startup — changes to config files require server restart","Only discovers config files in the server's working directory; cannot load configs from arbitrary paths","Validation is limited to ESLint's built-in checks; custom config validators are not supported","No config merging or inheritance visualization — only shows the final resolved config"],"requires":["Node.js 18+","ESLint 9.x","@eslint/mcp npm package","Valid ESLint configuration file in the server's working directory"],"input_types":["optional: specific config file path or config object"],"output_types":["loaded configuration (rules, severity levels, plugins, parser options)","configuration validation results (errors, warnings)","active rule list with severity levels"],"categories":["memory-knowledge","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-eslint-mcp__cap_5","uri":"capability://code.generation.editing.language.specific.linting.with.parser.and.plugin.support","name":"language-specific linting with parser and plugin support","description":"Supports linting of multiple languages (JavaScript, TypeScript, JSX, TSX) by leveraging ESLint's parser and plugin system. The server loads configured parsers (e.g., @typescript-eslint/parser) and plugins (e.g., @typescript-eslint/eslint-plugin) from the server environment, enabling language-specific rule checking and type-aware linting for TypeScript code.","intents":["I want to lint TypeScript code with type-aware ESLint rules","I need to check JSX/TSX syntax and React-specific linting rules","I want to use custom parsers or language-specific ESLint plugins in my linting workflow"],"best_for":["TypeScript projects using type-aware ESLint rules (@typescript-eslint)","React/JSX projects with React-specific linting rules","Polyglot projects with multiple language linting requirements"],"limitations":["Parsers and plugins must be installed in the server's environment — clients cannot dynamically inject them","Type-aware linting requires TypeScript project setup (tsconfig.json) — adds configuration complexity","Parser performance varies by language; TypeScript parsing is slower than JavaScript","Plugin compatibility depends on ESLint version — version mismatches can cause failures"],"requires":["Node.js 18+","ESLint 9.x","@eslint/mcp npm package","Language-specific parsers installed (e.g., @typescript-eslint/parser for TypeScript)","Language-specific plugins installed (e.g., @typescript-eslint/eslint-plugin)","tsconfig.json for TypeScript projects (if using type-aware rules)"],"input_types":["code (JavaScript, TypeScript, JSX, TSX as strings)","language hint or file extension"],"output_types":["language-specific linting results (violations with language-aware context)","type information (for type-aware rules)","parser errors (if code is syntactically invalid)"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":38,"verified":false,"data_access_risk":"high","permissions":["Node.js 18+ (ESLint 9.x requirement)","ESLint 9.x installed in the MCP server environment","@eslint/mcp npm package","MCP-compatible client (Claude Desktop, custom MCP client library, or agent framework with MCP support)","Valid ESLint configuration file (.eslintrc.js, eslint.config.js, or package.json eslintConfig) in the server's working directory","Node.js 18+","ESLint 9.x with rule definitions loaded","ESLint 9.x with rules that support auto-fix","Code input as string or file path","ESLint 9.x"],"failure_modes":["Requires a running MCP server process — adds deployment complexity vs. direct ESLint npm module usage","Network latency between MCP client and server adds overhead compared to in-process linting","Configuration must be accessible to the server process; client cannot dynamically inject ESLint configs","No built-in caching of lint results — each request re-runs the full linting pass","Limited to ESLint's rule set; custom rules must be installed in the server's environment","Metadata is static per server startup — changes to ESLint rules require server restart","Only exposes rules loaded in the server's ESLint environment; custom rules must be installed server-side","No filtering or search capability — client must handle rule discovery logic","Only rules with fix implementations can be auto-fixed; many rules only report violations without fixes","Fixes are applied in a single pass — some violations may require multiple passes to fully resolve","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.5463660840576325,"quality":0.22,"ecosystem":0.46,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.902Z","last_scraped_at":"2026-05-03T14:04:47.472Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":26965,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=eslint-mcp","compare_url":"https://unfragile.ai/compare?artifact=eslint-mcp"}},"signature":"q42kHdTllgIKvmqsQyEyFiWmz6H8KvGftJElxVXTojCaWShIsdqyKzpnR+bNP48EJStATE8EntKkkTcNIZp0BQ==","signedAt":"2026-06-22T09:42:04.147Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/eslint-mcp","artifact":"https://unfragile.ai/eslint-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=eslint-mcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}