MCP.Market

Countersign MCP server

by countersign-network·io.github.countersign-network/countersign·v0.2.2·1 stars

Kill switch + spend guard for AI agents that spend money, across every wallet vendor at once.

B82/100grade B
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
Growing

1 stars76 downloads/wk

Reviews

Write one

Nobody has reviewed Countersign yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Countersign tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it

no findings
  • Code scan4 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Countersign compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 63% of 48,255 servers
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
76
more than 56% of 12,191 servers with a package

Install Countersign in Claude Code, Cursor or VS Code

Runs npx -y @countersign/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add countersign -- npx -y @countersign/mcp
Add to Cursor

What the publisher says

From the Countersign repository's README, as published. We do not edit it. Read it on GitHub

Countersign

A neutral, cross-vendor control plane for AI agents that spend money. Countersign holds the policy, the freeze, and the audit ledger across multiple agent-wallet backends at once — the one thing no single wallet vendor can do, because each only governs its own rail. That aggregation is the moat.

Live version of this loop: countersign.network/demo.html · 60s video

One falsifiable test defines it: **can Countersign freeze agents across many backends at once, in

under a second, with a unified tamper-evident ledger of every attempt? Proven LIVE across four

rails (Coinbase, Turnkey, Openfort, and a Lithic Visa card**) in ~432ms on testnet.

❄️ The hosted Core is paused (2026-09-18). app.countersign.network is switched off: it issues no

keys and existing keys no longer authenticate. These packages are unaffected — they are Apache-2.0,

still published on npm, and work against a Core you run yourself. Point COUNTERSIGN_URL at your own

instance wherever this README says app.countersign.network.

This repository is the open-core front door — the Apache-2.0 packages you build against: the integration contract, the typed client, the MCP tools, and the x402 guard. The control-plane "brain" (the policy compiler, the hash-chained ledger, the vendor adapters, and the hosted Core) is separate and proprietary; you reach it over the network via the SDK/MCP. It was hosted at app.countersign.network, which is currently paused — self-host the Core to use these packages today.

Quickstart

Drop the kill switch + spend guard into any MCP client (Claude, Cursor, …) — one line:

// claude / cursor mcp config
{ "mcpServers": { "countersign": {
  "command": "npx", "args": ["-y", "@countersign/mcp"],
  "env": { "COUNTERSIGN_URL": "https://app.countersign.network", "COUNTERSIGN_API_KEY": "csk_…" }
}}}

Or wire it into your own agent with the SDK:

import { CountersignClient } from "@countersign/sdk";
const cs = new CountersignClient({ baseUrl, apiKey });

await cs.evaluate({ agentId, amount, asset, venue }); // may this spend happen? (allow / deny / needs_approval)
await cs.freeze();                                     // the kill switch — every backend, < 1s

~~Get a free testnet key at app.countersign.network/start~~ — the hosted signup is paused. Run your own Core and issue yourself a key with POST /signup.

Agents paying agents? See examples/guarded-payee — the A2A/AP2 pattern where a payee advertises it is governed and the payer verifies that (and guards its own payment) before any mandate is signed.

Packages (this repo — all Apache-2.0)

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Countersign: common questions

Is Countersign MCP server safe?
Mostly: it is graded B (82/100). Read the Countersign safety report
How do I install Countersign?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Countersign need an API key?
Yes. The registry entry asks for COUNTERSIGN_API_KEY.
Is Countersign maintained?
The last commit was 3 days ago (2026-11-01). The latest release is v0.2.2.
How does Countersign compare with other MCP servers?
safety score 82/100 (higher than 63% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers); downloads a week 76 (more than 56% of 12,191 servers with a package). Full comparison.