MCP server exposing 4 tools for blm-mining-claims.
This URL is a JSON-RPC 2.0 endpoint over HTTP. Issue POST requests with a JSON-RPC body. Browsers and search crawlers land here on GET.
POST https://gateway.pipeworx.io/blm-mining-claims/mcp
Content-Type: application/json
{"jsonrpc":"2.0","id":1,"method":"tools/list"}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 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.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/placer/mill-site type, status, acres, mapped center and an MLRS case-record link.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 description (meridian, township, range, section, aliquot parts), how well BLM could map it, the mapped bounding box, and the MLRS case-record link.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 site, and how much of it is active versus closed.Code samples (curl / TypeScript / one-click client install), schemas, and the live playground are on the pack page:
https://pipeworx.io/packs/blm-mining-claims/
Pipeworx is an open MCP gateway connecting AI agents to live data. pipeworx.io