OWS-native approval layer

ClearSign

ClearSign gives treasury teams and agent-driven systems a safer approval path with readable proposals, signer thresholds, expiry, anomaly detection, and a final execution gate.

$curl -fsSL https://clearsign.fun/setup.sh | bash

CLI, skill, and MCP for safer treasury and agent approvals.

Why ClearSign

Human-readable

Review what moves

Every approval starts with a proposal people can actually read before a signature is produced.

Remote signers

Keep custody separate

Proposal JSON moves between machines. Private keys do not.

Hard stops

Expire and block bad flows

TTL, anomaly checks, and execution gating stop stale or suspicious approvals.

Flow

Three steps between request and execution.

Build a proposal

Create intent with title, description, asset, payload, signer set, and expiry.

Share for review

Signers import the same proposal, verify the hash, and approve from their own machines.

Verify before execution

ClearSign collects signatures, runs anomaly checks, and blocks anything expired or unsafe.

Stack

Use the CLI, library, skill, and MCP from the same model.

CLI

Run the signing flow

clearsign keygen
clearsign review ./proposal.json
clearsign sign ./proposal.json

Library

Embed it in apps

import { buildProposal, MultiSigCoordinator, ExecutionGate } from "clearsign";

Skill + MCP

Use it with agents

skills/clearsign/SKILL.md
node mcp/clearsign-server/index.mjs