Connect to Sonatype Nexus 3 or JFrog Artifactory and create a named session.

Probes registry system status and version to verify connectivity and credentials. Credentials are automatically cached to ~/.artifact-mcp-cache/credentials.json.

Purpose: Establish an authenticated session before calling any registry tool. When to Use: At the start of an artifact supply chain workflow or to switch between staging/production registries using named sessions. Behavior: Read-Only probe (no artifacts mutated). Side Effects: Caches session credentials locally.

Args: registry_type: 'nexus' (Sonatype Nexus 3) or 'artifactory' (JFrog Artifactory) base_url: Registry base URL (e.g. 'http://localhost:8081' or 'https://myorg.jfrog.io/artifactory') token_or_password: Password, API Token, or Access Token username: Username (e.g. 'admin' or 'ci-agent') session_name: Name for this session, e.g. 'prod', 'staging' (default: 'default')

Check connection health, authenticated user, registry version, and storage quota.

Probes status endpoints (Nexus /service/rest/v1/status, Artifactory /api/system/ping), retrieves server version, and summarizes repository storage metrics.

Purpose: Verify registry availability, user privileges, and storage capacity. When to Use: Before initiating large binary uploads or checking health. Behavior: Read-Only probe. Side Effects: None.

Args: session_name: Artifact registry session to inspect (default: 'default')

Disconnect an active artifact registry session and close HTTP connections.

Purpose: Clean up open network sessions and release memory. When to Use: When switching environments or finishing a pipeline run. Behavior: Closes local HTTP client. Side Effects: Removes session from active memory.

Args: session_name: Session to disconnect (default: 'default')

List all active and cached registry sessions with masked credentials.

Purpose: Review available registry targets, environments, and versions. When to Use: To determine which sessions are configured before executing workflows. Behavior: Read-Only local inspection. Side Effects: None.

Save registry credentials to the local persistent cache file.

Purpose: Cache connection details so future sessions can reconnect automatically. When to Use: When pre-configuring staging/production environments without running queries. Behavior: Local file write to ~/.artifact-mcp-cache/credentials.json. Side Effects: Overwrites existing cached credentials for session_name.

Args: registry_type: 'nexus' or 'artifactory' base_url: Registry base URL token_or_password: Password, API Token, or Access Token username: Username (e.g. 'admin') session_name: Session name to store (default: 'default')

List repositories filtered by package format and repository type.

Works across both Nexus 3 (/service/rest/v1/repositories) and Artifactory (/api/repositories).

Purpose: Inspect repository topology and locate target repos for upload or promotion. When to Use: During supply chain discovery before publishing or pulling artifacts. Behavior: Read-Only query. Side Effects: None.

Args: format_filter: Filter by package format: 'maven2', 'docker', 'npm', 'pypi', 'helm', 'raw' (or 'generic') type_filter: Filter by type: 'hosted' (or 'local'), 'proxy' (or 'remote'), 'group' (or 'virtual') session_name: Session to query (default: 'default')

Search components and artifacts across Nexus or Artifactory.

Returns download URLs, exact versions, creation/modification timestamps, and SHA256/SHA1/MD5 checksums.

Purpose: Locate specific binaries or verify build component presence. When to Use: To locate release artifacts before deployment or check artifact metadata. Behavior: Read-Only search. Side Effects: None.

Args: name: Artifact or component name (supports wildcards/substrings, e.g. 'order-service') group_or_repo: Repository name or Maven groupId (e.g. 'libs-release-local' or 'com.myorg') version: Specific version string (e.g. '1.4.2' or '2.0.0-SNAPSHOT') sha256: Exact 64-character SHA256 checksum to look up session_name: Session to query (default: 'default')

Query Docker/OCI repositories to resolve an immutable sha256:... image digest.

Queries Docker v2 manifest endpoints and AQL in Nexus and Artifactory. Produces an immutable image reference (image@sha256:...) and ready-to-run tool arguments for k8s-mcp rollouts.

Purpose: Bridge container registry images to Kubernetes deployments securely. When to Use: Right before calling k8s-mcp to deploy or update a container workload. Behavior: Read-Only query. Side Effects: None.

Args: repository: Docker repository key/name in the registry (e.g. 'docker-local' or 'docker-hosted') image_name: Container image name (e.g. 'payment-service' or 'microservices/auth') limit: Maximum number of tags to return (default: 20) session_name: Session to query (default: 'default')

Compare the SHA256 digest generated by CI against registry checksum before deployment.

Verifies cryptographic attestation: compares the expected SHA256 (produced by github-mcp GitHub Actions or jenkins-mcp build jobs) against the checksum stored in Nexus or Artifactory. Blocks deployment if tampering or corruption is detected.

Purpose: Supply-chain security attestation gate. When to Use: In CI/CD pipelines right before deployment to Kubernetes/OpenShift. Behavior: Read-Only verification. Side Effects: None.

Args: artifact_path_or_url: Remote artifact path (e.g. 'libs-release-local/com/corp/app-1.0.jar') or full URL expected_sha256: 64-character SHA256 digest from CI build or SBOM session_name: Session to query (default: 'default')

Upload a local build artifact/archive to Nexus or Artifactory with checksum verification.

⚠️ CONFIRMATION-GATED MUTATING TOOL: Requires confirm=true to execute.

Computes local SHA256/SHA1/MD5 checksums, uploads the binary to the destination repository, and immediately verifies the remote checksum match.

Purpose: Publish build archives, JARs, wheels, or tarballs to the registry. When to Use: In Workflow 1 after jenkins-mcp or github-mcp build completes. Behavior: MUTATING. Writes binary to registry storage. Side Effects: Consumes registry storage space.

Args: repository: Destination repository (e.g. 'maven-releases', 'libs-snapshot-local') local_file_path: Absolute or relative path to the local file to upload target_path: Destination path in the repository (e.g. 'com/corp/auth/1.0.0/auth-1.0.0.jar') maven_coords: Optional dict of Maven coordinates {'groupId': '...', 'artifactId': '...', 'version': '...', 'packaging': 'jar'} confirm: Must be True to execute upload (default: False) session_name: Session to use (default: 'default')

Promote an immutable artifact from staging/snapshot to production release repository.

⚠️ CONFIRMATION-GATED MUTATING TOOL: Requires confirm=true to execute.

Promotes a tested, immutable component from staging (e.g. 'dev-local', 'maven-staging') to production release (e.g. 'prod-release', 'maven-releases') without rebuilding, maintaining complete provenance and cryptographic integrity.

Purpose: Supply-chain promotion between pipeline stages. When to Use: In Workflow 2 after integration/smoke tests pass. Behavior: MUTATING. Copies component to target release repository. Side Effects: Modifies target release repository contents.

Args: source_repo: Source repository key (e.g. 'dev-local', 'staging-repo') target_repo: Target release repository key (e.g. 'prod-release', 'maven-releases') artifact_or_build_name: Name of the artifact or build component (e.g. 'cart-service') version: Version string to promote (e.g. '1.5.0') confirm: Must be True to execute promotion (default: False) session_name: Session to use (default: 'default')

Identify and prune stale snapshot artifacts to reclaim storage.

⚠️ CONFIRMATION-GATED MUTATING TOOL: Requires dry_run=false AND confirm=true to delete.

Finds all snapshot versions of a component, sorts by timestamp/version descending, preserves the latest keep_latest_n snapshots, and simulates or deletes stale items.

Purpose: Maintain storage quotas and enforce artifact retention policies. When to Use: In Workflow 4 during scheduled maintenance or when storage alerts trigger. Behavior: Dry-run simulation by default. Destructive deletion when dry_run=false and confirm=true. Side Effects: Permanently deletes pruned snapshot artifacts when executed.

Args: repository: Repository containing snapshot artifacts (e.g. 'maven-snapshots', 'libs-snapshot-local') component_name: Name of the component to clean up (e.g. 'billing-engine') keep_latest_n: Number of most recent snapshots to preserve (default: 5) dry_run: If True, simulates cleanup without deleting files (default: True) confirm: Must be True when dry_run=False to execute permanent deletion (default: False) session_name: Session to use (default: 'default')