MCP Ecdsa logo

MCP Ecdsa

Generate, import, export, sign, verify, and inspect elliptic-curve keys through MCP.

Install MCP Ecdsa

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-ecdsa": {
      "command": "uvx",
      "args": [
        "mcp-ecdsa"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

uvx mcp-ecdsa

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 11d ago.

Overview

mcp-ecdsa MCP server exposes ECDSA cryptography operations through MCP over a standard command-based interface. It can generate key pairs, sign data or pre-hashed digests, verify signatures, import and export keys, inspect key details, and recover public keys. Reach for it when an MCP client or agent needs programmatic elliptic-curve key handling without embedding these operations in its own tool implementation.

Use cases

  • Generate elliptic-curve key pairs for agent workflows
  • Sign data or pre-hashed digests
  • Verify signatures over data and digests
  • Convert keys between PEM, DER, base64, and SSH formats
  • Inspect keys and recover public keys from signatures

Key features

  • ECDSA key-pair generation
  • Data and digest signing
  • Data and digest signature verification
  • PEM, DER, base64, and SSH key import and export
  • Key information lookup
  • Public-key recovery

Tools11

What MCP Ecdsa lets your agent do. Expand a tool for its parameters.

Self-reported~114 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

8/8 checks healthy over the last 48d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · mcp-ecdsa (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
Last commit6mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed11Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Ecdsa works

What mcp-ecdsa MCP server does

The mcp-ecdsa MCP server makes elliptic-curve cryptography available as MCP tools. It supports key-pair generation, signing, signature verification, key conversion, key inspection, and public-key recovery. Operations can work with complete data or with digests that have already been calculated by another process.

Supported curves include NIST192p, NIST224p, NIST256p, NIST384p, NIST521p, SECP256k1, Ed25519, and Ed448. The listed hash options are SHA1, SHA224, SHA256, SHA384, SHA512, SHA3-256, SHA3-384, and SHA3-512.

How it works

The server runs as the mcp-ecdsa command and communicates with an MCP client through the command configuration. A client sends arguments to individual tools and receives structured tool results. The repository also exposes Python functions, including generate_key, sign_data, and verify_signature, for callers using the package directly.

Data signing tools cover two workflows. sign_data hashes the supplied data before signing, while sign_digest accepts a digest that was prepared elsewhere. Matching verification tools are available for both forms: verify_signature checks a signature against data, and verify_digest_signature checks one against a digest.

Setup and configuration

Install the package from PyPI with:

Terminal
pip install mcp-ecdsa

Register the server in an MCP client by using the installed executable as the command:

config.json
{
  "mcpServers": {
    "mcp-ecdsa": {
      "command": "mcp-ecdsa"
    }
  }
}

The repository also includes development instructions for an editable installation with test dependencies, followed by pytest, Ruff, and mypy commands.

Tools and capabilities

Available tools are:

  • generate_key: create an elliptic-curve key pair.
  • sign_data: hash and sign supplied data.
  • sign_digest: sign an existing digest.
  • verify_signature: verify a signature over data.
  • verify_digest_signature: verify a signature over a digest.
  • import_private_key and import_public_key: read keys from PEM, DER, or base64 input.
  • export_private_key and export_public_key: write keys as PEM, DER, base64, or SSH output.
  • get_key_info: return information about a key.
  • recover_public_key: recover public keys from a signature.

Limitations and notes

Those details should be confirmed before relying on the server in a production signing workflow.

The package can be used through MCP or its Python API. The documented Python example uses asynchronous functions and reads text from the returned tool result before passing key and signature values to later operations.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Ecdsa

mcp-ecdsa is an MCP server that connects MCP clients to elliptic-curve cryptography operations. Its main tools generate keys, sign data or pre-hashed digests, verify signatures, import and export keys, inspect key information, and recover public keys from signatures. It supports several NIST, SECP256k1, Ed25519, and Ed448 curves.

Install it with `pip install mcp-ecdsa`. Then configure your MCP client to run the `mcp-ecdsa` command as the server process. The provided configuration uses a standard command entry without documented environment variables.

It supports NIST192p, NIST224p, NIST256p, NIST384p, NIST521p, SECP256k1, Ed25519, and Ed448.

Yes. Use `sign_digest` to sign an existing digest, and use `verify_digest_signature` to verify a signature against a digest. For unprocessed data, use `sign_data` and `verify_signature`, which operate on data with hashing.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Ecdsa AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-ecdsa?style=directory)](https://allmcps.com/mcp/mcp-ecdsa)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-ecdsa"><img src="https://allmcps.com/api/badge/mcp-ecdsa?style=directory" alt="MCP Ecdsa on AllMCPs" /></a>