Remote MCP · Endpoint
io.github.michal-lefler/secure-flows MCP server
No. io.github.michal-lefler/secure-flows answered an MCP handshake 9 hours ago.
UpLast checked 9 hours ago
Server URL
https://www.secure-flows.com/mcp?alias=secure-flows
The last check completed an MCP handshake.
- Registry name
- io.github.michal-lefler/secure-flows
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 334 ms
- Tools exposed
- 18 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- MCP server for secureFlows (secure-flows.com). Alias of io.github.michal-lefler/secureflows-mcp.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 9 hours ago | Handshake completed | 334 ms |
| 2 days ago | Handshake completed | 224 ms |
| 4 days ago | Handshake completed | 363 ms |
| 5 days ago | Handshake completed | 344 ms |
| 7 days ago | Handshake completed | 234 ms |
| 8 days ago | Handshake completed | 327 ms |
| 9 days ago | Handshake completed | 326 ms |
| 12 days ago | Handshake completed | 245 ms |
| 14 days ago | Handshake completed | 317 ms |
| 15 days ago | Handshake completed | 227 ms |
| 16 days ago | Handshake completed | 330 ms |
| 17 days ago | Handshake completed | 283 ms |
| 19 days ago | Handshake completed | 284 ms |
| 19 days ago | Handshake completed | 284 ms |
| 20 days ago | Handshake completed | 275 ms |
| 21 days ago | Handshake completed | 327 ms |
| 23 days ago | Handshake completed | 289 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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.
Listing data comes from the official MCP registry. Glide is not affiliated with io.github.michal-lefler/secure-flows and makes no claim about it beyond what these checks measured.