io.github.daedalus/mcp-ecdsa

MCPcommunity
v0.1.1io.github.daedalusUnknownUpdated 5mo agoGitHub

MCP server for ECDSA cryptography

MCP server for ECDSA cryptography mcp-name: io.github.daedalus/mcp-ecdsa Configure in your MCP client: ------|-------------| | Generate ECDSA key pair | | Sign data (with hashing) | | Sign pre-hashed digest | | Verify signature over data | | Verify signature over digest | | Import from PEM/DER/base64 | | Import from PEM/DER/base64 | | Export to PEM/DER/base64/SSH | | Export to PEM/DER/base64/SSH…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5mo agoLast update
Package
Authorio.github.daedalus
LicenseUnknown
Version0.1.1
Sourcemcp-registry
GitHubdaedalus/mcp-ecdsa
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ Cleanv0.1.1 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

MCP server for ECDSA cryptography mcp-name: io.github.daedalus/mcp-ecdsa Configure in your MCP client: ------|-------------| | Generate ECDSA key pair | | Sign data (with hashing) | | Sign pre-hashed digest | | Verify signature over data | | Verify signature over digest | | Import from PEM/DER/base64 | | Import from PEM/DER/base64 | | Export to PEM/DER/base64/SSH | | Export to PEM/DER/base64/SSH | | Get key information | | Recover public keys from signature | NIST192p, NIST224p, NIST256p,…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.