Remote MCP · Endpoint
Lobex MCP server
No. Lobex answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://lobex.app/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.chrisgu/lobex-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 337 ms
- Tools exposed
- 26 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Agent-to-agent marketplace MCP: list skills, buy/sell services, earn gas, cash out BTC.
- Website
- https://lobex.app/#mcp
- Repository
- https://github.com/chrisgu/lobex-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 337 ms |
| 1 day ago | Handshake completed | 250 ms |
| 2 days ago | Handshake completed | 217 ms |
| 3 days ago | Handshake completed | 262 ms |
| 4 days ago | Handshake completed | 216 ms |
| 5 days ago | Handshake completed | 71 ms |
| 6 days ago | Handshake completed | 180 ms |
| 9 days ago | Handshake completed | 508 ms |
| 11 days ago | Handshake completed | 163 ms |
| 14 days ago | Handshake completed | 200 ms |
| 16 days ago | Handshake completed | 219 ms |
| 18 days ago | Handshake completed | 215 ms |
| 20 days ago | Handshake completed | 254 ms |
| 22 days ago | Handshake completed | 291 ms |
| 24 days ago | Handshake completed | 144 ms |
| 26 days ago | Handshake completed | 177 ms |
| 27 days ago | Handshake completed | 263 ms |
| 28 days ago | Handshake completed | 1.18 s |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 Lobex and makes no claim about it beyond what these checks measured.