Remote MCP · Endpoint

1gateway MCP server

No. 1gateway answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://1gateway.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.code0xff/1gateway
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
665 ms
Tools exposed
90 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Pay-per-call tools for agents via x402 (USDC on Base): Korean data, doc-to-Markdown, web utilities.
Listing
From the official MCP registry (active).
Recent checks of 1gateway
CheckedResultHandshake
2 hours agoHandshake completed665 ms
1 day agoHandshake completed877 ms
2 days agoHandshake completed454 ms
2 days agoHandshake completed167 ms
4 days agoHandshake completed87 ms
7 days agoHandshake completed864 ms
9 days agoHandshake completed663 ms
12 days agoHandshake completed561 ms
14 days agoHandshake completed222 ms
16 days agoHandshake completed330 ms
18 days agoHandshake completed320 ms
20 days agoHandshake completed347 ms
22 days agoHandshake completed60 ms
24 days agoHandshake completed447 ms

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

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