Remote MCP · Endpoint
com.ainetcafe/netcafe-tasks MCP server
No. com.ainetcafe/netcafe-tasks answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://ainetcafe.com/mcp/tasks?s=registry
The last check completed an MCP handshake.
- Registry name
- com.ainetcafe/netcafe-tasks
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 935 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 44.4% from 18 checks
- Described by its publisher as
- Recurring agent jobs that run on our servers and ping you only when the result changed.
- Repository
- https://github.com/mario03690/ai-netcafe
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 935 ms |
| 1 day ago | Handshake completed | 578 ms |
| 2 days ago | Handshake completed | 609 ms |
| 3 days ago | Failed - the request timed out | — |
| 4 days ago | Failed - the request timed out | — |
| 5 days ago | Failed - the request timed out | — |
| 6 days ago | Handshake completed | 496 ms |
| 9 days ago | Failed - the server returned an HTTP error | — |
| 11 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 | 310 ms |
| 26 days ago | Handshake completed | 333 ms |
| 27 days ago | Handshake completed | 312 ms |
| 29 days ago | Handshake completed | 1.83 s |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 19 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-tasks and makes no claim about it beyond what these checks measured.