Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者による説明(英語の原文)
Smart Meta-Facilitator for x402 payments on Base: route, verify, and settle payments.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
NEXFLOW_API_KEY, NEXFLOW_BASE_URL「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
Claude Desktop → Settings → Developer → Edit Config を開き、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"
}
}
}
}ターミナルでこれを実行します
claude mcp add nexflow-smf --env NEXFLOW_API_KEY=your-value --env NEXFLOW_BASE_URL=your-value -- npx -y @nexflow-smf/smf動かす前に、空欄の値を入力してください。
プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"nexflow-smf": {
"command": "npx",
"args": [
"-y",
"@nexflow-smf/smf"
],
"env": {
"NEXFLOW_API_KEY": "your-value",
"NEXFLOW_BASE_URL": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/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"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
NEXFLOW_BASE_URL envこの設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月8日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント moejeaux で確認済みです
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
入力が必要なもの:NEXFLOW_API_KEY
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(1.0.0)がレジストリに届いたのは10 か月前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにNode.jsも必要です。
同じカテゴリには:Spec Driven Development, Remote Desktop Commander, alalanet — check before you pay
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Check packages, MCP servers and x402 endpoints before agents install or pay. Signed.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
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
冒頭だけを表示しています。続きはリポジトリで読めます