io.github.CryptoAPIs-io/mcp-signer

MCPcommunity
v0.3.0io.github.CryptoAPIs-ioUnknownUpdated 3mo agonpmGitHub

MCP server for local transaction signing on EVM, UTXO, Tron, and XRP — no API calls needed

MCP server for local transaction signing across EVM, UTXO, Tron, and XRP blockchains. No Crypto APIs HTTP calls — signing happens entirely on your machine. No API key required. Stdio only — no HTTP transport. The server does not listen on any port. Private keys in tool input — each tool receives / / as parameters. Keys are never read from environment variables. No network calls — all signing is…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3mo agoLast update
Package
Authorio.github.CryptoAPIs-io
LicenseUnknown
Version0.3.0
Sourcemcp-registry
npm@cryptoapis-io/mcp-signer
GitHubCryptoAPIs-io/cryptoapis-mcp-signer
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ 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>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies60 resolved · 2 with advisories
Tool surface4 tools · none privileged
Security scan✓ Cleanv0.3.0 · 20d ago
DEPelliptic@6.6.1GHSA-848j-6mx2-7j84
DEPws@8.17.1GHSA-58qx-3vcg-4xpx (transitive)
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

MCP server for local transaction signing across EVM, UTXO, Tron, and XRP blockchains. No Crypto APIs HTTP calls — signing happens entirely on your machine. No API key required. Stdio only — no HTTP transport. The server does not listen on any port. Private keys in tool input — each tool receives / / as parameters. Keys are never read from environment variables. No network calls — all signing is done locally using cryptographic libraries. Or install all Crypto APIs MCP servers: Add to your…

Keywords
mcp