check_clojars_version_exists
Check if a specific version of a Clojars dependency exists
Settle a dependency question without opening a browser tab: the newest published version of a Clojars artifact, whether a specific version exists, and the release history behind it.
LABSCO SUMMARY
Every tool takes dependency as its unit of address, so the same coordinate carries straight through from get_clojars_latest_version to check_clojars_version_exists to get_clojars_history without re-deriving anything. The scope stops at versions — nothing here reads a project's dependency file, resolves a tree or reports vulnerabilities — which makes it an answer to "what should I pin?" rather than a dependency manager.
A lookup server over Clojars, answering version questions about a dependency given as a Maven artifact.
Nothing — no account, no key.
One command — npx -y clojars-deps-server
USE CASES
Check the version you were about to write down, and take the newest published one if it does not resolve.
Read the release history to see how the versions have moved, then compare it against what you are currently on.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
check_clojars_version_existsCheck if a specific version of a Clojars dependency exists
get_clojars_historyGet version history of a Clojars dependency
get_clojars_latest_versionGet the latest version of a Clojars dependency (Maven artifact)
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": {
"clojars-deps-server": {
"command": "npx",
"args": [
"-y",
"clojars-deps-server"
]
}
}
}npx -y clojars-deps-server