Skip to main content
Glama
mcp-ecdsa

mcp-ecdsa

by daedalus

mcp-ecdsa

MCP server for ECDSA cryptography

PyPI Python Ruff

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

Install

pip install mcp-ecdsa

Related MCP server: dpay-mcp

Usage

As MCP Server

Configure in your MCP client:

{
  "mcpServers": {
    "mcp-ecdsa": {
      "command": "mcp-ecdsa"
    }
  }
}

Python API

from mcp_ecdsa import generate_key, sign_data, verify_signature

# Generate key pair
result = await generate_key({"curve": "NIST256p"})
data = json.loads(result[0].text)

# Sign data
sign_result = await sign_data({
    "private_key": data["private_key"],
    "data": "Hello, World!"
})

# Verify signature
verify_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

git clone https://github.com/daedalus/mcp-ecdsa.git
cd mcp-ecdsa
pip install -e ".[test]"

# run tests
pytest

# format
ruff format src/ tests/

# lint
ruff check src/ tests/

# type check
mypy src/

Available Tools

11 tools
_export_private_keyC

Export a private key to various formats

Inputs: private_key (required), curve, format, pem_format. Returns: result

_export_public_keyC

Export a public key to various formats

Inputs: public_key (required), curve, format, point_encoding. Returns: result

_generate_keyC

Generate a new ECDSA key pair

Inputs: curve, hashfunc. Returns: result

_get_key_infoD

Get information about a key

Inputs: private_key, public_key, curve, hashfunc. Returns: result

_import_private_keyC

Import a private key from various formats

Inputs: key_data (required), format (required), curve, hashfunc. Returns: result

_import_public_keyC

Import a public key from various formats

Inputs: key_data (required), format (required), curve, hashfunc. Returns: result

_recover_public_keyC

Recover public keys from a signature and signed data

Inputs: signature (required), data (required), curve, hashfunc. Returns: result

_sign_dataC

Sign data using ECDSA

Inputs: private_key (required), data (required), curve, hashfunc, +2 more. Returns: result

_sign_digestC

Sign a digest directly using ECDSA (no hashing)

Inputs: private_key (required), digest (required), curve, sigencode, +1 more. Returns: result

_verify_digest_signatureC

Verify a signature over a digest

Inputs: public_key (required), signature (required), digest (required), curve, +1 more. Returns: result

_verify_signatureC

Verify an ECDSA signature

Inputs: public_key (required), signature (required), data (required), curve, +2 more. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a distinct purpose: key generation, import/export, signing, verification, and recovery. Even though signing and verification have two variants each (data vs digest), they are clearly differentiated by whether hashing is performed.

    Naming Consistency5/5

    All tool names follow the snake_case pattern with a verb_noun structure (e.g., _export_private_key, _sign_data). The underscore prefix is consistent across all tools, making the naming predictable.

    Tool Count5/5

    With 11 tools covering key lifecycle (generate, import/export, info) and signing/verification operations, the count is well-scoped for an ECDSA server. It provides necessary functionality without redundancy.

    Completeness4/5

    The set covers core ECDSA operations: key management, signing, verification, and public key recovery. A minor gap is the lack of a key deletion tool, but this does not hinder typical signing workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers