Is io.github.cdrn/sigil safe to use?

io.github.cdrn/sigil has no known CVEs as of the latest MCPpedia security scan. Authentication requirements were not detected automatically - check the project's documentation before connecting in a shared environment. Licensed under Apache-2.0.

How do I install io.github.cdrn/sigil?

io.github.cdrn/sigil supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can io.github.cdrn/sigil do?

io.github.cdrn/sigil provides 3 tools: sigil_sign_personal, sigil_sign_transaction, sigil_sign_typed_data. See the full tools list on the server page for descriptions and parameters.

What AI clients work with io.github.cdrn/sigil?

io.github.cdrn/sigil is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse transport.

Is io.github.cdrn/sigil actively maintained?

io.github.cdrn/sigil is recently maintained - last commit was 30 days ago. It has 3 GitHub stars.

io.github.cdrn/sigil

sigild

Local keystore + MCP server. Claude can sign EVM transactions but never sees the private key.

3 183/wk 3 tools GitHub npm

No known CVEs

Apache-2.0 license

Maintained

Last commit 30d ago

Works with most clients

Transport: stdio, sse

3 tools · ~315 tok

Grade A · 0.2% of 200K ctx

MCPpedia last refreshed this data 2d ago

Edit this pageView history

io.github.cdrn/sigil is an MCP server that local keystore + MCP server. Claude can sign EVM transactions but never sees the private key. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 87/100 on MCPpedia's security, maintenance and efficiency rubric.

AI / ML Finance

Step 1

Install in your client

Config is the same across clients - only the file and path differ.

Supported in Claude Desktopstdio, sse · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-cdrn-sigil": {
      "args": [
        "-y",
        "sigild"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-cdrn-sigil)](https://mcppedia.org/s/io-github-cdrn-sigil)

Read me

What io.github.cdrn/sigil does

Local keystore + MCP server. Claude can sign EVM transactions but never sees the private key.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.

npx -y 'sigild' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories - click any category to see the underlying evidence.

Score breakdown

87/100across 5 weighted dimensions

How we score →

0255075100

−13

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked sigild against OSV.dev.

Inventory

Tools (3)

Click any tool to inspect its schema.

~315 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience - it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.cdrn/sigil safe to use?: io.github.cdrn/sigil has no known CVEs as of the latest MCPpedia security scan. Authentication requirements were not detected automatically - check the project's documentation before connecting in a shared environment. Licensed under Apache-2.0.
How do I install io.github.cdrn/sigil?: io.github.cdrn/sigil supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.cdrn/sigil do?: io.github.cdrn/sigil provides 3 tools: sigil_sign_personal, sigil_sign_transaction, sigil_sign_typed_data. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.cdrn/sigil?: io.github.cdrn/sigil is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse transport.
Is io.github.cdrn/sigil actively maintained?: io.github.cdrn/sigil is recently maintained - last commit was 30 days ago. It has 3 GitHub stars.

Similar servers

Others in ai-ml / finance

View all →

Vibe Assistant95

A cross-platform desktop application for managing AI Agents and MCP Servers. 一款用于管理AI智能体与MCP服务器的跨平台桌面应用程序。

169 3

Codebase Memory Mcp95

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

48.6k 6

Gemini Cli95

An open-source AI agent that brings the power of Gemini directly into your terminal.

108.8k 8

Bla95

🛡️ BLA (Blind LLM Agents) — Adversarial defense shield that protects binaries, Electron apps, JS bundles, Python, and WebAssembly against AI reverse-engineering agents like REA. Poison -> Exhaust -> Hallucinate.

5.5k 1

MCP Security Weekly

Get CVE alerts and security updates for io.github.cdrn/sigil and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

AI / ML Finance

Step 1

Install in your client

Config is the same across clients - only the file and path differ.

Supported in Claude Desktopstdio, sse · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-cdrn-sigil": {
      "args": [
        "-y",
        "sigild"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-cdrn-sigil)](https://mcppedia.org/s/io-github-cdrn-sigil)

Read me

What io.github.cdrn/sigil does

Local keystore + MCP server. Claude can sign EVM transactions but never sees the private key.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.

npx -y 'sigild' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

sigil

Claude can sign, but never see.

sigil is a local signing tool and Claude Code integration that lets agentic coding tools use private keys without ever putting key material in the model's context window.

Status: pre-alpha. The MCP server, CLI, unlock flow, ward hooks, policy engine (static checks), out-of-band confirmation via ntfy, Solana signing, and the JSON-RPC signing proxy (Foundry/Hardhat) all work end-to-end. Rolling-window value caps and EIP-712 domain allowlists landed in the policy engine, but have not been through a release yet. Until v0.1.0 ships — with the supply-chain attestations promised for it — do not use this with real funds yet. Build plan lives in the tracking issue.

What it is

One MCP server process, four bins (plus a legacy sigild alias), six runtime deps (all pinned, zero transitive):

sigil-mcp — the only thing that runs. Claude Code spawns it per session via your mcpServers config; it dies when Claude exits. Holds unlocked keys in process memory (zeroized on shutdown, sigil lock, or unlock-failure; mlock against swap is planned). Keys at rest are encrypted with XChaCha20-Poly1305 and an Argon2id-derived key. Signs over stdio using a DIY MCP wire protocol (~200 lines, no SDK dep). Claude never sees key material — only opaque handles like evm:executor.
sigil — control CLI. init, status, portal new/add/list/qr/remove, policy show/init, unlock, lock.
sigil-hook-pre / sigil-hook-post — Claude Code hook binaries that block reads of common key paths and redact key-shaped strings from tool output.

sigil-mcp boots locked: empty in-memory handle table, no keys loaded. Sign methods return DAEMON_LOCKED (-32003) with a "run sigil unlock" message until you push the passphrase in from a separate terminal via sigil unlock. That CLI connects to a per-session Unix socket at ~/.sigil/control/<pid>.sock (0600) that sigil-mcp opens at startup — and fans out to every such socket so one sigil unlock reaches all open windows. After unlock, signs work for the rest of the session; sigil lock zeroizes the table without killing the process.

Sign methods exposed today: EIP-191 personal_sign, EIP-1559 + legacy transactions, EIP-712 typed data, plus Solana (ed25519) message + transaction signing — see Solana support below.

What it isn't

Not a hardware wallet replacement. If you can use a Ledger or YubiKey, do that.
Not a custody solution. It runs on your laptop or VPS and protects you from one specific class of failure: leaking key material through an LLM agent.
A first cut of bounding signing authority via the policy engine — but not the full thing. Shipped: static checks (chain ID, destination allowlist, per-tx value cap, function-selector allowlist, contract-creation gating, on/off toggles for personal_sign and EIP-712) plus out-of-band human confirmation via ntfy. Rolling-window caps and EIP-712 domain allowlists are tracked in #3 and will land incrementally.

Install

npm install -g sigild

This drops four binaries on your $PATH: sigil, sigil-mcp, sigil-hook-pre, sigil-hook-post (plus sigild, a legacy alias for sigil-mcp). (The package name on npm is sigild for legacy reasons; the bins do not include a daemon any more.)

Requires Node 22+, macOS or Linux. (The CLI ↔ session control channel uses Unix domain sockets; Windows is untested and currently unsupported.)

Quick start

# 1. Wire sigil into Claude Code (project-scoped). Pass --user to do it globally.
sigil init

# 2a. Generate a fresh key inside sigil (no plaintext ever hits disk):
sigil portal new evm:bot
# → prompts for a passphrase, mints a fresh secp256k1 key, prints the
#   address, writes ~/.sigil/keys/evm:bot.sigil + permissive policy.
#
# 2b. OR import an existing private key from a file:
#     Accepts either 

... [View full README on GitHub](https://github.com/cdrn/sigil#readme)

Loading README…

Scored, not listed

Why this score

Five weighted categories - click any category to see the underlying evidence.

Score breakdown

87/100across 5 weighted dimensions

How we score →

0255075100

−13

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked sigild against OSV.dev.

Inventory

Tools (3)

Click any tool to inspect its schema.

~315 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience - it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.cdrn/sigil safe to use?: io.github.cdrn/sigil has no known CVEs as of the latest MCPpedia security scan. Authentication requirements were not detected automatically - check the project's documentation before connecting in a shared environment. Licensed under Apache-2.0.
How do I install io.github.cdrn/sigil?: io.github.cdrn/sigil supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.cdrn/sigil do?: io.github.cdrn/sigil provides 3 tools: sigil_sign_personal, sigil_sign_transaction, sigil_sign_typed_data. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.cdrn/sigil?: io.github.cdrn/sigil is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse transport.
Is io.github.cdrn/sigil actively maintained?: io.github.cdrn/sigil is recently maintained - last commit was 30 days ago. It has 3 GitHub stars.