Remote MCP · Endpoint

com.robtex/mcp MCP server

No. com.robtex/mcp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.robtex.com/mcp

The last check completed an MCP handshake.

Registry name
com.robtex/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
527 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
DNS, IP, AS, domain reputation, and Lightning Network intelligence (44 tools)
Listing
From the official MCP registry (active).
Recent checks of com.robtex/mcp
CheckedResultHandshake
1 hour agoHandshake completed527 ms
2 days agoHandshake completed54 ms
4 days agoHandshake completed271 ms
5 days agoHandshake completed1.14 s
7 days agoHandshake completed81 ms
8 days agoHandshake completed280 ms
9 days agoHandshake completed45 ms
12 days agoHandshake completed33 ms
13 days agoHandshake completed58 ms
15 days agoHandshake completed330 ms
16 days agoHandshake completed53 ms
17 days agoHandshake completed56 ms
18 days agoHandshake completed214 ms
19 days agoHandshake completed29 ms
20 days agoHandshake completed236 ms
21 days agoHandshake completed211 ms
22 days agoHandshake completed798 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 com.robtex/mcp and makes no claim about it beyond what these checks measured.