Mcp Ecdsa

io.github.daedalusPublished by GitHub account daedalusv0.1.1Updated Oct 24, 2026

MCP server for ECDSA cryptography

VerifiedSTDIODesktop onlyDeveloper Tools Security & Monitoring

Server details

Identifier: io.github.daedalus/mcp-ecdsa
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account daedalus for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.daedalus%2Fmcp-ecdsa.svg)](https://sourceweft.com/mcp/io.github.daedalus%2Fmcp-ecdsa?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server exposing ECDSA key generation, signing, verification and key import/export tools to an assistant.

What you can do: Generate ECDSA key pairs on supported curves, including NIST, SECP256k1, Ed25519 and Ed448
Sign data with hashing, or sign a pre-hashed digest
Verify signatures over data or over a digest, and recover public keys from a signature
Import private and public keys from PEM, DER or base64
Export keys to PEM, DER, base64 or SSH format and read key information
When to use it: Useful when an assistant needs to create test key pairs, sign or verify payloads, or convert keys between PEM, DER, base64 and SSH formats during development or debugging of cryptographic workflows.
Requirements: Runs as a local process over stdio, installed from the PyPI package mcp-ecdsa (pip install mcp-ecdsa) and configured in the MCP client with the mcp-ecdsa command. No accounts, API keys or environment variables are declared.

Before you install

The tools handle private keys: signing and export take private key material, and generated or imported private keys may be returned to the assistant and its conversation. Treat any key used here as exposed, avoid real production or wallet keys, and note that SECP256k1 keys can control cryptocurrency funds.

Installation

In SourceWeft

Open Mcp Ecdsa in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mcp-ecdsa

MCP server for ECDSA cryptography

[PyPI] [Python] [Ruff]

mcp-name: io.github.daedalus/mcp-ecdsa

Install

Usage

As MCP Server

Configure in your MCP client:

Python API

python

from mcp_ecdsa import generate_key, sign_data, verify_signature
# Generate key pairresult = await generate_key({"curve": "NIST256p"})data = json.loads(result[0].text)
# Sign datasign_result = await sign_data({    "private_key": data["private_key"],    "data": "Hello, World!"})
# Verify signatureverify_result = await verify_signature({    "public_key": data["public_key"],    "signature": json.loads(sign_result[0].text)["signature"],    "data": "Hello, World!"})

from mcp_ecdsa import generate_key, sign_data, verify_signature
# Generate key pairresult = await generate_key({"curve": "NIST256p"})data = json.loads(result[0].text)
# Sign datasign_result = await sign_data({    "private_key": data["private_key"],    "data": "Hello, World!"})
# Verify signatureverify_result = await verify_signature({    "public_key": data["public_key"],    "signature": json.loads(sign_result[0].text)["signature"],    "data": "Hello, World!"})

Tools

Tool	Description
`generate_key`	Generate ECDSA key pair
`sign_data`	Sign data (with hashing)
`sign_digest`	Sign pre-hashed digest
`verify_signature`	Verify signature over data
`verify_digest_signature`	Verify signature over digest
`import_private_key`	Import from PEM/DER/base64
`import_public_key`	Import from PEM/DER/base64
`export_private_key`	Export to PEM/DER/base64/SSH
`export_public_key`	Export to PEM/DER/base64/SSH
`get_key_info`	Get key information
`recover_public_key`	Recover public keys from signature

Supported Curves

NIST192p, NIST224p, NIST256p, NIST384p, NIST521p
SECP256k1
Ed25519, Ed448

Supported Hash Functions

SHA1, SHA224, SHA256, SHA384, SHA512
SHA3-256, SHA3-384, SHA3-512

Development

bash

git clone https://github.com/daedalus/mcp-ecdsa.gitcd mcp-ecdsapip install -e ".[test]"
# run testspytest
# formatruff format src/ tests/
# lintruff check src/ tests/
# type checkmypy src/

git clone https://github.com/daedalus/mcp-ecdsa.gitcd mcp-ecdsapip install -e ".[test]"
# run testspytest
# formatruff format src/ tests/
# lintruff check src/ tests/
# type checkmypy src/

Source: README.md at commit 383ec6e

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts