Chain Signer
Let your coding agent review wallet and chain transactions for drains, permit phishing, and other risky signatures before you approve them.
Overview
chain-signer is a MCP server for the Ship phase that flags drains, permit-phishing, and other risky on-chain signing actions before an AI agent or user approves them.
What is this MCP server?
- Pre-sign analysis for AI agents that propose or execute on-chain transactions
- Flags token drains, permit-phishing patterns, and other high-risk signing requests
- Security-focused MCP suite around chain signing workflows, not generic chat guardrails
- stdio PyPI package chain-signer for local agent wiring
- Versioned MCP server schema (0.5.9) from the Kevthetech143/chain-signer repository
- MCP server version 0.5.9
- Single stdio transport package published as chain-signer on PyPI
- Focused on three risk classes called out in catalog copy: drains, permit-phishing, and risky signing actions
What problem does it solve?
Agents that draft or execute wallet transactions can push you toward signatures that drain funds or abuse permits without a dedicated pre-sign safety check.
Who is it for?
Solo builders shipping wallet-connected agents, trading bots, or DeFi helpers who want MCP-native guardrails at signing time.
Skip if: Teams that need a full smart-contract audit, key custody solution, or off-chain fraud monitoring without any signing step.
What do I get? / Deliverables
After you register chain-signer, your agent can surface risky signing patterns for review so you reject bad transactions before they land on-chain.
- MCP tools that evaluate proposed signatures for drain and phishing-style risk patterns
- Actionable warnings the agent can show before you approve a chain transaction
- A repeatable pre-sign review step in agent-driven Web3 workflows
Recommended MCP Servers
Journey fit
Signing and on-chain actions are a launch-and-ship risk surface whenever agents or scripts touch wallets, so the canonical shelf is Ship with a security subphase. The server exists specifically to flag dangerous signing patterns pre-execution, which is application security at the moment of commit—not generic monitoring after the fact.
How it compares
Pre-sign security MCP integration, not a general-purpose agent skill or on-chain monitoring dashboard.
Common Questions / FAQ
Who is chain-signer for?
It is for developers and indie builders who use AI agents around Ethereum-style signing and want automated warnings on drains and permit-phishing before they sign.
When should I use chain-signer?
Use it whenever an agent proposes transactions, token approvals, or permits—especially in production-adjacent or mainnet workflows where one bad signature is costly.
How do I add chain-signer to my agent?
Install the PyPI package chain-signer, configure the MCP server over stdio in your agent host (for example Claude Code or Cursor), and point the server entry at the published chain-signer MCP definition from the repository.