Remote MCP · Endpoint

com.ainetcafe/netcafe-tasks MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

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

The last check failed: the server returned an HTTP error.

Registry name
com.ainetcafe/netcafe-tasks
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
6 tools
Uptime, last 30 days
88.2% from 17 checks
Described by its publisher as
Recurring agent jobs that run on our servers and ping you only when the result changed.
Listing
From the official MCP registry (active).
Recent checks of com.ainetcafe/netcafe-tasks
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoHandshake completed310 ms
5 days agoHandshake completed333 ms
7 days agoHandshake completed312 ms
8 days agoHandshake completed1.83 s
9 days agoHandshake completed314 ms
12 days agoHandshake completed313 ms
14 days agoHandshake completed327 ms
15 days agoHandshake completed330 ms
17 days agoHandshake completed350 ms
18 days agoHandshake completed309 ms
19 days agoHandshake completed313 ms
20 days agoHandshake completed309 ms
20 days agoHandshake completed321 ms
22 days agoHandshake completed310 ms
23 days agoHandshake completed329 ms

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

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.