Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Governed USDC wallet for AI agents — policy gates, spending caps, and Ed25519-signed receipts.
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.
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": {
"agent-wallet": {
"command": "npx",
"args": [
"-y",
"dingdawg-agent-wallet"
]
}
}
}Run this in your terminal
claude mcp add agent-wallet -- npx -y dingdawg-agent-walletPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agent-wallet": {
"command": "npx",
"args": [
"-y",
"dingdawg-agent-wallet"
]
}
}
}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": {
"agent-wallet": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"dingdawg-agent-wallet"
]
}
}
}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.
These 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 7, 2026
The registry name was verified with the GitHub account dingdawg, 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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 (1.0.6) reached the registry 5 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, Starreel
Servers in the same category from other makers, sorted by stars.
Reading a card:★ 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.
Turn a script into a finished, downloadable short-drama episode — via MCP or REST.
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.
Shows governed agent wallet enforcement in action: allow, deny, step-up, allowlist — all in 5 seconds. No API keys. No blockchain required.
▶ provision_wallet
wallet_id: demo-wallet-abc123 daily_cap: $200 USDC per_call_cap: $100 USDC
▶ governed_spend — $25 USDC (allowed) ✓ AUTHORIZED receipt_id: 6aba84a6-... daily_remaining: $175 USDC next_step: wallet.sendToken({ assetId: "usdc", amount: "25", destination: "0xVendorABC123" })
▶ governed_spend — $150 USDC (exceeds per-call cap) ✗ DENIED reason: Amount 150 USDC exceeds per-call cap 100 USDC receipt_id: cd7a7aa8-... (denial is logged too)
▶ governed_spend — $75 USDC (step-up required) ⚠ STEP-UP REQUIRED reason: Amount 75 USDC > step-up threshold 50 USDC — MFA required fix: Pass approval_token from your authorization flow
▶ governed_spend — unknown recipient (not in allowlist) ✗ DENIED reason: Recipient 0xUnknownAddress not in allowlist
▶ wallet_audit chain_verified: true ✓ total_receipts: 5 [17:02:18] DENY $10 USDC governed_spend [17:02:18] DENY $75 USDC governed_spend [17:02:18] DENY $150 USDC governed_spend [17:02:18] ALLOW $25 USDC governed_spend [17:02:18] ALLOW provision_wallet
Every action — allow AND deny — produces an immutable receipt. chain_verified: true means the full chain is tamper-evident — any modification is detectable.
git clone https://github.com/DingDawg/agent-wallet-demo
cd agent-wallet-demo npm install node demo.mjs
dingdawg-agent-wallet — 5 MCP tools that wrap any agent wallet with policy enforcement and an immutable audit trail.
npm install dingdawg-agent-wallet
| Tool | What it does |
|---|---|
provision_wallet | Create wallet with spend policy (daily cap, per-call cap, allowlist) |
governed_spend | Policy check → authorize → immutable receipt |
governed_receive | Accept payment with tamper-evident receipt |
wallet_policy | Update limits and allowlists at runtime |
wallet_audit | Full receipt chain — chain_verified: true |
Coinbase AgentKit gives your agent a wallet. DingDawg gives it a conscience.
AI agents can now hold USDC and spend autonomously. The infrastructure exists. What doesn't: who enforces what the agent is allowed to spend, on what, for whom — and proves it happened correctly.
governed_spend authorizes then returns the exact agentkit_call SDK method to execute on-chainchain_verified: true means the audit trail is tamper-evident — any modification is detectable