mcpbeat Sign in

CallFlow AI MCP Server

not responding

CallFlow AI is listed as active in the registry but did not answer our last check. It exposes 2 tools.

Paid sales-call scoring and CRM next-step analysis for AI agents.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 18 days of history · worst day 20%
18 days agonow
50.0%
Uptime 24h
46 of 92 checks
2
Tools
read from the server
364 ms
Response time
average over 24h
open, no key
Access
streamable-http

CallFlow AI does not always answer

Over the last week it answered 67.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add callflow-ai --transport http https://callflow-ai-nine.vercel.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "callflow-ai": {
      "url": "https://callflow-ai-nine.vercel.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.callflow-ai]
url = "https://callflow-ai-nine.vercel.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "callflow-ai": {
      "url": "https://callflow-ai-nine.vercel.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "callflow-ai": {
      "url": "https://callflow-ai-nine.vercel.app/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

analyze
analyze_sales_call
Paid sales-call transcript analysis. Without paymentSignature it returns the x402 payment challenge. Retry with a valid PAYMENT-SIGNATURE for the analysis.
callflow
get_callflow_payment_info
Returns the CallFlow paid sales-call API URL, price, network and x402 payment protocol without charging.

Endpoints

URLTransportStateLatencyChecked
https://callflow-ai-nine.vercel.app/mcp streamable-http answering 44 ms 12 min ago

Alternatives to CallFlow AI

same job, measured the same way
Canarics
by canarics

AI call analysis and voice agents for sales teams. Signup, usage, agents and call data over MCP.

2 tools answering
Lint
by rog0x

Style check, naming, complexity analysis for AI agents

28 installs/wk local only
Arbitrum Transaction Preflight
by naur9n

Paid Arbitrum transaction simulation and risk scoring for wallets and AI agents.

21 installs/wk local only
Brain Scanner
by kevin-lozada-santos

Codebase graphs, caller impact analysis, and recorded project context for AI coding agents.

answering
CGIS Code Graph
by zaebee

Code graph for AI agents: impact analysis and call tracing for Python, TypeScript and Go.

1 369 installs/wk local only
pyscn
by ludo-technologies

Python code analysis for AI agents: complexity, dead code, clones, coupling, and a health score.

1 270 installs/wk local only
Verdoc
by verdochello

Deterministic AGENTS.md and repo analysis for coding agents, paid per call in USDC over x402.

local only
npm
by rog0x

npm package search, audit, bundle analysis for AI agents

28 installs/wk local only

CallFlow AI — questions

Answers built from our own checks of this server.

What can CallFlow AI do?
It exposes 2 tools, read directly from the server on our last check. Among them: analyze_sales_call, get_callflow_payment_info. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is CallFlow AI working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 46 of 92 checks got a reply (50.0%), average response time 364 ms. The bar chart above shows every period we have measured.
Is CallFlow AI still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists CallFlow AI as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect CallFlow AI?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does CallFlow AI need an API key?
No. CallFlow AI completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is CallFlow AI?
It answers our handshake in 364 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.