Remote MCP · Endpoint
com.ainetcafe/netcafe-almanac MCP server
No. com.ainetcafe/netcafe-almanac answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://ainetcafe.com/mcp/almanac?s=registry
The last check completed an MCP handshake.
- Registry name
- com.ainetcafe/netcafe-almanac
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 481 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 63.2% from 19 checks
- Described by its publisher as
- Chinese almanac: lunar calendar, BaZi 八字, daily 宜忌, lucky-day picker, public holidays.
- Website
- https://ainetcafe.com/tools
- Repository
- https://github.com/mario03690/ai-netcafe
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 481 ms |
| 18 hours ago | Handshake completed | 476 ms |
| 2 days ago | Handshake completed | 539 ms |
| 3 days ago | Handshake completed | 478 ms |
| 4 days ago | Handshake completed | 726 ms |
| 5 days ago | Handshake completed | 578 ms |
| 6 days ago | Handshake completed | 478 ms |
| 7 days ago | Handshake completed | 469 ms |
| 10 days ago | Failed - the server returned an HTTP error | — |
| 13 days ago | Failed - the server returned an HTTP error | — |
| 15 days ago | Failed - the server returned an HTTP error | — |
| 17 days ago | Failed - the server returned an HTTP error | — |
| 19 days ago | Failed - the server returned an HTTP error | — |
| 21 days ago | Failed - the server returned an HTTP error | — |
| 23 days ago | Failed - the server returned an HTTP error | — |
| 25 days ago | Handshake completed | 490 ms |
| 27 days ago | Handshake completed | 743 ms |
| 28 days ago | Handshake completed | 462 ms |
| 29 days ago | Handshake completed | 992 ms |
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.
Listing data comes from the official MCP registry. Glide is not affiliated with com.ainetcafe/netcafe-almanac and makes no claim about it beyond what these checks measured.