Remote MCP · Endpoint

Sipflow MCP server

No. Sipflow answered an MCP handshake 7 hours ago.

UpLast checked 7 hours 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
298 ms
Tools exposed
22 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
SIP/VoIP/telecom grounding for AI agents: vendor docs, RFCs, STIR/SHAKEN, traces, configs.
Listing
From the official MCP registry (active).
Recent checks of Sipflow
CheckedResultHandshake
7 hours agoHandshake completed298 ms
2 days agoHandshake completed226 ms
4 days agoHandshake completed259 ms
5 days agoHandshake completed438 ms
7 days agoHandshake completed402 ms
8 days agoHandshake completed286 ms
9 days agoHandshake completed372 ms
12 days agoHandshake completed327 ms
13 days agoHandshake completed250 ms
15 days agoHandshake completed726 ms
16 days agoHandshake completed174 ms
17 days agoHandshake completed191 ms
19 days agoHandshake completed217 ms
19 days agoHandshake completed185 ms
20 days agoHandshake completed278 ms
21 days agoHandshake completed159 ms
22 days agoHandshake completed165 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 Sipflow and makes no claim about it beyond what these checks measured.