World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 102 tools.
Description from the maker (original English)
Smart Meta-Facilitator for x402 payments on Base: route, verify, and settle payments.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
Passed 1/2 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
You need a Nexflow Smf key (sign up on the maker’s site, may cost money) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
One time only; it works for every server that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. It may cost money.
How to get a key is in the maker’s README below
SettingsDeveloperEdit Config
{
"mcpServers": {
"nexflow-smf": {
"command": "npx",
"args": [
"-y",
"@nexflow-smf/smf"
],
"env": {
"NEXFLOW_API_KEY": "your-value",
"NEXFLOW_BASE_URL": "your-value"
}
}
}
}Paste the key only into the app’s field, never into a chat or to anyone
Use Nexflow Smf and tell me what you can do for me, then show me one thing✓ If Claude says it is using Nexflow Smf or shows a Nexflow Smf tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Nexflow Smf yet
Nexflow Smf runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Nexflow Smf
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
You need a Nexflow Smf key (sign up on the maker’s site, may cost money) · Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. It may cost money.
How to get a key is in the maker’s README below
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add nexflow-smf --env NEXFLOW_API_KEY=your-value --env NEXFLOW_BASE_URL=your-value -- npx -y @nexflow-smf/smfReplace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see Nexflow Smf listed as connected
Use Nexflow Smf and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Nexflow Smf or shows a Nexflow Smf tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a Nexflow Smf key (sign up on the maker’s site, may cost money) · Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. It may cost money.
How to get a key is in the maker’s README below
In the Nexflow Smf settings, NEXFLOW_API_KEY, NEXFLOW_BASE_URL is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Nexflow Smf and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Nexflow Smf or shows a Nexflow Smf tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a Nexflow Smf key (sign up on the maker’s site, may cost money) · Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. It may cost money.
How to get a key is in the maker’s README below
In the Nexflow Smf settings, NEXFLOW_API_KEY, NEXFLOW_BASE_URL is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Nexflow Smf and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Nexflow Smf or shows a Nexflow Smf tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add nexflow-smf --env NEXFLOW_API_KEY=your-value --env NEXFLOW_BASE_URL=your-value -- npx -y @nexflow-smf/smfClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"nexflow-smf": {
"command": "npx",
"args": [
"-y",
"@nexflow-smf/smf"
],
"env": {
"NEXFLOW_API_KEY": "your-value",
"NEXFLOW_BASE_URL": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"nexflow-smf": {
"command": "npx",
"args": [
"-y",
"@nexflow-smf/smf"
],
"env": {
"NEXFLOW_API_KEY": "your-value",
"NEXFLOW_BASE_URL": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"nexflow-smf": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@nexflow-smf/smf"
],
"env": {
"NEXFLOW_API_KEY": "your-value",
"NEXFLOW_BASE_URL": "your-value"
}
}
}
}NEXFLOW_API_KEY secret required envNEXFLOW_BASE_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 11, 2026
The registry name was verified with the GitHub account moejeaux, which owns the repo
Code last changed 8 months ago, more than 6 months ago
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 2 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: NEXFLOW_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 8 months ago, and the latest version (1.0.0) reached the registry 10 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: World Monitor, Claude Flow, Tldraw
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 102 tools.
AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
The x402-native metered billing and routing brain for AI agents and SaaS APIs on Base.
NexFlow SMF routes, verifies, and settles x402 micropayments on Base. It acts as an intelligent intermediary between payers and facilitators, selecting the optimal route based on cost, latency, and reliability. This repository contains the on-chain settlement contracts, TypeScript SDK, agent manifest specification, and integration examples.
Discover AI agent services with x402 payment routing through NexFlow SMF. Submit your service to the catalog.
| Component | Description |
|---|---|
contracts/ | Solidity contracts for atomic batch settlement with Merkle proof verification |
sdk/ | Zero-dependency TypeScript SDK (@nexflow-smf/smf) for routing, verification, and settlement |
examples/ | Ready-to-run examples demonstrating common integration patterns |
examples/workflows/ | JSON workflow definitions for the NexFlow SMF workflow host |
examples/client/ | Minimal TypeScript clients showing the 402 → pay → retry pattern |
Canonical list of NexFlow SMF skills. Each skill has a SKILL.md (for Cursor/agents) and lives in nexflow-smf-skills/. Machine-readable manifest: skills-manifest.json · API: GET https://api.nexflowapp.app/.well-known/skills (redirects to manifest).
| Skill | Description |
|---|---|
| List Facilitators | Discover active x402 facilitators by network/asset before quoting or paying. |
| Route Matrix | Compare priced routes (fees, latency) across facilitators for USDC on Base. |
| Route Quote | Get a single priced quote for a chosen facilitator before committing. |
| Settlement Receipt | Fetch a settlement receipt for a completed x402 payment for logs or audits. |
| Healthcheck | Ping NexFlow SMF for status and latency before routing payments. |
| Simulate Charge | See x402 pricing headers without performing a real payment. |
| Budget Plan | Turn a USDC budget into an approximate number of SMF API calls. |
Discover NexFlow services as AgentCards, ready for AI agents and x402-aware clients:
https://nexflow-agentcards.pages.dev/
Drop a Lambda@Edge function in front of CloudFront. Every request to a protected path must include a valid x402-payment header — otherwise the client gets a 402 Payment Required with payment instructions. No backend changes needed.
How it works:
/x402/verify with the payment proof (not billed). If valid, attaches a settlementIntentId and forwards to origin. If invalid, returns 402.settlementIntentId. If origin status < 400, calls /x402/settle to confirm delivery (this is the billable event). Returns the response unchanged.Get started in 15 minutes:
[AWS CloudFront + Lambda@Edge Quickstart →](./examples/aws-cloudfront-lambdaedge/README.md)
For server-side integrations where you control the request lifecycle — route payments, verify intents, and trigger batch settlement from your own code.
npm install @nexflow-smf/smf
import { NexFlowSMFClient } from '@nexflow-smf/smf';
const smf = new NexFlowSMFClient({ baseUrl: 'https://api.nexflowapp.app', apiKey: process.env.NEXFLOW_API_KEY!, });
// Route a payment const route = await smf.route({ amount_wei: '1000000', token_address: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913', chain_id: 'eip155:8453', payment_id: 'order-123', });
// Verify a payment intent const result = await smf.verify({ payment_intent: 'x402:1:base:0xabc...', recipient_address: '0xYourAddress...', });
[Full SDK documentation →](./sdk/README.md)
| Path | Description |
|---|---|
examples/aws-cloudfront-lambdaedge/ | 15-minute AWS quickstart — Lambda@Edge x402 pay-per-request gating |
examples/basic-settlement.ts | End-to-end SDK example: route, verify, settle |
sdk/ | Zero-dependency TypeScript SDK (@nexflow-smf/smf) |
contracts/ | Solidity contracts for atomic batch settlement with Merkle proofs |
docs/ | API reference, facilitator contract, production checklist |
AGENT_MANIFEST_V1.md | Agent Manifest spec for machine-to-machine discovery |
nexflow-smf-skills/ | Cursor-style agent skills (route-matrix, quote, receipt, facilitators, health, simulate, budget) |
PRICING.md | Pricing model with example scenarios |
| Service | Description | Status |
|---|---|---|
| Smart Meta-Facilitator | Intelligent payment routing, verification, and batch settlement | Live |
| CloudFront Edge Gating | Lambda@Edge adapter for pay-per-request access via CloudFront | Live |
| Agent Manifest & Discovery | Machine-readable capability manifest for AI agent integration | Live |
| Pulse Scheduler | Metered job scheduling with x402 billing (cron, webhooks, tasks) | Live |
| Action Catalog | Pre-built metered actions (Shopify, Salesforce, data enrichment) | Live |
| Contract | Address | Explorer |
|---|---|---|
| AtomicBatchSettlement | 0x43A04228152115fDd5663B2Aa559Ebd84D17A49D | BaseScan |
| USDC | 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 | BaseScan |
NexFlow SMF allows agents to define, publish, and monetize hosted workflows — multi-step compositions of core SMF operations that other agents can invoke via the 402/MPP payment gateway.
Workflows can compose any of these paid SMF operations:
| Operation | Description |
|---|---|
create_session | Create a metered session with a budget |
budget_check | Check planned charges against budgets |
budget_diagnostics | Analyze sessions for overrun risk |
process_charges | Deduct charges from a session or caller |
verify_payment | Validate a payment descriptor |
settle_batch | Settle a batch of transactions |
revenue_share | Record revenue-share accounting for a period |
route_quote | Get a payment routing quote |
usage_timeseries | Time-series spend data for a caller/session |
configure_alerts | Set budget/usage alert thresholds |
monitor_sessions | List sessions with budget & spend status |
monitor_alerts | Return triggered budget/usage alerts |
pricing_estimate | Estimate cost of a set of operations |
examples/workflows/safety_capped_session_runner.json
A 5-step workflow that:
examples/workflows/usage_health_check.json
A 3-step diagnostic workflow that:
examples/workflows/revenue_share_settlement.json
A 5-step workflow demonstrating the full payment lifecycle:
The workflow creator earns their standard rev-share (set via creatorShareBps) on every invocation. Rev-share credits accumulate per wallet and are batched for payout when they reach $5+.
Input example:
{
"sessionBudget": { "amount": 2000000, "currency": "USDC" }, "charges": [ { "callerId": "agent_a", "amount": 500000, "description": "API usage week 12" }, { "callerId": "agent_b", "amount": 300000, "description": "Compute usage week 12" } ], "settlementPeriod": "2026-03-01/2026-03-31" }
# Register the Safety-Capped Session Runner
curl -X POST "$NEXFLOW_SMF_BASE_URL/nexflow/workflows" \ -H "Content-Type: application/json" \ -H "X-Caller-Id: demo_caller" \ --data-binary "@examples/workflows/safety_capped_session_runner.json"
Response:
{
"workflowId": "wf_abc123_1", "name": "Safety-Capped Session Runner", "invokeUrl": "/nexflow/workflows/wf_abc123_1/invoke", "status": "active", "steps": 5, "pricing": { "billingMode": "per_call", "markupBps": 300 } }
# First call — no payment proof → 402 Payment Required
curl -X POST "$NEXFLOW_SMF_BASE_URL/nexflow/workflows/wf_abc123_1/invoke" \ -H "Content-Type: application/json" \ -H "X-Caller-Id: demo_caller" \ --data '{ "requestedBudget": { "amount": 500000, "currency": "USDC" }, "plannedCost": { "amount": 50000, "currency": "USDC" } }'
The first call returns HTTP 402 with a payment challenge:
{
"object": "payment_challenge", "operation": "workflow_invoke", "workflow_id": "wf_abc123_1", "required_amount": 17350, "currency": "usdc", "price_breakdown": { "totalPrice": 17350, "baseCost": 7000, "markup": 210, "platformFee": 149 }, "instructions": "Pay via MPP using the challenge above, then retry with X-PAYMENT-PROOF header." }
After the agent pays (via Tempo MPP or x402), it retries with the proof:
# Second call — with valid proof → 200 OK
curl -X POST "$NEXFLOW_SMF_BASE_URL/nexflow/workflows/wf_abc123_1/invoke" \ -H "Content-Type: application/json" \ -H "X-Caller-Id: demo_caller" \ -H "X-PAYMENT-PROOF: " \ --data '{ "requestedBudget": { "amount": 500000, "currency": "USDC" }, "plannedCost": { "amount": 50000, "currency": "USDC" } }'
See examples/client/invokeUsageHealthCheck.ts for a runnable demo of the full 402 → proof → retry flow.
export NEXFLOW_SMF_BASE_URL=http://localhost:3001
export WORKFLOW_ID=wf_abc123_1 npx tsx examples/client/invokeUsageHealthCheck.ts
| Variable | Required | Description |
|---|---|---|
NEXFLOW_API_KEY | Yes | Your NexFlow API key (nf_live_xxx or nf_test_xxx) |
NEXFLOW_BASE_URL | No | Override API URL (default: https://api.nexflowapp.app) |
NEXFLOW_SMF_BASE_URL | No | NexFlow SMF bridge URL for workflow invocations (default: http://localhost:3001) |
WORKFLOW_ID | No | Workflow ID for the client example scripts |
Sign up or log in at [nexflowapp.app](https://n