Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Sonatype Nexus

OCI · GHCR.IO/OOMCHILLER/NEXUS-MCP-SERVER

Read-only-first Sonatype Nexus Repository 3 inspection, audit and documentation.

45 Trust /100

Last scanned (8 hours ago)

Scores higher than 64% of OCI servers

Category Cloud Infrastructure

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability88
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 2074 tokens (~103/item across 20 items; 12 tools + 8 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (12)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (4)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  • Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 43

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 6 Nov 2026 · Analysed oci/ghcr.io/oomchiller/nexus-mcp-server@0.2.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 12 exposed · ~1,368 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
nexus_audit_repository_content ~186

List the components and assets stored in one repository, with size, last modified and last downloaded dates, by paging through the Nexus component API on the server. The result states whether the inventory is complete; when a page or component limit is reached it is marked incomplete and must not be used to decide that content is unused. Use it for cleanup or retirement questions about one repository; use nexus_explain_repository for its configuration. Slow on large repositories: one request per page. Errors if Nexus is not configured, rejects the credentials or is unreachable.

NameTypeReqDescription
max_componentsinteger–Most components to return (1-5000).
max_pagesinteger–Most component pages to read from Nexus (1-100).
repositorystringyesExact repository name as shown by nexus_understand_architecture or the nexus://repositories resource, for example 'maven-central'.

Structured output declared, but exposes no named fields.

No examples provided.

nexus_compare_live_state_with_declared_state ~161

Compare live repositories with a declared state, for example one exported from Terraform or Puppet data by the user. Returns repositories missing in Nexus, repositories present only in Nexus, and repositories whose format or type differ. Only name, format and type are compared. Ask the user for the declared state before calling; to produce one from the live instance use nexus_generate_inventory_json. Covers what the configured account can see; endpoints missing for version, edition or permission reasons appear under limitations. Errors if Nexus is not configured, rejects the credentials or is unreachable.

NameTypeReqDescription
declared_stateobjectyesDeclared configuration as {"repositories": {"<name>": {"format": "maven2", "type": "proxy"}}}. Other keys are ignored.

Structured output declared, but exposes no named fields.

No examples provided.

nexus_detect_architecture_smells ~120

Run rule-based checks and return findings with severity, confidence, affected objects, evidence and a suggested action. Four rules: blob stores no repository uses, group repositories without members, offline repositories and cleanup policies applied to no repository. Returns an empty list when nothing is found. It is not a security audit; for a full Markdown report use nexus_generate_audit_report. Covers what the configured account can see; endpoints missing for version, edition or permission reasons appear under limitations. Errors if Nexus is not configured, rejects the credentials or is unreachable.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

nexus_explain_repository ~145

Explain one repository: format, type, the blob store it writes to, the cleanup policies applied to it and the group repositories it belongs to. Returns an object with an 'error' field if no repository has that name; list names with nexus_understand_architecture first. For the components stored in the repository use nexus_audit_repository_content. Covers what the configured account can see; endpoints missing for version, edition or permission reasons appear under limitations. Errors if Nexus is not configured, rejects the credentials or is unreachable.

NameTypeReqDescription
namestringyesExact repository name as shown by nexus_understand_architecture or the nexus://repositories resource, for example 'maven-central'.

Structured output declared, but exposes no named fields.

No examples provided.

nexus_explain_storage_strategy ~95

List every blob store with its type and the repositories that write to it, with relationship evidence. Use it to answer which repositories share storage or which blob store is unused; it does not report disk usage, which the REST API does not expose. Covers what the configured account can see; endpoints missing for version, edition or permission reasons appear under limitations. Errors if Nexus is not configured, rejects the credentials or is unreachable.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

nexus_generate_architecture_md ~99

Generate a short Markdown architecture document for the instance: Nexus version, repository and blob store counts, and how many repositories each blob store serves. Use it when the user wants a document to save or share; for questions answered in conversation use nexus_understand_architecture. Covers what the configured account can see; endpoints missing for version, edition or permission reasons appear under limitations. Errors if Nexus is not configured, rejects the credentials or is unreachable.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

nexus_generate_audit_report ~95

Generate a configuration audit report: a Markdown document plus structured summary counts, the findings of nexus_detect_architecture_smells, blob store usage and limitations. Use it when the user asks for an audit or a report to keep; use nexus_detect_architecture_smells for findings only. It covers REST-visible configuration, not vulnerabilities or a full security assessment. Errors if Nexus is not configured, rejects the credentials or is unreachable.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

nexus_generate_capability_map ~82

Group the instance's REST operations by domain: repositories, blob stores, components and assets, tasks, security, system, lifecycle and other. Use it for an overview of what the API of this Nexus can do; use nexus_openapi_list_operations for the flat list with operation IDs. Errors if Nexus is not configured, rejects the credentials or is unreachable.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

nexus_generate_inventory_json ~104

Export repositories, blob stores, cleanup policies and routing rules as one JSON document, plus collector metadata and limitations. Use it to save a baseline, feed another tool, or build a declared state for nexus_compare_live_state_with_declared_state; for a readable summary use nexus_understand_architecture. Covers what the configured account can see; endpoints missing for version, edition or permission reasons appear under limitations. Errors if Nexus is not configured, rejects the credentials or is unreachable.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

nexus_generate_repository_catalog_md ~91

Generate a Markdown catalog with one section per repository: type, format, online status, blob store and the groups it belongs to. Use it for a per-repository reference document; nexus_generate_architecture_md gives the overview. Covers what the configured account can see; endpoints missing for version, edition or permission reasons appear under limitations. Errors if Nexus is not configured, rejects the credentials or is unreachable.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

nexus_openapi_list_operations ~76

List every REST operation the instance publishes in its OpenAPI document, with path, method, operation ID, summary and tags. Use it to check whether this Nexus version or edition offers an endpoint; nexus_generate_capability_map groups the same operations by domain. Errors if Nexus is not configured, rejects the credentials or is unreachable.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

nexus_understand_architecture ~114

Start here: overview of the whole Nexus instance. Returns object counts, repositories grouped by format and type (hosted, proxy, group), how many repositories each blob store serves, members of every group repository and offline repositories, each with evidence. Use nexus_explain_repository for one repository and nexus_explain_storage_strategy for blob store detail. Covers what the configured account can see; endpoints missing for version, edition or permission reasons appear under limitations. Errors if Nexus is not configured, rejects the credentials or is unreachable.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Sonatype Nexus MCP server?

Sonatype Nexus runs locally as a container image, launched with docker run --rm -i -e NEXUS_URL -e NEXUS_USERNAME -e NEXUS_PASSWORD -e NEXUS_VERIFY_TLS -e NEXUS_MCP_MODE -e NEXUS_MCP_ENABLE_WRITE_TOOLS -e NEXUS_MCP_ENABLE_RAW_API ghcr.io/oomchiller/nexus-mcp-server:0.2.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/oomchiller/nexus-mcp-server

# add to Claude Code
claude mcp add oomchiller-nexus-mcp-server -- docker run --rm -i -e NEXUS_URL -e NEXUS_USERNAME -e NEXUS_PASSWORD -e NEXUS_VERIFY_TLS -e NEXUS_MCP_MODE -e NEXUS_MCP_ENABLE_WRITE_TOOLS -e NEXUS_MCP_ENABLE_RAW_API ghcr.io/oomchiller/nexus-mcp-server:0.2.1

This image reads NEXUS_URL, NEXUS_USERNAME, NEXUS_PASSWORD, NEXUS_VERIFY_TLS, NEXUS_MCP_MODE, NEXUS_MCP_ENABLE_WRITE_TOOLS and NEXUS_MCP_ENABLE_RAW_API. Set them in your client's env block for this server; docker run -e passes each one through to the container.

Common questions

What is the Sonatype Nexus MCP server?

Sonatype Nexus is an MCP server listed in the public MCP registry as io.github.oomchiller/nexus-mcp-server. Read-only-first Sonatype Nexus Repository 3 inspection, audit and documentation. This page covers its container image (ghcr.io/oomchiller/nexus-mcp-server).

Is the Sonatype Nexus MCP server safe to use?

Sonatype Nexus scores 45 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Sonatype Nexus MCP server expose?

Sonatype Nexus exposes 12 tools: nexus_understand_architecture, nexus_explain_repository, nexus_explain_storage_strategy, nexus_audit_repository_content, nexus_generate_inventory_json, and 7 more. Their descriptions and schemas cost roughly 1,368 tokens of context every time the server is loaded.

Is the Sonatype Nexus MCP server still maintained?

Sonatype Nexus is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Sonatype Nexus MCP server under?

Sonatype Nexus declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Sonatype Nexus MCP server?

VerifyMCP ran 12 checks on Sonatype Nexus, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about Sonatype Nexus: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.