Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Paid Arbitrum transaction simulation and risk scoring for wallets and AI agents.
These three are never merged into one score: opinions, measurements and popularity are different things.
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.
CLIENT_PRIVATE_KEY, SERVER_URL, CHAIN_IDValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"arbitrum-transaction-preflight": {
"command": "npx",
"args": [
"-y",
"arbitrum-mpp-transaction-preflight"
],
"env": {
"CLIENT_PRIVATE_KEY": "your-value",
"SERVER_URL": "your-value",
"CHAIN_ID": "your-value"
}
}
}
}Run this in your terminal
claude mcp add arbitrum-transaction-preflight --env CLIENT_PRIVATE_KEY=your-value --env SERVER_URL=your-value --env CHAIN_ID=your-value -- npx -y arbitrum-mpp-transaction-preflightFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"arbitrum-transaction-preflight": {
"command": "npx",
"args": [
"-y",
"arbitrum-mpp-transaction-preflight"
],
"env": {
"CLIENT_PRIVATE_KEY": "your-value",
"SERVER_URL": "your-value",
"CHAIN_ID": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"arbitrum-transaction-preflight": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"arbitrum-mpp-transaction-preflight"
],
"env": {
"CLIENT_PRIVATE_KEY": "your-value",
"SERVER_URL": "your-value",
"CHAIN_ID": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
SERVER_URL envCHAIN_ID envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
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 8, 2026
The registry name was verified with the GitHub account naur9n, which owns the repo
We have not read this repo from GitHub yet
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
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 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: CLIENT_PRIVATE_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 –, and the latest version (4.0.0) reached the registry 4 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: Spec Driven Development, Remote Desktop Commander, Commonly
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
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.
Read Commonly pods and post as a Commonly agent you create, with a token from your Commonly account.
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.
Paid transaction simulation and risk reports for wallets, bots, and AI agents. Before a transaction is signed, the API checks whether it simulates successfully, estimates gas, detects token/NFT approvals, inspects the target, and returns a machine-readable risk score.
Production API: https://arbitrum-mpp-transaction-preflight-production.up.railway.app
42161)0xaf88d065e77c8cC2239327C5EDb3A432268e5831)0.10 USDC per report (100000 raw USDC units)The service never asks for a transaction-signing wallet. The example MPP/MCP clients use a separate low-value payer key only to authorize the API payment.
The hosted service exposes free discovery metadata:
GET / — product, network, price, and endpoint summaryGET /health — health checkGET /openapi.json — MPP-aware OpenAPI 3.1 discovery documentGET /llms.txt — concise instructions for AI agentsGET /.well-known/agent.json — agent/service metadataMPP clients call:
POST /v1/preflight
When x402 is enabled, x402 clients call:
POST /x402/v1/preflight
{
"from": "0x0000000000000000000000000000000000000001", "to": "0x0000000000000000000000000000000000000002", "data": "0x", "valueEth": "0" }
from and to are required. data defaults to 0x. Use either valueEth or valueWei for native value. A successful paid response contains:
approve and NFT setApprovalForAll detection;Automated simulation and heuristics reduce risk but are not a guarantee of safety.
Requirements: Node.js 22+ and a dedicated server wallet. On mainnet, the server wallet needs a small Arbitrum One ETH balance for MPP settlement gas.
npm install
cp .env.example .env npm run server
Minimum production configuration:
SERVER_PRIVATE_KEY=0x...
CHAIN_ID=42161 ARBITRUM_RPC=https://arb1.arbitrum.io/rpc PRICE_RAW_USDC=100000 ENABLE_FREE_DEMO=false SERVER_URL=https://arbitrum-mpp-transaction-preflight-production.up.railway.app
Never commit .env or expose SERVER_PRIVATE_KEY.
The included client performs the complete 402 -> authorization -> retry -> receipt flow:
CLIENT_PRIVATE_KEY=0x...
TARGET_ADDRESS=0x... SERVER_URL=https://arbitrum-mpp-transaction-preflight-production.up.railway.app CHAIN_ID=42161
npm run client
The payer needs native USDC on Arbitrum One. It does not need ETH for the MPP payment; the merchant settles the signed EIP-3009 authorization.
The MCP server exposes check_arbitrum_transaction. It uses the caller's dedicated CLIENT_PRIVATE_KEY to pay the hosted MPP API, so each tool call produces API revenue instead of bypassing payment.
npm run mcp
After the npm package is published, MCP hosts can run:
{
"mcpServers": { "arbitrum-preflight": { "command": "npx", "args": ["-y", "arbitrum-mpp-transaction-preflight"], "env": { "CLIENT_PRIVATE_KEY": "0x...", "SERVER_URL": "https://arbitrum-mpp-transaction-preflight-production.up.railway.app", "CHAIN_ID": "42161" } } } }
Use a dedicated low-value payer wallet. Never reuse a valuable wallet key.
Production x402 settlement on Arbitrum uses Coinbase's CDP facilitator. Create a CDP project and add these Railway variables:
ENABLE_X402=true
CDP_API_KEY_ID=... CDP_API_KEY_SECRET=...
The server then exposes POST /x402/v1/preflight with Bazaar discovery metadata. MPP remains available at POST /v1/preflight; the two payment channels share the same analysis engine and merchant address.
npm run typecheck
npm run build npm pack --dry-run
Set ENABLE_FREE_DEMO=true only for local development to expose POST /demo/preflight without payment. Never enable it in production.
The repository includes server.json and npm metadata for the official MCP Registry. Release order:
arbitrum-mpp-transaction-preflight to npm;server.json with mcp-publisher;Official Arbitrum MPP guide: https://docs.arbitrum.io/build-decentralized-apps/machine-payments-protocol