Remote MCP · Endpoint
io.github.tang-vu/keryx MCP server
No. io.github.tang-vu/keryx answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://keryx.cc/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.tang-vu/keryx
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 809 ms
- Tools exposed
- 27 tools
- Uptime, last 30 days
- 89.5% from 19 checks
- Described by its publisher as
- Budgeted research with cited evidence and visible payment state on the selected Arc network.
- Website
- https://keryx.cc/
- Repository
- https://github.com/tang-vu/keryx
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 809 ms |
| 1 day ago | Handshake completed | 779 ms |
| 2 days ago | Handshake completed | 769 ms |
| 3 days ago | Handshake completed | 803 ms |
| 4 days ago | Handshake completed | 1.03 s |
| 5 days ago | Handshake completed | 1.91 s |
| 6 days ago | Handshake completed | 859 ms |
| 8 days ago | Handshake completed | 812 ms |
| 11 days ago | Handshake completed | 6.65 s |
| 13 days ago | Handshake completed | 813 ms |
| 15 days ago | Handshake completed | 870 ms |
| 18 days ago | Handshake completed | 797 ms |
| 20 days ago | Handshake completed | 855 ms |
| 22 days ago | Handshake completed | 775 ms |
| 24 days ago | Failed - the check failed for an unclassified reason | — |
| 26 days ago | Handshake completed | 786 ms |
| 27 days ago | Handshake completed | 802 ms |
| 28 days ago | Failed - the server returned an HTTP error | — |
| 29 days ago | Handshake completed | 829 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 27 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 io.github.tang-vu/keryx and makes no claim about it beyond what these checks measured.