Skip to content
Official MCP RegistryListed

KlearFlow Relay

Part ofKlearFlow RelayMCP server

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

First seen 2 Oct 2026. Evidence as of 9 Oct 2026.

3
Tools
From an anonymous probe
1
Source listings
Each with its own history
11
Recorded changes
Since first seen

Tools

ToolDescriptionBehaviour
inspect_revenue_opportunityUse 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.Read-only
recover_revenueUse 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.Read-only
route_taskUse 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.Read-only

Change history

  1. Description changed (registry)
  2. route_task: input schema changed
  3. route_task: description changed (+"Use this when the caller needs to discover and rank" +"before choosing" +"KlearFlow does not execute the selected provider. Routing")
  4. route_task: annotations changed
  5. recover_revenue: input schema changed
  6. recover_revenue: description changed (+"Use this after" +"specific revenue-loss event already happened and the caller needs the next recovery action. Returns" +"packet; KlearFlow sends no")
  7. recover_revenue: annotations changed
  8. inspect_revenue_opportunity: input schema changed
  9. inspect_revenue_opportunity: description changed (+"Use this first when deciding whether" +"has recoverable" +"or follow-up")
  10. inspect_revenue_opportunity: annotations changed
  11. server instructions changed (+"Start with inspect_revenue_opportunity to quantify leakage, use recover_revenue after a specific loss event, and use route_task to rank external x402 providers." +"USDC; current prices are exposed by /api/pricing." -"revenue-intelligence, recovery, and Track C routing")
Source listings
SourceListingFirst seenLast seenVersions
Official MCP Registryio.github.erickmckee/klearflow-relay2 Oct 20269 Oct 20262