# Blm Mining Claims (npm · @pipeworx/mcp-blm-mining-claims)

BLM mining claims (MLRS) — fleet #2826.

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

## Components

- remote · `gateway.pipeworx.io`: 84/100, [markdown](https://verifymcp.io/servers/pipeworx-io-blm-mining-claims/blm-mining-claims-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-blm-mining-claims/blm-mining-claims-mcp)
- npm · `@pipeworx/mcp-blm-mining-claims`: 79/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-blm-mining-claims/pipeworx-mcp-blm-mining-claims.md), [page](https://verifymcp.io/servers/pipeworx-io-blm-mining-claims/pipeworx-mcp-blm-mining-claims)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-blm-mining-claims`
- 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-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-blm-mining-claims).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - 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.
  - 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 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.

### Claude

```bash
claude mcp add pipeworx-io-blm-mining-claims -- npx -y @pipeworx/mcp-blm-mining-claims
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-blm-mining-claims": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-blm-mining-claims"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-blm-mining-claims": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-blm-mining-claims"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-blm-mining-claims -- npx -y @pipeworx/mcp-blm-mining-claims
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-blm-mining-claims --command npx --arg -y --arg @pipeworx/mcp-blm-mining-claims
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-blm-mining-claims:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-blm-mining-claims"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-blm-mining-claims": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-blm-mining-claims"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-blm-mining-claims -t stdio -c npx -a -y @pipeworx/mcp-blm-mining-claims
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-blm-mining-claims": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-blm-mining-claims"
      ]
    }
  }
}
```

## 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-31 (score 79, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-30 (score 64)

First indexed and scored.

## MCP tools (4)

### `blm_claims_near` (~309 tokens)

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.

Input parameters:

- `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, required): Latitude (WGS84), e.g. 41.71
- `limit` (number): Claims to return, 1–500 (default 50)
- `longitude` (number, required): 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".

### `blm_claims_in_bbox` (~242 tokens)

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.

Input parameters:

- `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, required): North edge latitude
- `max_lon` (number, required): East edge longitude
- `min_lat` (number, required): South edge latitude
- `min_lon` (number, required): 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".

### `blm_claims_case` (~136 tokens)

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.

Input parameters:

- `case_id` (string, required): MLRS case serial number (e.g. NV101474832) or legacy serial (e.g. NMC1018964)

### `blm_claims_summary` (~160 tokens)

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.

Input parameters:

- `latitude` (number, required): Latitude (WGS84)
- `longitude` (number, required): 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".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-blm-mining-claims/pipeworx-mcp-blm-mining-claims#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: 64

## Common questions

### 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.

## Links

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