Remote MCP · Endpoint
Sipflow MCP server
No. Sipflow answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.sipflow.dev/mcp
The last check completed an MCP handshake.
- Registry name
- dev.sipflow/sipflow
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 291 ms
- Tools exposed
- 22 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- SIP/VoIP/telecom grounding for AI agents: vendor docs, RFCs, STIR/SHAKEN, traces, configs.
- Website
- https://www.sipflow.dev/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 291 ms |
| 1 day ago | Handshake completed | 197 ms |
| 3 days ago | Handshake completed | 211 ms |
| 3 days ago | Handshake completed | 272 ms |
| 4 days ago | Handshake completed | 268 ms |
| 5 days ago | Handshake completed | 187 ms |
| 7 days ago | Handshake completed | 9.67 s |
| 10 days ago | Handshake completed | 245 ms |
| 12 days ago | Handshake completed | 367 ms |
| 15 days ago | Handshake completed | 273 ms |
| 17 days ago | Handshake completed | 270 ms |
| 19 days ago | Handshake completed | 498 ms |
| 21 days ago | Handshake completed | 298 ms |
| 23 days ago | Handshake completed | 226 ms |
| 25 days ago | Handshake completed | 259 ms |
| 26 days ago | Handshake completed | 438 ms |
| 28 days ago | Handshake completed | 402 ms |
| 29 days ago | Handshake completed | 286 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 Sipflow and makes no claim about it beyond what these checks measured.