Nexflow Smf runs on your own machine — the client starts it, so there is no endpoint to ping. 37 installs a week from npm. Last commit 20 Mar 2026.
Smart Meta-Facilitator for x402 payments on Base: route, verify, and settle payments.
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
пакет @nexflow-smf/smf ссылается на moejeaux/nexflow-smf-public
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add nexflow-smf -e 'NEXFLOW_API_KEY=<NEXFLOW_API_KEY>' -- npx -y @nexflow-smf/smf
{
"mcpServers": {
"nexflow-smf": {
"command": "npx",
"args": [
"-y",
"@nexflow-smf/smf"
],
"env": {
"NEXFLOW_API_KEY": "<NEXFLOW_API_KEY>"
}
}
}
}
[mcp_servers.nexflow-smf]
command = "npx"
args = ["-y", "@nexflow-smf/smf"]
env = { NEXFLOW_API_KEY = "<NEXFLOW_API_KEY>" }
{
"mcpServers": {
"nexflow-smf": {
"command": "npx",
"args": [
"-y",
"@nexflow-smf/smf"
],
"env": {
"NEXFLOW_API_KEY": "<NEXFLOW_API_KEY>"
}
}
}
}
{
"servers": {
"nexflow-smf": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@nexflow-smf/smf"
],
"env": {
"NEXFLOW_API_KEY": "<NEXFLOW_API_KEY>"
}
}
}
}
Put your own value in place of
<NEXFLOW_API_KEY> (NexFlow API key (format: nf_live_* or nf_test_*)).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
NEXFLOW_BASE_URL (API base URL (default: https://api.nexflowapp.app)).
Check supported assets and verify x402 payments on Celo
Verify and settle x402 stablecoin payments; browse the PayAI Bazaar of x402-payable resources.
x402 payment wrapper for AI Agents and MCP Servers. USDC settlements on Base L2.
Verify signed x402 payments; treasury-scoped settlement is irreversible.
Put any API behind x402 in one call, settle USDC on Base, buy credits, find paid resources
Smart contract security for AI agents — verify, monitor, freeze, x402 payments
Read-only Base mainnet reader. Verifies x402 payment settlements + AFTA federation status.
Pre-payment merchant trust checks for x402 agents on Base and Solana.
Answers built from our own checks of this server.