KlearFlow Relay

io.github.erickmckeePublished by GitHub account erickmckeev1.0.2Updated Oct 27, 2026

Machine-paid revenue intelligence, recovery decisions, and x402 routing for AI agents.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint that scores a business's missed-call and follow-up revenue leakage, returns recovery decisions, and ranks x402 providers for a task.

What you can do
  • Score a business for recoverable missed-call or follow-up revenue leakage, with estimated monthly leak, recoverable revenue and a next action
  • Get a prioritized recovery decision packet after a specific revenue-loss event
  • Discover and rank live x402 providers for a task before choosing downstream spend
When to use it
Useful when an assistant is evaluating whether a business is losing revenue to missed calls or follow-ups, or needs a next recovery step after a known loss event. Also relevant for comparing x402 providers before committing spend on a task.
Requirements
Remote streamable HTTP endpoint; no packages, environment variables or headers declared. Each tool call is paid in USDC on Base via x402, so the calling agent needs a funded wallet and x402 payment capability.
Before you install
Every tool costs money per execution: $0.005 for inspect_revenue_opportunity and route_task, $0.05 for recover_revenue, charged in USDC on Base through x402. Routing only ranks providers and does not execute the selected one, and recovery returns a decision packet without sending any external message. No authentication is declared, so payment is the access control.

Installation

In SourceWeft

  1. Open KlearFlow Relay in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

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.erickmckee%2Fklearflow-relay/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "klearflow-relay": {
      "type": "http",
      "url": "https://klearflow.vercel.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

3

inspect_revenue_opportunity

Inspect Revenue Opportunity

Use this first when deciding whether a business has recoverable missed-call or follow-up revenue leakage. Returns a score, estimated monthly leak, recoverable revenue, and next action. Execution costs $0.005 via x402 Base USDC.

ParameterszipCodeindustryrequiredbusinessNameinterestLevelfollowUpMethodrequiredaverageJobValuemissedCallsPerWeekrequiredestimatedRecoveryRate

route_task

Route Task

Use this when the caller needs to discover and rank live x402 providers for a task before choosing downstream spend. KlearFlow does not execute the selected provider. Routing costs $0.005 via x402 Base USDC.

ParameterstaskrequiredlimitmaxPriceUsdexcludeHostspreferPaidVerified

recover_revenue

Recover Revenue

Use this after a specific revenue-loss event already happened and the caller needs the next recovery action. Returns a prioritized decision packet; KlearFlow sends no external message. Execution costs $0.05 via x402 Base USDC.

ParametersindustryeventTyperequiredbookingUrlpaymentUrlbusinessNamepriorAttemptspreferredChannelcustomerFirstNameminutesSinceEventrequiredaverageOpportunityValue

Version history

4
  1. v1.0.2LatestOct 9, 2026
  2. v0.3.1Sep 24, 2026
  3. v0.3.0Sep 23, 2026
  4. v0.2.1Sep 23, 2026

Score

75% 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.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.