get_callflow_payment_info
Get CallFlow payment info
Returns the CallFlow paid sales-call API URL, price, network and x402 payment protocol without charging.
Takes no parameters.

io.github.sarvin-techPublished by GitHub account sarvin-techv1.0.0Updated Oct 28, 2026
Paid sales-call scoring and CRM next-step analysis for AI agents.
Remote MCP server that scores sales-call transcripts and suggests CRM next steps, charging per analysis through the x402 payment protocol.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.sarvin-tech%2Fcallflow-ai/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"callflow-ai": {
"type": "http",
"url": "https://callflow-ai-nine.vercel.app/mcp"
}
}
}This repository has no README.
Get CallFlow payment info
Returns the CallFlow paid sales-call API URL, price, network and x402 payment protocol without charging.
Takes no parameters.
Analyze a sales call with CallFlow
Paid sales-call transcript analysis. Without paymentSignature it returns the x402 payment challenge. Retry with a valid PAYMENT-SIGNATURE for the analysis.
reptitlecompanyprospecttranscriptrequiredpaymentSignature75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
Declare a license in the repository or the registry entry.