Summary
The three questions a dependency bump actually raises.
Excluding pre-releases by default on both the latest-release and the list tools is the right default, and it removes the usual confusion where a release candidate looks like the newest version. check_maven_version_exists is the one that heads off a whole class of build failure: the version somebody pasted into a pom either exists or it does not, and finding out costs one call rather than one failed build and a stack trace.
What it is
A three-tool Maven dependency lookup covering the latest release, a version existence check, and the version list in deploy order.
What you get
- get_latest_release for a dependency, excluding pre-releases by default
- check_maven_version_exists, answering whether a named version of a dependency is actually published
- list_maven_versions in deploy order with the most recent first, with a depth limit and the same pre-release exclusion
Requirements
Nothing — no account, no key.
Setup effort
One command — npx mcp-maven-deps