Remote MCP · Endpoint
com.ainetcafe/ai-netcafe MCP server
No. com.ainetcafe/ai-netcafe answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://ainetcafe.com/mcp?s=registry
The last check completed an MCP handshake.
- Registry name
- com.ainetcafe/ai-netcafe
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 486 ms
- Tools exposed
- 34 tools
- Uptime, last 30 days
- 55.6% from 18 checks
- Described by its publisher as
- Tables and ledgers checked by arithmetic, not by a model. 24 tools. MCP 2026-07-28 ready.
- Repository
- https://github.com/mario03690/ai-netcafe
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 486 ms |
| 1 day ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Handshake completed | 1.02 s |
| 3 days ago | Handshake completed | 721 ms |
| 4 days ago | Handshake completed | 472 ms |
| 5 days ago | Handshake completed | 461 ms |
| 7 days ago | Handshake completed | 5.42 s |
| 10 days ago | Failed - the server returned an HTTP error | — |
| 12 days ago | Failed - the server returned an HTTP error | — |
| 14 days ago | Failed - the server returned an HTTP error | — |
| 17 days ago | Failed - the server returned an HTTP error | — |
| 19 days ago | Failed - the server returned an HTTP error | — |
| 21 days ago | Failed - the server returned an HTTP error | — |
| 23 days ago | Failed - the server returned an HTTP error | — |
| 25 days ago | Handshake completed | 491 ms |
| 26 days ago | Handshake completed | 457 ms |
| 28 days ago | Handshake completed | 509 ms |
| 29 days ago | Handshake completed | 706 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 21 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 com.ainetcafe/ai-netcafe and makes no claim about it beyond what these checks measured.