Remote MCP · Endpoint

com.ainetcafe/netcafe-docflow MCP server

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

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
com.ainetcafe/netcafe-docflow
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
538 ms
Tools exposed
13 tools
Uptime, last 30 days
61.1% from 18 checks
Described by its publisher as
Markdown in, any format out. PDFs merged, split, watermarked. Runs on our own doc engines.
Listing
From the official MCP registry (active).
Recent checks of com.ainetcafe/netcafe-docflow
CheckedResultHandshake
1 hour agoHandshake completed538 ms
1 day agoHandshake completed510 ms
2 days agoHandshake completed1.21 s
3 days agoHandshake completed1.06 s
4 days agoHandshake completed1.20 s
5 days agoHandshake completed453 ms
6 days agoHandshake completed1.58 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 completed509 ms
26 days agoHandshake completed482 ms
27 days agoHandshake completed451 ms
29 days agoHandshake completed1.40 s

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 22 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-docflow and makes no claim about it beyond what these checks measured.