Jdk25 Upgrade Blocker Lint

io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.4Updated Oct 24, 2026

Finds the Java lines the new LTS removed — 18 rules; 23 findings in one 64-line fixture

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local stdio MCP server that lints Java code for lines removed in the new LTS release, reporting findings against 18 rules.

What you can do
  • Scan Java source for constructs removed in the new LTS release.
  • Report findings grouped by rule, with counts such as 23 findings in a 64-line fixture.
  • Surface upgrade blockers so they can be fixed before migrating.
When to use it
Useful when planning a Java upgrade to the new LTS and you want an assistant to flag code that will break, or to review a codebase for removed APIs before migrating.
Requirements
Runs as a local process over stdio, launched with npx from the npm package @readystack/jdk25-upgrade-blocker-lint. Requires Node.js and npx on the machine; desktop client only. No authentication, environment variables or headers are declared.
Before you install
The README content does not match the tool's stated purpose and only mentions VS Code themes and a website, so the package's actual behavior is hard to verify from the supplied material. Review the package before running it locally.

Installation

In SourceWeft

  1. Open Jdk25 Upgrade Blocker Lint in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

readystack-themes

Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack

Source: README.md at commit ee1c884

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

3
  1. v1.0.4LatestSep 23, 2026
  2. v1.0.2Sep 19, 2026
  3. v1.0.1Sep 18, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.