Remote MCP · Endpoint

Fengshui Calculator MCP server

No. Fengshui Calculator answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://fengshuicalculator.com/v1/mcp

The last check completed an MCP handshake.

Registry name
com.fengshuicalculator/fengshui-calculator
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
288 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Verifiable Chinese calendar & feng shui: BaZi, flying stars, Kua, almanac. SHA-256 replayable.
Listing
From the official MCP registry (active).
Recent checks of Fengshui Calculator
CheckedResultHandshake
1 hour agoHandshake completed288 ms
3 days agoHandshake completed212 ms
12 days agoHandshake completed487 ms
13 days agoHandshake completed242 ms
15 days agoHandshake completed234 ms
15 days agoHandshake completed240 ms
17 days agoHandshake completed158 ms
18 days agoHandshake completed162 ms
18 days agoHandshake completed166 ms
20 days agoHandshake completed350 ms
22 days agoHandshake completed199 ms
25 days agoHandshake completed221 ms
27 days agoHandshake completed162 ms

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

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 Fengshui Calculator and makes no claim about it beyond what these checks measured.