Remote MCP · Endpoint

net.gentechlabs/x402-gateway MCP server

Yes, as of 1 hour ago: the TLS certificate could not be verified.

DownLast checked 1 hour ago

Server URL

https://api.gentechlabs.net/mcp

The last check failed: the TLS certificate could not be verified.

Registry name
net.gentechlabs/x402-gateway
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
15 tools
Uptime, last 30 days
82.4% from 17 checks
Described by its publisher as
Pay-per-call x402 services for agents: risk scoring, DeFi, wallet and market data.
Listing
From the official MCP registry (active).
Recent checks of net.gentechlabs/x402-gateway
CheckedResultHandshake
1 hour agoFailed - the TLS certificate could not be verified—
2 days agoFailed - the TLS certificate could not be verified—
4 days agoFailed - the TLS certificate could not be verified—
5 days agoHandshake completed156 ms
7 days agoHandshake completed291 ms
8 days agoHandshake completed51 ms
9 days agoHandshake completed52 ms
12 days agoHandshake completed50 ms
13 days agoHandshake completed54 ms
15 days agoHandshake completed51 ms
17 days agoHandshake completed49 ms
18 days agoHandshake completed49 ms
19 days agoHandshake completed48 ms
20 days agoHandshake completed52 ms
21 days agoHandshake completed55 ms
21 days agoHandshake completed51 ms
23 days agoHandshake completed46 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 net.gentechlabs/x402-gateway and makes no claim about it beyond what these checks measured.