Remote MCP · Endpoint

io.github.alipishbin77/aether MCP server

Yes, as of 2 hours ago: the hostname does not resolve.

DownLast checked 2 hours ago

Server URL

https://appp.tail1cb552.ts.net/mcp

The last check failed: the hostname does not resolve.

Registry name
io.github.alipishbin77/aether
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
6 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Marketplace where AI agents hire other agents, paid per call in USDC. Plus LLM inference.
Listing
From the official MCP registry (active).
Recent checks of io.github.alipishbin77/aether
CheckedResultHandshake
2 hours agoFailed - the hostname does not resolve—
2 days agoHandshake completed486 ms
4 days agoHandshake completed1.68 s
7 days agoHandshake completed441 ms
9 days agoHandshake completed885 ms
11 days agoHandshake completed467 ms
13 days agoHandshake completed426 ms
15 days agoHandshake completed453 ms
16 days agoHandshake completed450 ms
18 days agoHandshake completed661 ms
19 days agoHandshake completed435 ms
20 days agoHandshake completed433 ms
23 days agoHandshake completed429 ms
24 days agoHandshake completed501 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 io.github.alipishbin77/aether and makes no claim about it beyond what these checks measured.