Usgs Mineral Commodities
NPM · @PIPEWORX/MCP-USGS-MINERAL-COMMODITIES · 2 COMPONENTS
USGS Mineral Commodity Summaries (MCS) — U.S. production, imports, exports, consumption, price…
Available components
Last scanned (7 hours ago)
Scores higher than 62% of npm servers
Category Health and Science
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-usgs-mineral-commodities). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
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.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
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 →
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.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-usgs-mineral-commodities@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-usgs-mineral-commodities |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-usgs-mineral-commodities/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560891024 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f45c3953348eb6e668f07dc28df9644ea8551d42505dc9697cdf478451432a8b489d97296e096b4ff94f4c1cf08d8a17e192a5301b40979b857828c43 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
mcs_commodity_data ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| commodity | string | yes | Commodity name or code, e.g. "lithium", "cobalt", "rare earths", "gold". |
No output schema declared.
No examples provided.
mcs_country_comparison ~216
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.
| Name | Type | Req | Description |
|---|---|---|---|
| commodity | string | yes | 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. |
No output schema declared.
No examples provided.
mcs_list_commodities ~175
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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". |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-usgs-mineral-commodities
claude mcp add pipeworx-io-usgs-mineral-commodities -- npx -y @pipeworx/mcp-usgs-mineral-commodities
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.