Remote MCP · Endpoint
io.github.Kotaro-Studio/curanz-sounds MCP server
No. io.github.Kotaro-Studio/curanz-sounds answered an MCP handshake 51 minutes ago.
UpLast checked 51 minutes ago
Server URL
https://curanzsounds.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.Kotaro-Studio/curanz-sounds
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 910 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- 生年月日から占いを計算して答える。星座・九星気学の本命星と年盤・四柱推命の日干と流年・天中殺・数秘術の個人年。出生時刻は不要。古典の暦法による計算。
- Website
- https://curanzsounds.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 51 minutes ago | Handshake completed | 910 ms |
| 1 hour ago | Handshake completed | 902 ms |
| 1 day ago | Handshake completed | 758 ms |
| 2 days ago | Handshake completed | 1.86 s |
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 io.github.Kotaro-Studio/curanz-sounds and makes no claim about it beyond what these checks measured.