Remote MCP · Endpoint
hush MCP server
No. hush answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://royashbrook.com/hush
The last check completed an MCP handshake.
- Registry name
- com.royashbrook/hush
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 1.03 s
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- A secret store for AI agents: the agent never sees the plaintext.
- Repository
- https://github.com/royashbrook/hush
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 1.03 s |
| 1 day ago | Handshake completed | 121 ms |
| 2 days ago | Handshake completed | 532 ms |
| 3 days ago | Handshake completed | 493 ms |
| 4 days ago | Handshake completed | 521 ms |
| 5 days ago | Handshake completed | 809 ms |
| 7 days ago | Handshake completed | 126 ms |
| 9 days ago | Handshake completed | 90 ms |
| 12 days ago | Handshake completed | 68 ms |
| 14 days ago | Handshake completed | 669 ms |
| 16 days ago | Handshake completed | 544 ms |
| 18 days ago | Handshake completed | 395 ms |
| 20 days ago | Handshake completed | 501 ms |
| 23 days ago | Handshake completed | 1.74 s |
| 25 days ago | Handshake completed | 372 ms |
| 26 days ago | Handshake completed | 494 ms |
| 28 days ago | Handshake completed | 456 ms |
| 29 days ago | Handshake completed | 734 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 hush and makes no claim about it beyond what these checks measured.