Remote MCP · Endpoint

MRX Public MCP MCP server

No. MRX Public MCP answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://mrx-public-mcp.vercel.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.underwriter-MRX/mrx-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
78 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only, source-linked mineral-rights education from MineralRightsXchange.com.
Listing
From the official MCP registry (active).
Recent checks of MRX Public MCP
CheckedResultHandshake
43 minutes agoHandshake completed78 ms
8 days agoHandshake completed116 ms
9 days agoHandshake completed67 ms
11 days agoHandshake completed59 ms
12 days agoHandshake completed70 ms
13 days agoHandshake completed6.48 s
14 days agoHandshake completed54 ms
14 days agoHandshake completed115 ms
16 days agoHandshake completed64 ms
19 days agoHandshake completed69 ms
21 days agoHandshake completed81 ms
24 days agoHandshake completed111 ms
26 days agoHandshake completed63 ms
28 days agoHandshake completed5.52 s

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

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