npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@krozov/maven-central-mcp

v0.5.1

Published

MCP server for Maven Central dependency intelligence

Downloads

668

Readme

maven-mcp

Claude Code plugin that provides Maven dependency intelligence via an MCP server — query artifact versions, scan projects for outdated dependencies, check for vulnerabilities, and fetch changelogs.

How it works

An MCP server registers tools that Claude can call during a conversation. The server queries Maven Central, Google Maven, Gradle Plugin Portal, and any custom repositories discovered from your project's build files.

Tools

| Tool | Description | |------|-------------| | get_latest_version | Find latest version of an artifact with stability-aware selection | | check_version_exists | Verify if a specific version exists and classify its stability | | check_multiple_dependencies | Bulk lookup of latest versions for multiple dependencies | | compare_dependency_versions | Compare current versions against latest (major/minor/patch) | | get_dependency_changes | Show changes between versions from GitHub changelogs | | scan_project_dependencies | Scan Gradle/Maven build files and Gradle version catalogs (gradle/libs.versions.toml) for dependencies | | get_dependency_vulnerabilities | Check for known CVEs via OSV.dev | | search_artifacts | Search Maven Central | | audit_project_dependencies | Full audit: scan + version compare + vulnerability check |

Skills

| Skill | Description | |-------|-------------| | /latest-version <groupId:artifactId> | Find latest version of a Maven artifact | | /check-deps | Scan project for outdated dependencies and update them |

Supported build systems

  • Gradlebuild.gradle, build.gradle.kts, settings.gradle, settings.gradle.kts
  • Mavenpom.xml
  • Version catalogsgradle/libs.versions.toml

Custom repositories are auto-discovered from Gradle settings.gradle(.kts)/build.gradle(.kts) and Maven pom.xml, and the server queries these alongside Maven Central. Dependency scanning additionally reads gradle/libs.versions.toml for declared dependencies, but version catalogs are not used for repository discovery.

Prerequisites

  • Node.js 18+ (required)
  • jq (required when hooks are enabled) — used by the PostToolUse hook script (plugin/hooks/post-edit-deps.sh) to parse JSON input
  • GITHUB_TOKEN (optional) — set this environment variable to raise GitHub API rate limits from 60 to 5000 requests/hour, used by the get_dependency_changes tool to fetch changelogs and release notes

Installation

claude plugin add /path/to/maven-mcp/plugin

Or use the published npm package directly as an MCP server:

npx @krozov/maven-central-mcp

Hooks

The plugin includes a PostToolUse hook that triggers when build files (build.gradle, pom.xml, libs.versions.toml, etc.) are edited. It reminds you to run /check-deps to verify dependency updates.

Caching

Persistent cache stored at ~/.cache/maven-central-mcp/:

  • SCM mappings (artifact → GitHub repo) — cached permanently
  • Releases and changelogs — cached with 24-hour TTL