Remote MCP · Endpoint
com.ainetcafe/netcafe-tables MCP server
Yes, as of 1 hour ago: the request timed out.
DownLast checked 1 hour ago
Server URL
https://ainetcafe.com/mcp/table?s=registry
The last check failed: the request timed out.
- Registry name
- com.ainetcafe/netcafe-tables
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 15 tools
- Uptime, last 30 days
- 50.0% from 18 checks
- Described by its publisher as
- Messy spreadsheets in, clean checkable tables out. Every result carries its arithmetic proof.
- Repository
- https://github.com/mario03690/ai-netcafe
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the request timed out | — |
| 1 day ago | Handshake completed | 515 ms |
| 2 days ago | Handshake completed | 487 ms |
| 3 days ago | Handshake completed | 529 ms |
| 4 days ago | Failed - the request timed out | — |
| 5 days ago | Handshake completed | 2.75 s |
| 6 days ago | Handshake completed | 1.13 s |
| 9 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 | — |
| 16 days ago | Failed - the server returned an HTTP error | — |
| 18 days ago | Failed - the server returned an HTTP error | — |
| 20 days ago | Failed - the server returned an HTTP error | — |
| 22 days ago | Failed - the server returned an HTTP error | — |
| 24 days ago | Handshake completed | 325 ms |
| 26 days ago | Handshake completed | 332 ms |
| 27 days ago | Handshake completed | 316 ms |
| 29 days ago | Handshake completed | 583 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 20 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/netcafe-tables and makes no claim about it beyond what these checks measured.