Usgs Mrdata
NPM · @PIPEWORX/MCP-USGS-MRDATA · 2 COMPONENTS
USGS MRData MCP — the Mineral Resources Data System (MRDS)
Available components
Last scanned (8 hours ago)
Scores higher than 61% 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-mrdata). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 564 tokens (~188/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.
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.
- 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-mrdata@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-mrdata |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-usgs-mrdata/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560895156 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:31931001384533fbc5551e1251306232a6550b09c8dc06ce52835be47c68260739d5030add0fc15018df5d9c9ffe9caafa0d410f798885ce7fb7f8718 |
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 →
mrdata_commodities ~128
Which commodities are recorded in USGS MRDS inside an area, with a site count per commodity — the "what is this region mined for" tool. Also serves as the lookup for the commodity symbols that mrdata_search_deposits expects. Sourced from USGS MRData.
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | string | – | Bounding box "minLon,minLat,maxLon,maxLat" (WGS84). Omit to get the symbol reference list with no counts. |
| sample_size | number | – | How many sites in the box to tally (default 500, max 2000) |
No output schema declared.
No examples provided.
mrdata_deposit ~143
Full USGS MRDS record for one mineral deposit by its deposit id — commodities with their roles, deposit type and model, development status, operation type, mining method, years of first and last production, discovery method, alternate site names, host rocks, ore and gangue minerals, and the bibliography behind the record. Sourced from USGS MRData.
| Name | Type | Req | Description |
|---|---|---|---|
| dep_id | string | yes | MRDS deposit id, e.g. "10186774". Get one from mrdata_search_deposits. |
| sections | string | – | Comma-separated sections to keep, e.g. "deposits,commodity,name". Omit for the whole record. |
No output schema declared.
No examples provided.
mrdata_search_deposits ~235
Search the USGS Mineral Resources Data System for mines, prospects and mineral occurrences by bounding box, site name or commodity. AUTHORITATIVE for "what has been mined near here" and "where are the US lithium/copper/gold occurrences" — returns each site's deposit id, name, development status (Producer, Past Producer, Prospect, Occurrence), coordinates and commodity codes. Sourced from USGS MRData.
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | string | – | Bounding box "minLon,minLat,maxLon,maxLat" (WGS84), e.g. "-112.2,33.4,-112.0,33.6" |
| commodity | string | – | Commodity symbol as MRDS codes it, e.g. "AU" (gold), "CU" (copper), "LI" (lithium), "REE". List them with mrdata_commodities. |
| limit | number | – | Max sites to return (default 25, max 200) |
| name_contains | string | – | Site-name substring, case-sensitive as stored, e.g. "Bingham", "Rico" |
No output schema declared.
No examples provided.
How do I install the Usgs Mrdata MCP server?
Usgs Mrdata runs locally as an npm package, launched with npx -y @pipeworx/mcp-usgs-mrdata. 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-mrdata
claude mcp add pipeworx-io-usgs-mrdata -- npx -y @pipeworx/mcp-usgs-mrdata
What is the Usgs Mrdata MCP server?
Usgs Mrdata is an MCP server listed in the public MCP registry as io.github.pipeworx-io/usgs-mrdata. USGS MRData MCP, the Mineral Resources Data System (MRDS). This page covers its npm package (@pipeworx/mcp-usgs-mrdata).
Is the Usgs Mrdata MCP server safe to use?
Usgs Mrdata 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 Mrdata MCP server expose?
Usgs Mrdata exposes 3 tools: mrdata_search_deposits, mrdata_deposit, mrdata_commodities. Their descriptions and schemas cost roughly 506 tokens of context every time the server is loaded.
Is the Usgs Mrdata MCP server still maintained?
Usgs Mrdata 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 Mrdata MCP server under?
Usgs Mrdata declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.