Blm Mining Claims
NPM · @PIPEWORX/MCP-BLM-MINING-CLAIMS · 2 COMPONENTS
BLM mining claims (MLRS) — fleet #2826.
Available components
Last scanned (9 hours ago)
Scores higher than 62% of npm servers
Category Maps and Location
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-blm-mining-claims). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 907 tokens (~226/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 64
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-blm-mining-claims@0.2.1
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-blm-mining-claims |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-blm-mining-claims/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3601486716 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:fc24a620c57ad77bd4163540de3258c595e278dca1299be32c01f47ae457d6873e929ba0d6a04e6894b8a6907a353ed9f02d640ae6e1c823ee08d5384 |
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 →
blm_claims_case ~136
One BLM mining claim by case serial number (MLRS, e.g. "NV101474832") or legacy serial (e.g. "NMC1018964"): claim name, type, status, recorded acres, patented flag, the full PLSS legal land description (meridian, township, range, section, aliquot parts), how well BLM could map it, the mapped bounding box, and the MLRS case-record link.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | MLRS case serial number (e.g. NV101474832) or legacy serial (e.g. NMC1018964) |
No output schema declared.
No examples provided.
blm_claims_in_bbox ~242
US federal mining claims (BLM MLRS) inside a latitude/longitude bounding box (up to 2° on a side). Returns the total count in the box and a page of claims: BLM case serial number, claim name, lode/placer/mill-site type, status, acres, mapped center and an MLRS case-record link.
| Name | Type | Req | Description |
|---|---|---|---|
| after_object_id | number | – | Paging cursor: pass next_after_object_id from the previous page (default: first page) |
| claim_type | string | – | Optional claim type filter: lode, placer, mill_site or tunnel_site. |
| limit | number | – | Claims to return, 1–500 (default 50) |
| max_lat | number | yes | North edge latitude |
| max_lon | number | yes | East edge longitude |
| min_lat | number | yes | South edge latitude |
| min_lon | number | yes | West edge longitude |
| status | string | – | Which claims: "open" (default — every claim not closed: Active, Filed, Under Review, On Appeal…), "active" (disposition exactly Active), "closed", or "all". |
No output schema declared.
No examples provided.
blm_claims_near ~309
US federal mining claims (BLM MLRS) within a radius of a latitude/longitude — e.g. claims staked around a lithium, gold or uranium deposit in Nevada, Arizona, Utah, Wyoming. Returns the total count in the radius plus a page of claims (each page sorted by distance): BLM case serial number, claim name, type (lode / placer / mill site / tunnel site), status (Active, Filed, Closed…), recorded acres, distance, and an MLRS case-record link. Geometry is the recorded PLSS land description, not the staked boundary.
| Name | Type | Req | Description |
|---|---|---|---|
| after_object_id | number | – | Paging cursor: pass next_after_object_id from the previous page (default: first page) |
| claim_type | string | – | Optional claim type filter: lode, placer, mill_site or tunnel_site. |
| latitude | number | yes | Latitude (WGS84), e.g. 41.71 |
| limit | number | – | Claims to return, 1–500 (default 50) |
| longitude | number | yes | Longitude (WGS84), e.g. -118.06 |
| radius_km | number | – | Search radius in km, 0.1–50 (default 5) |
| status | string | – | Which claims: "open" (default — every claim not closed: Active, Filed, Under Review, On Appeal…), "active" (disposition exactly Active), "closed", or "all". |
No output schema declared.
No examples provided.
blm_claims_summary ~160
Counts of US federal mining claims (BLM MLRS) within a radius of a point, broken down by claim type and status, with total recorded acres — how heavily staked is the ground around a deposit or project site, and how much of it is active versus closed.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | Latitude (WGS84) |
| longitude | number | yes | Longitude (WGS84) |
| radius_km | number | – | Radius in km, 0.1–50 (default 10) |
| status | string | – | Which claims: "open" (default — every claim not closed: Active, Filed, Under Review, On Appeal…), "active" (disposition exactly Active), "closed", or "all". |
No output schema declared.
No examples provided.
How do I install the Blm Mining Claims MCP server?
Blm Mining Claims runs locally as an npm package, launched with npx -y @pipeworx/mcp-blm-mining-claims. 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-blm-mining-claims
claude mcp add pipeworx-io-blm-mining-claims -- npx -y @pipeworx/mcp-blm-mining-claims
What is the Blm Mining Claims MCP server?
Blm Mining Claims is an MCP server listed in the public MCP registry as io.github.pipeworx-io/blm-mining-claims. BLM mining claims (MLRS), fleet #2826. This page covers its npm package (@pipeworx/mcp-blm-mining-claims).
Is the Blm Mining Claims MCP server safe to use?
Blm Mining Claims 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 Blm Mining Claims MCP server expose?
Blm Mining Claims exposes 4 tools: blm_claims_near, blm_claims_in_bbox, blm_claims_case, blm_claims_summary. Their descriptions and schemas cost roughly 847 tokens of context every time the server is loaded.
Is the Blm Mining Claims MCP server still maintained?
Blm Mining Claims 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 Blm Mining Claims MCP server under?
Blm Mining Claims 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 Blm Mining Claims MCP server?
VerifyMCP ran 15 checks on Blm Mining Claims, 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 Blm Mining Claims: 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.