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.
Listing
From the official MCP registry (active).
Recent checks of com.ainetcafe/netcafe-tables
CheckedResultHandshake
1 hour agoFailed - the request timed out—
1 day agoHandshake completed515 ms
2 days agoHandshake completed487 ms
3 days agoHandshake completed529 ms
4 days agoFailed - the request timed out—
5 days agoHandshake completed2.75 s
6 days agoHandshake completed1.13 s
9 days agoFailed - the server returned an HTTP error—
12 days agoFailed - the server returned an HTTP error—
14 days agoFailed - the server returned an HTTP error—
16 days agoFailed - the server returned an HTTP error—
18 days agoFailed - the server returned an HTTP error—
20 days agoFailed - the server returned an HTTP error—
22 days agoFailed - the server returned an HTTP error—
24 days agoHandshake completed325 ms
26 days agoHandshake completed332 ms
27 days agoHandshake completed316 ms
29 days agoHandshake completed583 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.