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.
- Website
- https://avva.chat/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 739 ms |
| 13 hours ago | Handshake completed | 1.34 s |
| 1 day ago | Handshake completed | 696 ms |
| 3 days ago | Handshake completed | 927 ms |
| 4 days ago | Handshake completed | 1.52 s |
| 4 days ago | Failed - the TLS certificate could not be verified | — |
| 5 days ago | Handshake completed | 236 ms |
| 6 days ago | Handshake completed | 622 ms |
| 8 days ago | Handshake completed | 324 ms |
| 11 days ago | Handshake completed | 287 ms |
| 13 days ago | Handshake completed | 248 ms |
| 16 days ago | Handshake completed | 382 ms |
| 18 days ago | Handshake completed | 315 ms |
| 20 days ago | Handshake completed | 2.29 s |
| 22 days ago | Handshake completed | 248 ms |
| 24 days ago | Handshake completed | 179 ms |
| 26 days ago | Handshake completed | 157 ms |
| 27 days ago | Handshake completed | 279 ms |
| 29 days ago | Handshake completed | 446 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.