@pipeworx/blm-mining-claims
Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/blm-mining-claims’s. Install: one-click buttons
Connect to just the @pipeworx/blm-mining-claims pack
https://gateway.pipeworx.io/blm-mining-claims/mcp — only @pipeworx/blm-mining-claims’s own tools, nothing else in the catalog.
No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.
Tools: 4
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.
Tools
blm_claims_near(latitude, longitude, radius_km?, status?, claim_type?, limit?, after_object_id?): 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.blm_claims_in_bbox(min_lat, min_lon, max_lat, max_lon, status?, claim_type?, limit?, after_object_id?): the same for a bounding box of up to 2° on a side.blm_claims_case(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.blm_claims_summary(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. claim_type accepts lode, placer, mill_site or tunnel_site.
Auth
Keyless.
Data sources
- https://gis.blm.gov/nlsdb/rest/services/Mining_Claims/MiningClaims/MapServer: 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.
- https://mlrs.blm.gov/: the MLRS case record that
mlrs_case_urlopens.
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
QLTYscore says how well the mapping worked.geometry_basisturns 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
fields_not_in_layerrather than returning nulls. - No as-of date is published. The service carries no editingInfo or documentInfo date, so
data_as_ofis the time of the live query anddata_as_of_basissays that. orderByFieldsis 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 (after_object_id→next_after_object_id).resultOffsetis 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.BLM_PRODcapitalization varies (Lode ClaimandLODE CLAIMboth occur), so type filters match onUPPER(BLM_PROD) LIKE 'LODE CLAIM%', which also includes the ”– National Park” variants.
Tools
- blm_claims_near — 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
- blm_claims_in_bbox — 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/pla
- blm_claims_case — 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 descriptio
- blm_claims_summary — 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
Tools
blm_claims_case— 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 descriptionblm_claims_in_bbox— 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/plablm_claims_near— 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 inblm_claims_summary— 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