Model Context Protocol low risk

Package Version

This MCP server checks the latest stable versions of packages from various registries, including npm, PyPI, Maven, Go, Swift, Docker, Bedrock, and GitHub Actions.

Connections & Capabilities

Connects To

GitHubDockerAWS

Capabilities

read

Quickstart

Config

{
  "mcpServers": {
    "package-version": {
      "command": "/Users/sammcj/go/bin/mcp-package-version"
    }
  }
}

Exposed MCP Tools (11)

safe

check_npm_versions

Checks the latest versions of NPM packages against specified constraints.

Read-only operation; retrieves package versions.

safe

check_python_versions

Checks the latest versions of Python packages from a requirements.txt file.

Read-only operation; retrieves package versions.

safe

check_pyproject_versions

Checks the latest versions of Python packages from a pyproject.toml file.

Read-only operation; retrieves package versions.

safe

check_maven_versions

Checks the latest versions of Java packages from Maven.

Read-only operation; retrieves package versions.

safe

check_gradle_versions

Checks the latest versions of Java packages from Gradle.

Read-only operation; retrieves package versions.

safe

check_go_versions

Checks the latest versions of Go packages from go.mod.

Read-only operation; retrieves package versions.

safe

check_docker_tags

Checks available tags for Docker images.

Read-only operation; retrieves Docker image tags.

safe

check_bedrock_models

Lists or searches for AWS Bedrock models.

Read-only operation; retrieves model information.

safe

get_latest_bedrock_model

Gets the latest Claude Sonnet model from AWS Bedrock.

Read-only operation; retrieves model information.

safe

check_swift_versions

Checks the latest versions of Swift packages.

Read-only operation; retrieves package versions.

safe

check_github_actions

Checks the latest versions of GitHub Actions.

Read-only operation; retrieves action versions.

Safety Assessment

This MCP server is generally safe for use as it primarily performs read-only operations to retrieve package version information. However, it's crucial to ensure proper validation of responses from external package registries to mitigate potential vulnerabilities. Running the server in a sandboxed environment can further reduce risk.

Primarily read-only operations
No direct access to sensitive data or credentials
Focus on retrieving package version information
Limited execution capabilities

Potential for information disclosure if package data is mishandled
Reliance on external package registries introduces dependency risks
Improperly validated responses from registries could lead to vulnerabilities
Network access required to external registries