io.github.cdrn/sigil
NPM · SIGILD
Local keystore + MCP server. Claude can sign EVM transactions but never sees the private key.
Available components
Last scanned (26 minutes ago)
Scores higher than 97% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 1 of 4 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to cdrn/sigil). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 53 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 356 tokens (~89/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 −1
- Stability: pass → 0.93 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 −3
- Stability: pass → 0.77 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/sigild@0.0.6
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | cdrn/sigil |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/cdrn/sigil/.github/workflows/release.yml@refs/tags/v0.0.6 |
| Rekor log index | 1578289800 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:64a1b63e375a05daf3eaa49c291dece271f51e62f5c94035ffd1bf5dcc8150f6967f92b127be026259fb462b30f66efaa84f5f7b55cc379ab6d0070a0 |
Background: How many MCP packages publish verified provenance →
Dependencies 4 packages
| Packages resolved | 4 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
sigil_eth_sign_message ~100
Sign an EIP-191 personal_sign message with the named portal. The message is supplied as 0x-prefixed hex bytes (encode strings to UTF-8 first). Returns the 65-byte r||s||v signature as 0x-prefixed hex.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | 0x-prefixed hex of the bytes to sign. |
| portal | string | yes | Portal handle, e.g. "eth:executor". |
No output schema declared.
No examples provided.
sigil_eth_sign_transaction ~138
Sign an Ethereum transaction (legacy or EIP-1559) with the named portal. Returns the signed transaction as 0x-prefixed hex, ready for eth_sendRawTransaction.
| Name | Type | Req | Description |
|---|---|---|---|
| portal | string | yes | Portal handle. |
| tx | object | yes | Transaction fields. type="legacy" requires {chainId, nonce, gasPrice, gasLimit, to, value, data}. type="eip1559" requires {chainId, nonce, maxPriorityFeePerGas, maxFeePerGas, gasLimit, to, value, dat… |
No output schema declared.
No examples provided.
sigil_eth_sign_typed_data ~74
Sign an EIP-712 typed data structure with the named portal. Returns the 65-byte signature as 0x-prefixed hex.
| Name | Type | Req | Description |
|---|---|---|---|
| portal | string | yes | Portal handle. |
| typedData | object | yes | EIP-712 typed data: {types, primaryType, domain, message}. |
No output schema declared.
No examples provided.
sigil_list_portals ~44
List the signing portals currently loaded in sigil. Returns each portal handle (e.g. "eth:executor"), its kind, and the public address it controls.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.cdrn/sigil MCP server?
io.github.cdrn/sigil runs locally as an npm package, launched with npx -y sigild. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · sigild
claude mcp add cdrn-sigil -- npx -y sigild
What is the io.github.cdrn/sigil MCP server?
io.github.cdrn/sigil is an MCP server listed in the public MCP registry as io.github.cdrn/sigil. Local keystore + MCP server. Claude can sign EVM transactions but never sees the private key. This page covers its npm package (sigild).
Is the io.github.cdrn/sigil MCP server safe to use?
io.github.cdrn/sigil scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.cdrn/sigil MCP server expose?
io.github.cdrn/sigil exposes 4 tools: sigil_list_portals, sigil_eth_sign_message, sigil_eth_sign_transaction, sigil_eth_sign_typed_data. Their descriptions and schemas cost roughly 356 tokens of context every time the server is loaded.
Is the io.github.cdrn/sigil MCP server still maintained?
io.github.cdrn/sigil is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.cdrn/sigil MCP server under?
io.github.cdrn/sigil declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.