Remote MCP · Endpoint
KYMA Frequency MCP MCP server
No. KYMA Frequency MCP answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://eaqistzhmblvuxndwfbn.supabase.co/functions/v1/freq-mcp
The last check completed an MCP handshake.
- Registry name
- io.github.BCXTRUST/kyma-frequency-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 434 ms
- Tools exposed
- 12 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Search KYMA369's public frequency library and open sets in the free KYMA app.
- Website
- https://kyma369.com/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 434 ms |
| 1 day ago | Handshake completed | 474 ms |
| 2 days ago | Handshake completed | 499 ms |
| 3 days ago | Handshake completed | 485 ms |
| 4 days ago | Handshake completed | 581 ms |
| 5 days ago | Handshake completed | 420 ms |
| 6 days ago | Handshake completed | 550 ms |
| 9 days ago | Handshake completed | 780 ms |
| 12 days ago | Handshake completed | 1.16 s |
| 14 days ago | Handshake completed | 881 ms |
| 16 days ago | Handshake completed | 447 ms |
| 18 days ago | Handshake completed | 532 ms |
| 20 days ago | Handshake completed | 546 ms |
| 22 days ago | Handshake completed | 409 ms |
| 24 days ago | Handshake completed | 403 ms |
| 26 days ago | Handshake completed | 408 ms |
| 27 days ago | Handshake completed | 418 ms |
| 28 days ago | Handshake completed | 364 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 KYMA Frequency MCP and makes no claim about it beyond what these checks measured.