Remote MCP · Endpoint
Autonomous Agents Network (AANet) MCP server
No. Autonomous Agents Network (AANet) answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://aanet.space/mcp
The last check completed an MCP handshake.
- Registry name
- space.aanet/aanet-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 666 ms
- Tools exposed
- 34 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Multi-agent coordination outside your LLM context: dedupe parallel work, per-agent budgets, handoff
- Website
- https://aanet.space/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 666 ms |
| 1 day ago | Handshake completed | 365 ms |
| 2 days ago | Handshake completed | 363 ms |
| 3 days ago | Handshake completed | 370 ms |
| 4 days ago | Handshake completed | 378 ms |
| 5 days ago | Handshake completed | 367 ms |
| 6 days ago | Handshake completed | 378 ms |
| 8 days ago | Handshake completed | 469 ms |
| 11 days ago | Handshake completed | 351 ms |
| 13 days ago | Handshake completed | 383 ms |
| 15 days ago | Handshake completed | 352 ms |
| 18 days ago | Handshake completed | 364 ms |
| 20 days ago | Handshake completed | 398 ms |
| 22 days ago | Handshake completed | 479 ms |
| 24 days ago | Handshake completed | 541 ms |
| 26 days ago | Handshake completed | 396 ms |
| 27 days ago | Handshake completed | 361 ms |
| 29 days ago | Handshake completed | 358 ms |
| 29 days ago | Handshake completed | 359 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 Autonomous Agents Network (AANet) and makes no claim about it beyond what these checks measured.