Remote MCP · Endpoint
FateMCP Destiny Weight MCP server
No. FateMCP Destiny Weight answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.fatemcp.com/destiny-weight
The last check completed an MCP handshake.
- Registry name
- io.github.optimizer668/destiny-weight
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 201 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- Destiny Weight reading from birth date — Yuan Tiangang method.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 201 ms |
| 4 hours ago | Handshake completed | 199 ms |
| 1 day ago | Handshake completed | 211 ms |
| 2 days ago | Handshake completed | 201 ms |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.
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 FateMCP Destiny Weight and makes no claim about it beyond what these checks measured.