Remote MCP · Endpoint

com.ainetcafe/netcafe-build MCP server

No. com.ainetcafe/netcafe-build answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ainetcafe.com/mcp/build?s=registry

The last check completed an MCP handshake.

Registry name
com.ainetcafe/netcafe-build
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
492 ms
Tools exposed
7 tools
Uptime, last 30 days
63.2% from 19 checks
Described by its publisher as
Deploy a live web app from one sentence. build_app + poll to a public HTTPS URL you own.
Website
https://ainetcafe.com/build.html
Repository
https://github.com/mario03690/ai-netcafe
Listing
From the official MCP registry (active).
Recent checks of com.ainetcafe/netcafe-build
CheckedResultHandshake
1 hour agoHandshake completed492 ms
18 hours agoHandshake completed546 ms
2 days agoHandshake completed525 ms
3 days agoHandshake completed448 ms
4 days agoHandshake completed1.10 s
5 days agoHandshake completed793 ms
6 days agoHandshake completed481 ms
7 days agoHandshake completed523 ms
10 days agoFailed - the server returned an HTTP error—
13 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
17 days agoFailed - the server returned an HTTP error—
19 days agoFailed - the server returned an HTTP error—
21 days agoFailed - the server returned an HTTP error—
23 days agoFailed - the server returned an HTTP error—
25 days agoHandshake completed478 ms
27 days agoHandshake completed516 ms
28 days agoHandshake completed545 ms
29 days agoHandshake completed1.08 s

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 23 responding of 30.

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with com.ainetcafe/netcafe-build and makes no claim about it beyond what these checks measured.