Remote MCP · Endpoint

io.tranx/alice MCP server

No. io.tranx/alice answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tranx.io/api/mcp

The last check completed an MCP handshake.

Registry name
io.tranx/alice
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
103 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Audit any site's AI visibility from your assistant: crawler access, rendering, and schema.
Listing
From the official MCP registry (active).
Recent checks of io.tranx/alice
CheckedResultHandshake
1 hour agoHandshake completed103 ms
2 days agoHandshake completed78 ms
4 days agoHandshake completed198 ms
5 days agoHandshake completed96 ms
7 days agoHandshake completed106 ms
8 days agoHandshake completed112 ms
9 days agoHandshake completed134 ms
12 days agoHandshake completed99 ms
13 days agoHandshake completed119 ms
15 days agoHandshake completed106 ms
17 days agoHandshake completed93 ms
18 days agoHandshake completed95 ms
19 days agoHandshake completed100 ms
20 days agoHandshake completed101 ms
20 days agoHandshake completed87 ms
21 days agoHandshake completed90 ms
22 days agoHandshake completed94 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 io.tranx/alice and makes no claim about it beyond what these checks measured.