Remote MCP · Endpoint

ADEXTO MCP server

No. ADEXTO answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://adexto.xyz/api/mcp

The last check completed an MCP handshake.

Registry name
xyz.adexto/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
870 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Launch, buy, stake and claim on bonding-curve token markets across five chains, with your own key.
Listing
From the official MCP registry (active).
Recent checks of ADEXTO
CheckedResultHandshake
1 hour agoHandshake completed870 ms
2 days agoHandshake completed796 ms
5 days agoHandshake completed806 ms
7 days agoHandshake completed866 ms
9 days agoHandshake completed798 ms
11 days agoHandshake completed818 ms
13 days agoHandshake completed875 ms
15 days agoHandshake completed911 ms
17 days agoHandshake completed931 ms
18 days agoHandshake completed352 ms
20 days agoHandshake completed910 ms
21 days agoHandshake completed945 ms
23 days agoHandshake completed791 ms
25 days agoHandshake completed894 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 ADEXTO and makes no claim about it beyond what these checks measured.