Remote MCP · Endpoint

Blm Mining Claims MCP server

No. Blm Mining Claims answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/blm-mining-claims/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/blm-mining-claims
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
176 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
BLM mining claims (MLRS) — fleet #2826.
Listing
From the official MCP registry (active).
Recent checks of Blm Mining Claims
CheckedResultHandshake
1 hour agoHandshake completed176 ms
1 day agoHandshake completed104 ms
2 days agoHandshake completed102 ms
2 days agoHandshake completed141 ms
4 days agoHandshake completed214 ms
6 days agoHandshake completed628 ms
9 days agoHandshake completed1.33 s
12 days agoHandshake completed140 ms
14 days agoHandshake completed3.28 s
16 days agoHandshake completed1.05 s
18 days agoHandshake completed1.26 s
20 days agoHandshake completed1.94 s
22 days agoHandshake completed504 ms
24 days agoHandshake completed2.47 s

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Blm Mining Claims and makes no claim about it beyond what these checks measured.