Remote MCP · Endpoint

zobrx MCP server

No. zobrx answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.zobrx.com/mcp

The last check completed an MCP handshake.

Registry name
com.zobrx/zobrx
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
627 ms
Tools exposed
58 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Read-only zobrx e-commerce data: P&L, orders, inventory, marketplace, tax & shelf insights.
Listing
From the official MCP registry (active).
Recent checks of zobrx
CheckedResultHandshake
1 hour agoHandshake completed627 ms
2 days agoHandshake completed658 ms
4 days agoHandshake completed643 ms
5 days agoHandshake completed626 ms
7 days agoHandshake completed644 ms
8 days agoHandshake completed666 ms
9 days agoHandshake completed683 ms
12 days agoHandshake completed645 ms
13 days agoHandshake completed633 ms
15 days agoHandshake completed635 ms
16 days agoHandshake completed637 ms
18 days agoHandshake completed646 ms
19 days agoHandshake completed645 ms
20 days agoHandshake completed641 ms
20 days agoHandshake completed697 ms
21 days agoHandshake completed631 ms
22 days agoHandshake completed664 ms

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

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