Blm Mining Claims MCP server

@pipeworx/blm-mining-claims

US federal mining claims from the Bureau of Land Management's Mineral and Land Records System (MLRS): claims near a point or inside a box, one claim by case serial number, and claim counts by type and status around a site. Each result has the case serial, claim name, lode/placer/mill-site/tunnel-site type, status, recorded acres, the PLSS legal land description and a link to the MLRS case record.

Part of Pipeworx — an MCP gateway connecting AI agents to 1763+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

• blmclaimsnear(latitude, longitude, radiuskm?, status?, claimtype?, limit?, afterobjectid?): claims within a radius (max 50 km) of a point, with the total count in the radius. Each page is sorted by distance. Use it to see who has staked ground around a lithium, gold or uranium deposit.
• blmclaimsinbbox(minlat, minlon, maxlat, maxlon, status?, claimtype?, limit?, afterobjectid?): the same for a bounding box of up to 2° on a side.
• blmclaimscase(case_id): one case by MLRS serial (NV101474832) or legacy serial (NMC1018964). Returns type, status, acres, patented/excluded/conveyed flags, the parsed PLSS legal land description (meridian, township, range, section, aliquot part), the mapped bounding box, BLM's mapping-quality log and the MLRS link.
• blmclaimssummary(latitude, longitude, radius_km?, status?): counts and total recorded acres by claim type and status within a radius.

status accepts open (default: every case not closed, including Active, Filed, Under Review and On Appeal), active (disposition exactly Active), closed or all. claimtype accepts lode, placer, millsite or tunnel_site.

Auth

Keyless.

Data sources

• : BLM MLRS mining-claim case layer (ArcGIS MapServer). Layer 0 holds every case, layer 1 holds cases that are not closed, and layer 2 holds closed cases. Each call queries the service live.
• : the MLRS case record that mlrscaseurl opens.

Things the next person would otherwise rediscover:

• The geometry is not the staked boundary. BLM maps each case's recorded Legal Land Description onto the PLSS cadastral grid, so a 20-acre lode claim appears as the aliquot part(s) it was recorded in. The QLTY score says how well the mapping worked. geometry_basis turns it into words: direct PLSS match, calculated, section-only, county-only, no geometry, or hand-edited by BLM.
• The layer has no location date, claimant names or claimant count. Those fields exist only in the MLRS case record. The tools say so in fieldsnotin_layer rather than returning nulls.
• No as-of date is published. The service carries no editingInfo or documentInfo date, so dataasof is the time of the live query and dataasof_basis says that.
• orderByFields is very slow: 30–60 s against about 5 s without it, measured 2026-10-08. Rows come back in OBJECTID order, so paging uses an OBJECTID cursor (afterobjectid → nextafterobject_id).
• resultOffset is off by one on spatial queries. Offset 0 returns one row short, and offset k starts at row k−1. Paging by offset would repeat or skip a claim, which is why this pack uses the cursor instead.
• BLMPROD capitalization varies (Lode Claim and LODE CLAIM both occur), so type filters match on UPPER(BLMPROD) LIKE 'LODE CLAIM%', which also includes the "– National Park" variants.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "blm-mining-claims": {
      "url": "https://gateway.pipeworx.io/blm-mining-claims/mcp"
    }
  }
}

What this endpoint actually serves

Shortened. The full README is on GitHub.