Remote MCP · Endpoint

xyz.getava/ava MCP server

No. xyz.getava/ava answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://api.getava.xyz/mcp

The last check completed an MCP handshake.

Registry name
xyz.getava/ava
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
290 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Coding agents run multi-leg cross-chain DeFi. Legs re-derived from your sentence before signing.
Website
https://www.getava.xyz/
Repository
https://github.com/kamalbuilds/ava-4.0
Listing
From the official MCP registry (active).
Recent checks of xyz.getava/ava
CheckedResultHandshake
2 hours agoHandshake completed290 ms
2 days agoHandshake completed274 ms
4 days agoHandshake completed277 ms
6 days agoHandshake completed282 ms
7 days agoHandshake completed553 ms
9 days agoHandshake completed276 ms
10 days agoHandshake completed276 ms
11 days agoHandshake completed505 ms
14 days agoHandshake completed271 ms
15 days agoHandshake completed268 ms
17 days agoHandshake completed272 ms
18 days agoHandshake completed276 ms
19 days agoHandshake completed931 ms
20 days agoHandshake completed533 ms
21 days agoHandshake completed282 ms
22 days agoHandshake completed280 ms
23 days agoHandshake completed275 ms
24 days agoHandshake completed454 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with xyz.getava/ava and makes no claim about it beyond what these checks measured.