check_maven_version_exists
Check if a specific version of a Maven dependency exists
Answer the three questions a dependency bump raises: what the latest release is, whether a specific version exists, and what was deployed and in what order.
LABSCO SUMMARY
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.
A three-tool Maven dependency lookup covering the latest release, a version existence check, and the version list in deploy order.
Nothing — no account, no key.
One command — npx mcp-maven-deps
USE CASES
Ask for the current release of the coordinate, then read the version list in deploy order to see how far the jump is and whether a patch was published after the minor you are sitting on.
Check that the exact version string exists before pinning to it, and put it next to the current release so you know whether the pin moves you forward or back.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
check_maven_version_existsCheck if a specific version of a Maven dependency exists
get_latest_releaseGet the latest release version of a Maven dependency (excludes pre-releases by default)
list_maven_versionsList Maven dependency versions in deploy order (most recent first)
BEFORE YOU INSTALL
3 tools when we connected.
npx on PATH
CONTEXT COST
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Add the block to your client, or run the command directly.
{
"mcpServers": {
"mcp-maven-deps": {
"command": "npx",
"args": [
"mcp-maven-deps"
]
}
}
}npx mcp-maven-deps