Remote MCP · Endpoint

chat.avva/catalog MCP server

No. chat.avva/catalog answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://avva.chat/mcp-catalog

The last check completed an MCP handshake.

Registry name
chat.avva/catalog
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
739 ms
Tools exposed
2 tools
Uptime, last 30 days
94.7% from 19 checks
Described by its publisher as
Search Avva for an expert, then connect their model - judgment from real past decisions.
Listing
From the official MCP registry (active).
Recent checks of chat.avva/catalog
CheckedResultHandshake
1 hour agoHandshake completed739 ms
13 hours agoHandshake completed1.34 s
1 day agoHandshake completed696 ms
3 days agoHandshake completed927 ms
4 days agoHandshake completed1.52 s
4 days agoFailed - the TLS certificate could not be verified—
5 days agoHandshake completed236 ms
6 days agoHandshake completed622 ms
8 days agoHandshake completed324 ms
11 days agoHandshake completed287 ms
13 days agoHandshake completed248 ms
16 days agoHandshake completed382 ms
18 days agoHandshake completed315 ms
20 days agoHandshake completed2.29 s
22 days agoHandshake completed248 ms
24 days agoHandshake completed179 ms
26 days agoHandshake completed157 ms
27 days agoHandshake completed279 ms
29 days agoHandshake completed446 ms

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

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 chat.avva/catalog and makes no claim about it beyond what these checks measured.