KlearFlow Relay
REMOTE · KLEARFLOW.VERCEL.APP · SCANNED OCT 15
Machine-paid revenue intelligence, recovery decisions, and x402 routing for AI agents.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 720 tokens (~240/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the KlearFlow Relay MCP server?
KlearFlow Relay is a hosted endpoint at https://klearflow.vercel.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · klearflow.vercel.app
claude mcp add --transport http erickmckee-klearflow-relay 'https://klearflow.vercel.app/mcp'
{
"mcpServers": {
"erickmckee-klearflow-relay": {
"url": "https://klearflow.vercel.app/mcp"
}
}
} {
"servers": {
"erickmckee-klearflow-relay": {
"type": "http",
"url": "https://klearflow.vercel.app/mcp"
}
}
} [mcp_servers.erickmckee-klearflow-relay] url = "https://klearflow.vercel.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"erickmckee-klearflow-relay": {
"type": "remote",
"url": "https://klearflow.vercel.app/mcp",
"enabled": true
}
}
} openclaw mcp add erickmckee-klearflow-relay --url 'https://klearflow.vercel.app/mcp' --transport streamable-http
mcp_servers:
erickmckee-klearflow-relay:
url: "https://klearflow.vercel.app/mcp" {
"McpServers": {
"erickmckee-klearflow-relay": {
"Transport": "http",
"Url": "https://klearflow.vercel.app/mcp"
}
}
} assistant mcp add erickmckee-klearflow-relay -t streamable-http -u 'https://klearflow.vercel.app/mcp'
{
"mcpServers": {
"erickmckee-klearflow-relay": {
"type": "http",
"url": "https://klearflow.vercel.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +4
- Schema quality: 196 → 240 ▼ functional
- Tool coverage: 65% → 100% ▲ functional
- Tool “inspect_revenue_opportunity” now declares an output schema ▲ functional
- Tool “recover_revenue” now declares an output schema ▲ functional
- Tool “route_task” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Server version: 0.3.1 → 0.3.2 functional
- “inspect_revenue_opportunity” reworded the description of “followUpMethod” cosmetic
- “inspect_revenue_opportunity” reworded the description of “interestLevel” cosmetic
- “recover_revenue” reworded the description of “businessName” cosmetic
- “recover_revenue” reworded the description of “customerFirstName” cosmetic
- “recover_revenue” reworded the description of “eventType” cosmetic
- “recover_revenue” reworded the description of “industry” cosmetic
- “recover_revenue” reworded the description of “preferredChannel” cosmetic
- “route_task” reworded the description of “excludeHosts” cosmetic
- 7 Oct 26 +10
- Authorization: unverified → partial ▲ security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 65% ▲ functional
- Schema quality: fair → good functional
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 146 → 124 ▲ functional
- New tool “route_task” functional
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 15 Oct 2026 · Probed https://klearflow.vercel.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | f7911168ffa7d0f4135e24792e7a52a8 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of klearflow.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://klearflow.vercel.app/mcp | Verified | 200 | |
| http (plaintext) | http://klearflow.vercel.app/mcp | HTTPS enforced | 308 | https://klearflow.vercel.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
inspect_revenue_opportunity Inspect Revenue Opportunity ~245
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.
| Name | Type | Req | Description |
|---|---|---|---|
| averageJobValue | number | – | Average revenue in USD from one won job or customer opportunity. |
| businessName | string | – | Optional business name used only to label the result. |
| estimatedRecoveryRate | number | – | Expected fraction of leaked opportunities that can be recovered, from 0 to 1. Omit to use the model default. |
| followUpMethod | string | yes | Current follow-up process for missed opportunities: none, manual human follow-up, email, or text/SMS. |
| industry | string | yes | Business industry or service category, for example HVAC, roofing, plumbing, legal, or dental. |
| interestLevel | string | – | Optional buying/response urgency used to calibrate the recommended commercial action. |
| missedCallsPerWeek | number | yes | Estimated inbound calls missed per week. Use 0 when none are missed. |
| zipCode | string | – | Optional postal code used as business-market context. |
| Name | Type | Req | Description |
|---|---|---|---|
| payment | object | yes | – |
| priceUsd | number | yes | USDC-denominated execution price settled through x402. |
| proofId | string | yes | Unique KlearFlow proof identifier for this settled paid execution. |
| result | object | yes | Inspection result containing the leakage score, modeled monthly leak, recoverable revenue estimate, and recommended next action. |
No examples provided.
recover_revenue Recover Revenue ~260
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.
| Name | Type | Req | Description |
|---|---|---|---|
| averageOpportunityValue | number | – | Estimated gross value in USD of the customer opportunity. |
| bookingUrl | string | – | Optional booking URL to include in a recommended recovery message. |
| businessName | string | – | Optional business name used to label the recovery packet. |
| customerFirstName | string | – | Optional customer first name used only when composing the recommended action text. |
| eventType | string | yes | Specific revenue-loss event to recover: missed call, stale lead, unanswered quote, appointment no-show, or failed payment. |
| industry | string | – | Optional business industry or service category used to tailor the recovery action. |
| minutesSinceEvent | number | yes | Minutes elapsed since the revenue-loss event occurred. |
| paymentUrl | string | – | Optional secure payment-retry URL for payment_failed events. |
| preferredChannel | string | – | Preferred recovery channel. Use auto to let KlearFlow select among SMS, email, or a human phone task. |
| priorAttempts | integer | – | Number of prior recovery outreach attempts already made. |
| Name | Type | Req | Description |
|---|---|---|---|
| payment | object | yes | – |
| priceUsd | number | yes | USDC-denominated execution price settled through x402. |
| proofId | string | yes | Unique KlearFlow proof identifier for this settled paid execution. |
| result | object | yes | Recovery decision packet containing priority, recommended action, fallbacks, stop conditions, modeled economics, and safety boundaries. |
No examples provided.
route_task Route Task ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| excludeHosts | array | – | Optional provider hostnames to exclude from the ranked result, useful to avoid self-routing or previously rejected providers. |
| limit | integer | – | Maximum number of ranked provider candidates to return. |
| maxPriceUsd | number | – | Optional maximum listed provider price in USD. |
| preferPaidVerified | boolean | – | When true, rank providers with independent paid-verification evidence higher. |
| task | string | yes | Plain-English capability the caller wants a live x402 provider to perform. |
| Name | Type | Req | Description |
|---|---|---|---|
| payment | object | yes | – |
| priceUsd | number | yes | USDC-denominated execution price settled through x402. |
| proofId | string | yes | Unique KlearFlow proof identifier for this settled paid execution. |
| result | object | yes | Routing result containing the ranked live x402 provider candidates and the selected recommendation; no downstream provider is executed. |
No examples provided.
What is the KlearFlow Relay MCP server?
KlearFlow Relay is an MCP server listed in the public MCP registry as io.github.erickmckee/klearflow-relay. Machine-paid revenue intelligence, recovery decisions, and x402 routing for AI agents. This page covers its hosted endpoint (https://klearflow.vercel.app/mcp).
Is the KlearFlow Relay MCP server safe to use?
KlearFlow Relay scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the KlearFlow Relay MCP server expose?
KlearFlow Relay exposes 3 tools: inspect_revenue_opportunity, route_task, recover_revenue. Their descriptions and schemas cost roughly 658 tokens of context every time the server is loaded.
Does the KlearFlow Relay MCP server require authentication?
No. We connected to KlearFlow Relay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the KlearFlow Relay MCP server still maintained?
KlearFlow Relay is still listed as active in the MCP registry. We last reached this channel on 15 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.