Remote MCP · Endpoint

Msha Mines MCP server

No. Msha Mines answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/msha-mines/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/msha-mines
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
125 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
MSHA mine records — search a US mine by operator or mine name, or look up a known MSHA Mine ID for…
Listing
From the official MCP registry (active).
Recent checks of Msha Mines
CheckedResultHandshake
1 hour agoHandshake completed125 ms
22 hours agoHandshake completed59 ms
1 day agoHandshake completed82 ms
2 days agoHandshake completed100 ms
4 days agoHandshake completed326 ms
7 days agoHandshake completed99 ms
9 days agoHandshake completed109 ms
12 days agoHandshake completed373 ms
14 days agoHandshake completed167 ms
16 days agoHandshake completed63 ms
18 days agoHandshake completed80 ms
20 days agoHandshake completed3.10 s
22 days agoHandshake completed966 ms
24 days agoHandshake completed569 ms

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 Msha Mines and makes no claim about it beyond what these checks measured.