# Usgs Mineral Commodities (npm · @pipeworx/mcp-usgs-mineral-commodities)

USGS Mineral Commodity Summaries (MCS) — U.S. production, imports, exports, consumption, price…

- Trust score: 79/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 71/100, [markdown](https://verifymcp.io/servers/pipeworx-io-usgs-mineral-commodities/usgs-mineral-commodities-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-usgs-mineral-commodities/usgs-mineral-commodities-mcp)
- npm · `@pipeworx/mcp-usgs-mineral-commodities`: 79/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-usgs-mineral-commodities/pipeworx-mcp-usgs-mineral-commodities.md), [page](https://verifymcp.io/servers/pipeworx-io-usgs-mineral-commodities/pipeworx-mcp-usgs-mineral-commodities)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-usgs-mineral-commodities`
- Version: `0.2.0`
- 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-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-usgs-mineral-commodities).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 632 tokens (~210/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Usgs Mineral Commodities MCP server?

Usgs Mineral Commodities runs locally as an npm package, launched with npx -y @pipeworx/mcp-usgs-mineral-commodities. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-usgs-mineral-commodities -- npx -y @pipeworx/mcp-usgs-mineral-commodities
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-usgs-mineral-commodities": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-usgs-mineral-commodities"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-usgs-mineral-commodities": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-usgs-mineral-commodities"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-usgs-mineral-commodities -- npx -y @pipeworx/mcp-usgs-mineral-commodities
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-usgs-mineral-commodities": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-usgs-mineral-commodities"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-usgs-mineral-commodities --command npx --arg -y --arg @pipeworx/mcp-usgs-mineral-commodities
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-usgs-mineral-commodities:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-usgs-mineral-commodities"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-usgs-mineral-commodities": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-usgs-mineral-commodities"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-usgs-mineral-commodities -t stdio -c npx -a -y @pipeworx/mcp-usgs-mineral-commodities
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-usgs-mineral-commodities": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-usgs-mineral-commodities"
      ]
    }
  }
}
```

## 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-10-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (3)

### `mcs_list_commodities` (~175 tokens)

Browse the ~85 nonfuel mineral commodities covered by the USGS Mineral Commodity Summaries (MCS) annual data release — lithium, copper, cobalt, rare earths, gold, aluminum, nickel, platinum-group metals, and dozens more, through industrial minerals like barite and feldspar. Each entry names its U.S. statistics columns (production, imports, exports, price, employment, net import reliance — varies by commodity) and whether a world production/reserves-by-country table is also available (mcs_country_comparison). Optional substring query over commodity name or code. Keyless.

Input parameters:

- `limit` (number): Max commodities to return, default 100, max 200.
- `query` (string): Optional substring filter over commodity name or code, e.g. "earth" or "iron".

### `mcs_commodity_data` (~179 tokens)

U.S. salient statistics for one mineral commodity from the USGS Mineral Commodity Summaries — the most recent 5 years of production, imports, exports, consumption, price, employment, and NET IMPORT RELIANCE (the "import reliance" figure — what share of U.S. consumption comes from imports). Accepts a common name ("lithium", "copper", "rare earths", "platinum group metals") or the MCS code. Raw USGS footnote codes (W=withheld, E=estimated, NA=not available, ">50" on import reliance) are preserved verbatim, never silently coerced to a number. Keyless.

Input parameters:

- `commodity` (string, required): Commodity name or code, e.g. "lithium", "cobalt", "rare earths", "gold".

### `mcs_country_comparison` (~216 tokens)

World mine/plant PRODUCTION (prior-year actual + current-year estimate) and RESERVES, by country, for one mineral commodity from the USGS Mineral Commodity Summaries — e.g. "which countries hold lithium reserves" or "China vs. Australia rare-earth production". Covers 75 of the 85 commodities MCS tracks (the other 10 — mostly scrap/slag/crushed-stone categories USGS tracks only domestically — return found:false with a pointer to mcs_commodity_data instead). Optional `countries` filter (comma-separated or array) narrows to named countries; rows are otherwise sorted by current reserves, descending. Keyless.

Input parameters:

- `commodity` (string, required): Commodity name or code, e.g. "lithium", "cobalt", "copper".
- `countries`: Optional country name filter — a comma-separated string or array, e.g. "China,Australia,Chile".
- `limit` (number): Max countries to return, default 50, max 100.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-usgs-mineral-commodities/pipeworx-mcp-usgs-mineral-commodities#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Usgs Mineral Commodities MCP server?

Usgs Mineral Commodities is an MCP server listed in the public MCP registry as io.github.pipeworx-io/usgs-mineral-commodities. USGS Mineral Commodity Summaries (MCS), U.S. production, imports, exports, consumption, price… This page covers its npm package (@pipeworx/mcp-usgs-mineral-commodities).

### Is the Usgs Mineral Commodities MCP server safe to use?

Usgs Mineral Commodities scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Usgs Mineral Commodities MCP server expose?

Usgs Mineral Commodities exposes 3 tools: mcs_list_commodities, mcs_commodity_data, mcs_country_comparison. Their descriptions and schemas cost roughly 570 tokens of context every time the server is loaded.

### Is the Usgs Mineral Commodities MCP server still maintained?

Usgs Mineral Commodities is still listed as active in the MCP registry. We last reached this channel on 5 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 Usgs Mineral Commodities MCP server under?

Usgs Mineral Commodities 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 Usgs Mineral Commodities MCP server?

VerifyMCP ran 15 checks on Usgs Mineral Commodities, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Usgs Mineral Commodities: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-usgs-mineral-commodities
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-usgs-mineral-commodities
- Repository: https://github.com/pipeworx-io/mcp-usgs-mineral-commodities
- Website: https://pipeworx.io/packs/usgs-mineral-commodities
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-usgs-mineral-commodities/pipeworx-mcp-usgs-mineral-commodities.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-usgs-mineral-commodities/pipeworx-mcp-usgs-mineral-commodities/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-usgs-mineral-commodities/pipeworx-mcp-usgs-mineral-commodities.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-usgs-mineral-commodities/pipeworx-mcp-usgs-mineral-commodities