Remote MCP · Endpoint

Aether testnet wallet MCP server

No. Aether testnet wallet answered an MCP handshake 38 minutes ago.

UpLast checked 38 minutes ago

Server URL

https://explorer.157-245-252-221.sslip.io/mcp

The last check completed an MCP handshake.

Registry name
io.github.whoyoujoshin/aether-wallet
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
50 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Testnet wallet for AI agents on Aether: pay, get paid and buy from paid APIs, with spending caps.
Listing
From the official MCP registry (active).
Recent checks of Aether testnet wallet
CheckedResultHandshake
38 minutes agoHandshake completed50 ms
3 days agoHandshake completed136 ms
13 days agoHandshake completed39 ms
13 days agoHandshake completed39 ms
15 days agoHandshake completed44 ms
16 days agoHandshake completed46 ms
17 days agoHandshake completed45 ms
18 days agoHandshake completed42 ms
18 days agoHandshake completed47 ms
20 days agoHandshake completed42 ms
22 days agoHandshake completed79 ms
25 days agoHandshake completed57 ms
27 days agoHandshake completed44 ms
30 days agoHandshake completed44 ms

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

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