logo
Free, unlimited AI code reviews that run on commit
git-lrc git-lrc GitHub Install Now We'd appreciate a star git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt

mcp-dependency-version-aggregator

A utility service designed to query and report the most current stable releases across a comprehensive suite of software distribution platforms, such as npm, Python Package Index (PyPI), Maven Central repository, Go Modules proxy, and others. This enables autonomous agents to suggest optimized, non-obsolete package references when generating code.

Author

mcp-dependency-version-aggregator logo

sammcj

MIT License

Quick Info

GitHub GitHub Stars 117
NPM Weekly Downloads 0
Tools 1
Last Updated 2026-02-19

Tags

sammcjpackagemavenpackage versionspackage versionmcp package

Centralized Package Version Inspection Engine

smithery badge

This Micro Control Plane (MCP) endpoint furnishes instrumentation for ascertaining the freshest production-ready version identifiers across numerous software artifact repositories:

  • Node Package Manager (npm) for JavaScript/TypeScript environments
  • Python Package Index (PyPI) for Python
  • Maven Central Repository (Java/JVM ecosystem)
  • Go Modules Proxy for Go language projects
  • Swift Package Manager sources
  • AWS Bedrock Service (for examining underlying AI model releases)
  • Docker Hub (for container images)
  • GitHub Container Registry (for container artifacts)
  • GitHub Actions Workflows

This centralized resource aids Large Language Models (LLMs) in maintaining strict currency when formulating software dependencies.

NOTE: This functionality is progressively being subsumed into my larger mcp-devtools server infrastructure.

https://github.com/sammcj/mcp-package-version MCP server

Visual Depiction

Prerequisites & Setup

Runtime Requirements:

Installation via go install (Recommended for MCP Client Configuration):

go install github.com/sammcj/mcp-package-version/v2@HEAD

Subsequently, configure your client to invoke this service. Assuming the binary is placed in $GOPATH/bin (e.g., /Users/sammcj/go/bin), specify the absolute path in your configuration:

{
  "mcpServers": {
    "package-version": {
      "command": "/Users/sammcj/go/bin/mcp-package-version"
    }
  }
}
  • Cline VSCode Extension Location: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
  • Claude Desktop Configuration Path: ~/Library/Application\ Support/Claude/claude_desktop_config.json
  • GoMCP Configuration File: ~/.config/gomcp/config.yaml

Alternate Deployment Mechanisms

Alternatively, clone the repository and compile locally:

git clone https://github.com/sammcj/mcp-package-version.git
cd mcp-package-version
make

You may also initiate the service within a container environment:

docker run -p 18080:18080 ghcr.io/sammcj/mcp-package-version:main

Note: When operating in a containerized context, the client must reference the network endpoint via url instead of specifying the execution command:

{
  "mcpServers": {
    "package-version": {
      "url": "http://localhost:18080"
    }
  }
}

Hint: Go Path Management

If $GOPATH/bin is absent from your shell's PATH, you are obligated to use the full binary locator when configuring your MCP consumer (e.g., /Users/sammcj/go/bin/mcp-package-version).

If you are new to Go tooling, $GOPATH might not be explicitly defined, which is critical for successful execution of go install commands.

Clarification on $GOPATH

The go install utility fetches and compiles Go source archives, depositing the resulting binary artifact into the bin subdirectory within $GOPATH. By default, $GOPATH typically defaults to $HOME/go on Unix-like OSes. If this variable remains unset, Go adopts this standard location.

The path $GOPATH/bin (e.g., /Users/your_username/go/bin) must be injected into your operating system's PATH environment variable to permit direct invocation of installed Go executables by name across your terminal sessions.

To establish $GOPATH to the default if it's undefined and guarantee $GOPATH/bin is in PATH, append this command to your shell startup script (e.g., ~/.zshrc, ~/.bashrc):

bash [ -z "$GOPATH" ] && export GOPATH="$HOME/go"; echo "$PATH" | grep -q ":$GOPATH/bin" || export PATH="$PATH:$GOPATH/bin"

Apply the modification by reopening your terminal or restarting the MCP client application.

Execution Paradigms

The service supports two principal communication protocols: standard input/output (stdio, default) and Server-Sent Events (SSE).

STDIO Transport (Default Mode)

mcp-package-version

SSE Transport

mcp-package-version --transport sse --port 18080 --base-url "http://localhost:18080"

This configuration exposes the service endpoint at http://localhost:18080/sse (Note the required /sse path segment!).

Command-Line Parameters

  • --transport, -t: Communication protocol selected (choose between stdio or sse). Default: stdio
  • --port: Network port allocated for SSE operation. Default: 18080
  • --base-url: Base URI prefix utilized for SSE connectivity. Default: http://localhost

Containerized Deployments

Images are sourced from the GitHub Container Registry:

docker pull ghcr.io/sammcj/mcp-package-version:main

You can also inspect the supplementary docker-compose.yaml file for orchestration examples.

Available Tooling Functions

npm Modules

Querying the newest versions for JavaScript dependencies:

{
  "name": "check_npm_versions",
  "arguments": {
    "dependencies": {
      "react": "^17.0.2",
      "react-dom": "^17.0.2",
      "lodash": "4.17.21"
    },
    "constraints": {
      "react": {
        "majorVersion": 17
      }
    }
  }
}

Python Packages (from requirements.txt)

Determining current stable versions for Python packages listed in a requirements file:

{
  "name": "check_python_versions",
  "arguments": {
    "requirements": [
      "requests==2.28.1",
      "flask>=2.0.0",
      "numpy"
    ]
  }
}

Python Packages (from pyproject.toml)

Checking Python package versions specified within a pyproject.toml manifest:

{
  "name": "check_pyproject_versions",
  "arguments": {
    "dependencies": {
      "dependencies": {
        "requests": "^2.28.1",
        "flask": ">=2.0.0"
      },
      "optional-dependencies": {
        "dev": {
          "pytest": "^7.0.0"
        }
      },
      "dev-dependencies": {
        "black": "^22.6.0"
      }
    }
  }
}

Java Artifacts (Maven Resolution)

Verifying the newest versions for Java components defined in a Maven context:

{
  "name": "check_maven_versions",
  "arguments": {
    "dependencies": [
      {
        "groupId": "org.springframework.boot",
        "artifactId": "spring-boot-starter-web",
        "version": "2.7.0"
      },
      {
        "groupId": "com.google.guava",
        "artifactId": "guava",
        "version": "31.1-jre"
      }
    ]
  }
}

Java Artifacts (Gradle Build Scripts)

Assessing the current versions for Java dependencies declared in Gradle format:

{
  "name": "check_gradle_versions",
  "arguments": {
    "dependencies": [
      {
        "configuration": "implementation",
        "group": "org.springframework.boot",
        "name": "spring-boot-starter-web",
        "version": "2.7.0"
      },
      {
        "configuration": "testImplementation",
        "group": "junit",
        "name": "junit",
        "version": "4.13.2"
      }
    ]
  }
}

Go Modules

Inspecting the uppermost revisions for Go modules listed in a go.mod file:

{
  "name": "check_go_versions",
  "arguments": {
    "dependencies": {
      "module": "github.com/example/mymodule",
      "require": [
        {
          "path": "github.com/gorilla/mux",
          "version": "v1.8.0"
        },
        {
          "path": "github.com/spf13/cobra",
          "version": "v1.5.0"
        }
      ]
    }
  }
}

Container Images (Docker)

Retrieving available image tags for a specified container artifact:

{
  "name": "check_docker_tags",
  "arguments": {
    "image": "nginx",
    "registry": "dockerhub",
    "limit": 5,
    "filterTags": ["^1\."],
    "includeDigest": true
  }
}

AWS Bedrock Models

Execute a query to retrieve all registered AWS Bedrock models:

{
  "name": "check_bedrock_models",
  "arguments": {
    "action": "list"
  }
}

Search for specific models housed within AWS Bedrock:

{
  "name": "check_bedrock_models",
  "arguments": {
    "action": "search",
    "query": "claude",
    "provider": "anthropic"
  }
}

Obtain the most recent release tag for the Claude Sonnet model available via Bedrock:

{
  "name": "get_latest_bedrock_model",
  "arguments": {}
}

Swift Packages

Checking the highest available revisions for Swift language dependencies:

{
  "name": "check_swift_versions",
  "arguments": {
    "dependencies": [
      {
        "url": "https://github.com/apple/swift-argument-parser",
        "version": "1.1.4"
      },
      {
        "url": "https://github.com/vapor/vapor",
        "version": "4.65.1"
      }
    ],
    "constraints": {
      "https://github.com/apple/swift-argument-parser": {
        "majorVersion": 1
      }
    }
  }
}

GitHub Actions Workflows

Investigating the latest published versions for specified GitHub Actions workflows:

{
  "name": "check_github_actions",
  "arguments": {
    "actions": [
      {
        "owner": "actions",
        "repo": "checkout",
        "currentVersion": "v3"
      },
      {
        "owner": "actions",
        "repo": "setup-node",
        "currentVersion": "v3"
      }
    ],
    "includeDetails": true
  }
}

Deployment Lifecycles

This utility employs GitHub Actions extensively for its Continuous Integration and Deployment pipeline. The established workflow automatically executes the following operations:

  1. Runs compilation and validation tests upon every commit to the main branch and for every submitted Pull Request.
  2. Triggers a formal release process when a version tag matching the pattern v* (e.g., v1.0.0) is pushed to the repository.
  3. Builds and pushes resulting container images to the GitHub Container Registry.

Licensing Terms

This software is distributed under the terms of the MIT license.

WIKIPEDIA: XMLHttpRequest (XHR) is an API in the form of a JavaScript object whose methods transmit HTTP requests from a web browser to a web server. The methods allow a browser-based application to send requests to the server after page loading is complete, and receive information back. XMLHttpRequest is a component of Ajax programming. Prior to Ajax, hyperlinks and form submissions were the primary mechanisms for interacting with the server, often replacing the current page with another one.

== History == The concept behind XMLHttpRequest was conceived in 2000 by the developers of Microsoft Outlook. The concept was then implemented within the Internet Explorer 5 browser (1999). However, the original syntax did not use the XMLHttpRequest identifier. Instead, the developers used the identifiers ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). As of Internet Explorer 7 (2006), all browsers support the XMLHttpRequest identifier. The XMLHttpRequest identifier is now the de facto standard in all the major browsers, including Mozilla's Gecko layout engine (2002), Safari 1.2 (2004) and Opera 8.0 (2005).

=== Standards === The World Wide Web Consortium (W3C) published a Working Draft specification for the XMLHttpRequest object on April 5, 2006. On February 25, 2008, the W3C published the Working Draft Level 2 specification. Level 2 added methods to monitor event progress, allow cross-site requests, and handle byte streams. At the end of 2011, the Level 2 specification was absorbed into the original specification. At the end of 2012, the WHATWG took over development and maintains a living document using Web IDL.

== Usage == Generally, sending a request with XMLHttpRequest has several programming steps.

Create an XMLHttpRequest object by calling a constructor: Call the "open" method to specify the request type, identify the relevant resource, and select synchronous or asynchronous operation: For an asynchronous request, set a listener that will be notified when the request's state changes: Initiate the request by calling the "send" method: Respond to state changes in the event listener. If the server sends response data, by default it is captured in the "responseText" property. When the object stops processing the response, it changes to state 4, the "done" state. Aside from these general steps, XMLHttpRequest has many options to control how the request is sent and how the response is processed. Custom header fields can be added to the request to indicate how the server should fulfill it, and data can be uploaded to the server by providing it in the "send" call. The response can be parsed from the JSON format into a readily usable JavaScript object, or processed gradually as it arrives rather than waiting for the entire text. The request can be aborted prematurely or set to fail if not completed in a specified amount of time.

== Cross-domain requests ==

In the early development of the World Wide Web, it was found possible to brea

See Also

`