Flow — Base quotes & contract safety for agents
REMOTE · FLOW-KG4X.VERCEL.APP
Best-execution quotes and contract safety checks on Base for AI agents, paid per call via x402.
Available components
Last scanned (3 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 707 tokens (~176/item across 4 items; 4 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 Management80
- Stability observed for 24 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 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.
- 1 Nov 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.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
- Tool “flow_paycheck” rewrote its description, which is the text the model reads security
- Schema quality: 204 → 176 ▲ functional
- “flow_paycheck” dropped the optional parameter “amountUsd” cosmetic
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 5 Nov 2026 · Probed https://flow-kg4x.vercel.app/api/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 | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 9c5f0e6a35c955e113044c86848e4cd5 |
| 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 flow-kg4x.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 |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://flow-kg4x.vercel.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://flow-kg4x.vercel.app/api/mcp | HTTPS enforced | 308 | https://flow-kg4x.vercel.app/api/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 →
flow_health ~25
Check the Flow quote API health: status, chain, and latest synced block number.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
flow_paycheck ~239
Before you pay this agent, check. PayCheck ($0.50 USDC via x402 on Base) runs Flow's whole checker stack on a payee in ONE call — the payee verdict (kind, on-chain activity, the full contract-safety engine when the payee is a contract), the wallet approval-exposure audit, contract safety, and the payee's recent USDC settlement history — and returns one finished grade (ALLOW / REVIEW / BLOCK with a 0-100 score), a verify_status (verified / failed / unverified_verifier_down), every check, the evidence under it, and a receipt. The guarantee: the report is produced before settlement; if it cannot be produced, the payment is never settled — no report, no charge. This hosted endpoint does not hold a wallet: an unpaid call returns the endpoint's x402 payment challenge itself, never an invented result. Pay it with any x402 client, or use the @flowexecutor/flow-mcp stdio package with an Early Builder Key.
| Name | Type | Req | Description |
|---|---|---|---|
| payee | string | yes | The payee address to grade before paying (0x…), Base |
No output schema declared.
No examples provided.
flow_quote ~216
Get a best-execution swap quote on Base. Compares Uniswap V3, PancakeSwap V3 and Aerodrome (plus two-hop routes via WETH), returns the winning venue, expected output, edge in bps vs the baseline, a liquidity flag (deep/watch/thin), the exact block number and timestamp, and build latency. Read-only: no funds move.
| Name | Type | Req | Description |
|---|---|---|---|
| amountIn | string | yes | Human-readable input amount, e.g. "10" for 10 USDC |
| chainId | number | – | Chain id, defaults to 8453 (Base) |
| tokenIn | string | yes | Input token contract address on Base (e.g. USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA4E46E) |
| tokenOut | string | yes | Output token contract address on Base (e.g. WETH 0x4200000000000000000000000000000000000006) |
No output schema declared.
No examples provided.
flow_search ~227
Verified Search ($0.01 USDC via x402 on Base): web search where every result is independently checked by Flow before it reaches you — the result URL is fetched live (liveness, final HTTP status recorded) and the fetched page text is matched against the result's own title/snippet terms (content-match score). Each result carries a verify_status (verified / failed / unverified_verifier_down), its httpStatus and contentMatch, and the response carries a receipt counting checked / verified / failed. Bad results are flagged, never silently dropped. The guarantee: the search is produced before settlement; if it cannot be produced, the payment is never settled. This hosted endpoint does not hold a wallet: an unpaid call returns the endpoint's x402 payment challenge itself, never an invented result. Pay it with any x402 client, or use the @flowexecutor/flow-mcp stdio package with an Early Builder Key.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | number | – | Max results to return and verify (default 5, cap 10) |
| query | string | yes | The search query |
No output schema declared.
No examples provided.
How do I install the Flow — Base quotes & contract safety for agents MCP server?
Flow — Base quotes & contract safety for agents is a hosted endpoint at https://flow-kg4x.vercel.app/api/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 · flow-kg4x.vercel.app
claude mcp add --transport http flow-executor-flow 'https://flow-kg4x.vercel.app/api/mcp'
What is the Flow — Base quotes & contract safety for agents MCP server?
Flow — Base quotes & contract safety for agents is an MCP server listed in the public MCP registry as io.github.flow-executor/flow. Best-execution quotes and contract safety checks on Base for AI agents, paid per call via x402. This page covers its hosted endpoint (https://flow-kg4x.vercel.app/api/mcp).
Is the Flow — Base quotes & contract safety for agents MCP server safe to use?
Flow — Base quotes & contract safety for agents scores 77 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 Flow — Base quotes & contract safety for agents MCP server expose?
Flow — Base quotes & contract safety for agents exposes 4 tools: flow_quote, flow_paycheck, flow_search, flow_health. Their descriptions and schemas cost roughly 707 tokens of context every time the server is loaded.
Does the Flow — Base quotes & contract safety for agents MCP server require authentication?
No. We connected to Flow — Base quotes & contract safety for agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Flow — Base quotes & contract safety for agents MCP server still maintained?
Flow — Base quotes & contract safety for agents is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.