Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Kill switch + spend guard for AI agents that spend money, across every wallet vendor at once.
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.
COUNTERSIGN_URL, COUNTERSIGN_API_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": {
"countersign": {
"command": "npx",
"args": [
"-y",
"@countersign/mcp"
],
"env": {
"COUNTERSIGN_URL": "your-value",
"COUNTERSIGN_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add countersign --env COUNTERSIGN_URL=your-value --env COUNTERSIGN_API_KEY=your-value -- npx -y @countersign/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"countersign": {
"command": "npx",
"args": [
"-y",
"@countersign/mcp"
],
"env": {
"COUNTERSIGN_URL": "your-value",
"COUNTERSIGN_API_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": {
"countersign": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@countersign/mcp"
],
"env": {
"COUNTERSIGN_URL": "your-value",
"COUNTERSIGN_API_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.
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 6, 2026
The registry name was verified with the GitHub account countersign-network, 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: COUNTERSIGN_URL, COUNTERSIGN_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 –, and the latest version (0.2.2) reached the registry 2 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, Dechonet MCP
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.
30 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.
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 cross-vendor kill switch + spend guard for AI agents — as MCP tools, inside any MCP client.
Countersign is a neutral control plane that holds one policy, one freeze, and one tamper-evident audit ledger across every agent-wallet backend at once. This package exposes it as Model Context Protocol tools, so an agent (or you, from chat in Claude / Cursor) can ask *"may I spend this?"* before acting — and freeze everything in under a second.
| Tool | What it does |
|---|---|
countersign_request_spend | Pre-flight guard — ask whether a spend is allowed *before* touching the wallet (allow / deny / needs_approval). |
countersign_freeze | The kill switch — freeze every agent on every backend at once. |
countersign_apply_policy | Apply one unified policy (caps, allow/deny lists, approval threshold) across all backends. |
countersign_list_agents / countersign_health | See the governed fleet + control-plane health. |
countersign_list_approvals / countersign_approve / countersign_deny | The human-approval queue. |
countersign_ledger | Read + re-verify the append-only, hash-chained audit ledger. |
countersign_unfreeze | Lift a freeze (recover). |
It governs a running Countersign Core. The hosted Core at app.countersign.network is paused since 2026-09-18 and answers 503, so point this at a Core you run yourself. Set:
COUNTERSIGN_URL — your Core, e.g. https://app.countersign.networkCOUNTERSIGN_API_KEY — required when the Core has auth enabledAdd to your MCP config (claude_desktop_config.json, or claude mcp add, or Cursor's mcp.json):
{
"mcpServers": { "countersign": { "command": "npx", "args": ["-y", "@countersign/mcp"], "env": { "COUNTERSIGN_URL": "https://app.countersign.network", "COUNTERSIGN_API_KEY": "csk_…" } } } }
That's it — your agent now has the spend guard and the kill switch.
If Countersign guards your agent, say so — it tells users (and other agents) that spending is governed, and points the next operator at the same kill switch. Drop this in your README:
[](https://countersign.network)
Countersign spreads by being easy to discover wherever agent builders look for tools. The metadata below is ready to submit to the common registries — copy it as-is.
registry.modelcontextprotocol.io / the mcp-registry repo) — entry: {
"name": "io.github.countersign-network/countersign", "description": "Cross-vendor kill switch + spend guard for AI agents that spend money — one policy, one freeze, one tamper-evident ledger across every wallet/card backend.", "homepage": "https://countersign.network", "repository": "https://github.com/countersign-network/countersign", "packages": [ { "registry": "npm", "name": "@countersign/mcp", "runtime": "npx" } ], "license": "Apache-2.0" }
- **[mcp.so](https://mcp.so)** — submit `@countersign/mcp`; category *Finance / Security / Agents*.
npx-launched server; env COUNTERSIGN_URL (default https://app.countersign.network) + optional COUNTERSIGN_API_KEY.[Countersign](https://github.com/countersign-network/countersign) — cross-vendor spend guard + sub-second kill switch + tamper-evident ledger for AI agents that move money (Coinbase, Turnkey, Openfort, Visa card). Testnet.
Standard listing fields:
| Field | Value |
|---|---|
| Server id | countersign |
| Launch | npx -y @countersign/mcp |
| Tools | countersign_request_spend, countersign_freeze, countersign_apply_policy, countersign_list_agents, countersign_health, countersign_list_approvals, countersign_approve, countersign_deny, countersign_ledger, countersign_unfreeze |
| Tags | payments · security · kill-switch · spend-guard · agent-payments · wallet |
Nothing here is auto-submitted — listings are made deliberately by a maintainer.
Apache-2.0. Countersign holds policy/freeze/ledger; it never takes custody of funds. Testnet only.