Remote MCP · Endpoint
com.ainetcafe/netcafe-devkit MCP server
No. com.ainetcafe/netcafe-devkit answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://ainetcafe.com/mcp/dev?s=registry
The last check completed an MCP handshake.
- Registry name
- com.ainetcafe/netcafe-devkit
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 539 ms
- Tools exposed
- 14 tools
- Uptime, last 30 days
- 55.6% from 18 checks
- Described by its publisher as
- JSON/YAML, regex, diff, JWT, SQL dialects — the keyless millisecond ops an agent needs mid-task.
- Repository
- https://github.com/mario03690/ai-netcafe
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 539 ms |
| 1 day ago | Handshake completed | 431 ms |
| 2 days ago | Handshake completed | 929 ms |
| 3 days ago | Handshake completed | 722 ms |
| 4 days ago | Handshake completed | 550 ms |
| 5 days ago | Handshake completed | 474 ms |
| 7 days ago | Failed - the request timed out | — |
| 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 | — |
| 25 days ago | Handshake completed | 652 ms |
| 26 days ago | Handshake completed | 500 ms |
| 27 days ago | Handshake completed | 464 ms |
| 29 days ago | Handshake completed | 1.05 s |
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/netcafe-devkit and makes no claim about it beyond what these checks measured.