Remote MCP · Endpoint

CallFlow AI MCP server

No. CallFlow AI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://callflow-ai-nine.vercel.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.sarvin-tech/callflow-ai
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
85 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Paid sales-call scoring and CRM next-step analysis for AI agents.
Listing
From the official MCP registry (active).
Recent checks of CallFlow AI
CheckedResultHandshake
1 hour agoHandshake completed85 ms
2 days agoHandshake completed138 ms
4 days agoHandshake completed102 ms
6 days agoHandshake completed59 ms
8 days agoHandshake completed232 ms
10 days agoHandshake completed147 ms
12 days agoHandshake completed144 ms
14 days agoHandshake completed66 ms
15 days agoHandshake completed66 ms
16 days agoHandshake completed60 ms
17 days agoHandshake completed114 ms
20 days agoHandshake completed61 ms
22 days agoHandshake completed62 ms
23 days agoHandshake completed909 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

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 CallFlow AI and makes no claim about it beyond what these checks measured.