Remote MCP · Endpoint
io.github.michal-lefler/secure-flows MCP server
No. io.github.michal-lefler/secure-flows answered an MCP handshake 2 hours ago.
UpLast checked 2 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
- 479 ms
- Tools exposed
- 18 tools
- Uptime, last 30 days
- 100% from 18 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 |
|---|---|---|
| 2 hours ago | Handshake completed | 479 ms |
| 1 day ago | Handshake completed | 299 ms |
| 3 days ago | Handshake completed | 393 ms |
| 3 days ago | Handshake completed | 335 ms |
| 4 days ago | Handshake completed | 350 ms |
| 5 days ago | Handshake completed | 434 ms |
| 7 days ago | Handshake completed | 719 ms |
| 10 days ago | Handshake completed | 179 ms |
| 12 days ago | Handshake completed | 380 ms |
| 15 days ago | Handshake completed | 438 ms |
| 17 days ago | Handshake completed | 435 ms |
| 19 days ago | Handshake completed | 476 ms |
| 21 days ago | Handshake completed | 334 ms |
| 23 days ago | Handshake completed | 224 ms |
| 25 days ago | Handshake completed | 363 ms |
| 26 days ago | Handshake completed | 344 ms |
| 28 days ago | Handshake completed | 234 ms |
| 29 days ago | Handshake completed | 327 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 io.github.michal-lefler/secure-flows and makes no claim about it beyond what these checks measured.