Remote MCP · Endpoint

FateMCP Destiny Weight MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://mcp.fatemcp.com/destiny-weight

The last check failed: the server returned an HTTP error.

Registry name
io.github.optimizer668/destiny-weight
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
1 tool
Uptime, last 30 days
41.2% from 17 checks
Described by its publisher as
Destiny Weight reading from birth date — Yuan Tiangang method.
Repository
https://github.com/fatemcp/destiny-weight
Listing
From the official MCP registry (active).
Recent checks of FateMCP Destiny Weight
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
8 days agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
12 days agoFailed - the server returned an HTTP error—
13 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
17 days agoHandshake completed201 ms
18 days agoHandshake completed219 ms
19 days agoHandshake completed199 ms
20 days agoHandshake completed201 ms
20 days agoHandshake completed199 ms
21 days agoHandshake completed211 ms
23 days agoHandshake completed201 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.