# Sonatype Nexus (oci · ghcr.io/oomchiller/nexus-mcp-server) Read-only-first Sonatype Nexus Repository 3 inspection, audit and documentation. - Trust score: 45/100 (low) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-06 ## Components - oci · `ghcr.io/oomchiller/nexus-mcp-server`: 45/100 (this document), [markdown](https://verifymcp.io/servers/oomchiller-nexus-mcp-server/ghcr-io-oomchiller-nexus-mcp-server.md), [page](https://verifymcp.io/servers/oomchiller-nexus-mcp-server/ghcr-io-oomchiller-nexus-mcp-server) ## Channel facts - Registry: `oci` - Package: `ghcr.io/oomchiller/nexus-mcp-server` - Version: `0.2.1` - Transport: `stdio` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-06. - **Supply Chain Security**: 0/100 - 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 could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - Install-script risk not yet assessed. - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - **Provenance & Transparency**: 48/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - Clear OSI-approved license (MIT). - Actively maintained (last published 2 days ago). - Publishes a security disclosure policy (SECURITY.md). - **Schema Quality & AI Usability**: 88/100 - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (excellent). - Tool/resource definitions use about 2074 tokens (~103/item across 20 items; 12 tools + 8 resources), lean. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 10/100 - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. **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. ## 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. ### Claude ```bash 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. ### Cursor ```json { "mcpServers": { "oomchiller-nexus-mcp-server": { "command": "docker", "args": [ "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. ### VS Code ```json { "servers": { "oomchiller-nexus-mcp-server": { "command": "docker", "args": [ "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. ### Codex ```bash codex 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. ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "oomchiller-nexus-mcp-server": { "type": "local", "command": [ "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" ], "enabled": true } } } ``` 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. ### Hermes ```yaml mcp_servers: oomchiller-nexus-mcp-server: command: "docker" args: ["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. ### Netclaw ```json { "McpServers": { "oomchiller-nexus-mcp-server": { "Transport": "stdio", "Command": "docker", "Arguments": [ "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. ### Other ```json { "mcpServers": { "oomchiller-nexus-mcp-server": { "command": "docker", "args": [ "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. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-06 (score 45, +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. ### 2026-11-04 (score 44, +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. ### 2026-11-03 (score 43) First indexed and scored. ## MCP tools (12) ### `nexus_understand_architecture` (~114 tokens) 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. ### `nexus_explain_repository` (~145 tokens) 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. Input parameters: - `name` (string, required): Exact repository name as shown by nexus_understand_architecture or the nexus://repositories resource, for example 'maven-central'. ### `nexus_explain_storage_strategy` (~95 tokens) 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. ### `nexus_audit_repository_content` (~186 tokens) 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. Input parameters: - `max_components` (integer): Most components to return (1-5000). - `max_pages` (integer): Most component pages to read from Nexus (1-100). - `repository` (string, required): Exact repository name as shown by nexus_understand_architecture or the nexus://repositories resource, for example 'maven-central'. ### `nexus_generate_inventory_json` (~104 tokens) 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. Output parameters: - `result` (string) ### `nexus_generate_architecture_md` (~99 tokens) 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. Output parameters: - `result` (string) ### `nexus_generate_repository_catalog_md` (~91 tokens) 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. Output parameters: - `result` (string) ### `nexus_detect_architecture_smells` (~120 tokens) 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. Output parameters: - `result` (array) ### `nexus_generate_audit_report` (~95 tokens) 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. ### `nexus_compare_live_state_with_declared_state` (~161 tokens) 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. Input parameters: - `declared_state` (object, required): Declared configuration as {"repositories": {"": {"format": "maven2", "type": "proxy"}}}. Other keys are ignored. ### `nexus_openapi_list_operations` (~76 tokens) 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. Output parameters: - `result` (array) ### `nexus_generate_capability_map` (~82 tokens) 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. ## Diagnostics Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/oomchiller-nexus-mcp-server/ghcr-io-oomchiller-nexus-mcp-server#diagnostics ## Score history - 2026-11-06: 45 - 2026-11-05: 44 - 2026-11-04: 44 - 2026-11-03: 43 ## 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. ## Links - GitHub Container Registry: https://ghcr.io/oomchiller/nexus-mcp-server - Repository: https://github.com/oomchiller/nexus-mcp-server - Changelog RSS feed: https://verifymcp.io/servers/oomchiller-nexus-mcp-server/ghcr-io-oomchiller-nexus-mcp-server.xml - Changelog JSON feed: https://verifymcp.io/servers/oomchiller-nexus-mcp-server/ghcr-io-oomchiller-nexus-mcp-server/changelog.json - Trust report (JSON): https://verifymcp.io/servers/oomchiller-nexus-mcp-server/ghcr-io-oomchiller-nexus-mcp-server.json - HTML version of this page: https://verifymcp.io/servers/oomchiller-nexus-mcp-server/ghcr-io-oomchiller-nexus-mcp-server