Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Runtime authorization for AI agents and smart contracts via an immutable on-chain policy registry
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.
SMARTPOLICY_REGISTRY, SMARTPOLICY_VERIFIER, SMARTPOLICY_RPC_URL, SMARTPOLICY_ISSUER_KEYValues 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": {
"smartpolicy": {
"command": "npx",
"args": [
"-y",
"@smartpolicy/mcp"
],
"env": {
"SMARTPOLICY_REGISTRY": "your-value",
"SMARTPOLICY_VERIFIER": "your-value",
"SMARTPOLICY_RPC_URL": "your-value",
"SMARTPOLICY_ISSUER_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add smartpolicy --env SMARTPOLICY_REGISTRY=your-value --env SMARTPOLICY_VERIFIER=your-value --env SMARTPOLICY_RPC_URL=your-value --env SMARTPOLICY_ISSUER_KEY=your-value -- npx -y @smartpolicy/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"smartpolicy": {
"command": "npx",
"args": [
"-y",
"@smartpolicy/mcp"
],
"env": {
"SMARTPOLICY_REGISTRY": "your-value",
"SMARTPOLICY_VERIFIER": "your-value",
"SMARTPOLICY_RPC_URL": "your-value",
"SMARTPOLICY_ISSUER_KEY": "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": {
"smartpolicy": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@smartpolicy/mcp"
],
"env": {
"SMARTPOLICY_REGISTRY": "your-value",
"SMARTPOLICY_VERIFIER": "your-value",
"SMARTPOLICY_RPC_URL": "your-value",
"SMARTPOLICY_ISSUER_KEY": "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.
SMARTPOLICY_REGISTRY envSMARTPOLICY_VERIFIER envSMARTPOLICY_RPC_URL 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 6, 2026
The registry name was verified with the GitHub account smartpolicy-protocol, 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: SMARTPOLICY_ISSUER_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 (0.2.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, Binggio
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.
Governed answers from your data: approved meanings only, refusals instead of guesses.
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.
Runtime authorization for AI agents and smart contracts.
Define what an agent, a user, or a contract is allowed to do — once, as a policy. Enforce it everywhere: on-chain via a minimal verifier, off-chain via an MCP server and REST API that AI systems consume directly. Update the rules without redeploying anything.
Status (2026-06-12): core contracts live on Ethereum Sepolia
(Etherscan-verified, addresses in contracts/deployments/sepolia.json); 54
Foundry tests green; MCP server v0 packaged —
npx smartpolicy-mcpruns
zero-config against Sepolia,
npx smartpolicy-mcp deploybootstraps any
chain from embedded bytecode; AI-consumability proven by unaided
fresh-agent execution tests (incl. cold start on an empty chain). NOT
audited; internal until mature — no public repo or registry listings yet.
Current state, decisions, and how to resume work: PLAN.md.
Every team shipping AI agents hits the same wall: the agent can technically do anything its keys allow, and the only ways to constrain it are hardcoded prompts or redeployed code. Every smart contract team hits the mirror image: access rules baked into the contract at deploy time.
SmartPolicy separates the rule from the enforcement point:
0xAgent perform action under policy N?"* and receives a short-lived signed grant (EIP-712) that any contract or backend can verify.┌─────────────┐ MCP / REST (x402 metered) ┌──────────────────┐
│ AI agents │ ────────────────────────────▶ │ SmartPolicy MCP │ │ & services │ ◀──── signed grants ──────── │ server (TS) │ └─────────────┘ └────────┬─────────┘ │ reads + grant issuance ┌─────────────┐ inherit Gate modifier ┌────────▼─────────┐ │ Protected │ ────── view calls ──────────▶ │ PolicyRegistry │ │ contracts │ │ (Base, immutable)│ └─────────────┘ └──────────────────┘
See ARCHITECTURE.md for the full design and the rationale for every decision (chain, fees, trust model, what was deliberately dropped from v1).
contracts/ Solidity core: PolicyRegistry, PolicyGate, interfaces (Foundry)
mcp/ MCP server + REST API (TypeScript, x402 metering) sdk/ TypeScript client SDK (@smartpolicy/sdk) — reads, grants, tx-building docs/ Integration guides (planned)
SmartPolicy is a clean rewrite of the strongest ideas from a 2025 prototype ("Smart Policy Protocol", Sepolia): the policy registry, the tiered integration model, and hybrid on-chain + signed-token enforcement. The rewrite deliberately drops the SPOL token/ICO/governance suite, the sports-prediction oracle, the factory contracts, and the upgradeable-proxy trust model, and fixes the known security issues (tx.origin checks, missing reentrancy guards, header-only API auth).
Apache-2.0 — see LICENSE.