namixai/signer-mcp

Overview

namixai/signer-mcp lets any MCP-aware AI agent sign orders for CEX/DEX exchanges like Binance, OKX, and Asterdex. The signing key never leaves an AWS Nitro Enclave, attested via PCR0. It exposes five tools over stdio.

Best for

Best for
Developers building AI-powered trading agents that need hardware-backed key protection on AWS

Use cases

• Automate order signing from an AI trading agent without exposing private keys
• Integrate secure trade execution into AI assistants for crypto exchanges
• Enforce key isolation in high-security trading workflows using attested enclaves

How to use

Install

npm install @elizaos/plugin-mcp

Tools exposed

• SIGNER_GATEWAY_URL
• SIGNER_API_TOKEN
• SIGNER_FETCH_TIMEOUT_MS
• hyperliquid_main

Tested with

Claude Desktop, Cursor

Example client config

{\n     "mcpServers": {\n       "signer": {\n         "command": "npx",\n         "args": ["-y", "@usenami/signer-mcp"],\n         "env": {\n           "SIGNER_GATEWAY_URL": "https://signer.usenami.io",\n           "SIGNER_API_TOKEN": "sk_live_..."\n         }\n       }\n     }\n   }

Notes

namixai/signer-mcp lets any MCP-aware AI agent sign orders for CEX/DEX exchanges like Binance, OKX, and Asterdex. The signing key never leaves an AWS Nitro Enclave, attested via PCR0. It exposes five tools over stdio.

0 stars on GitHub. Last updated 2026-06-11. Licensed MIT.

Use cases

• Automate order signing from an AI trading agent without exposing private keys
• Integrate secure trade execution into AI assistants for crypto exchanges
• Enforce key isolation in high-security trading workflows using attested enclaves

Pros

• Private key never leaves the AWS Nitro Enclave, offering strong attestation and security
• Works with any MCP-capable AI agent and supports multiple major exchanges
• Simple stdio interface makes it easy to integrate into agent pipelines

Cons

• Requires AWS Nitro Enclave infrastructure, limiting portability to non-AWS environments
• Only five tools available, which may not cover all order types or exchanges
• Stdio-only transport restricts remote or cloud-native usage without additional bridging

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.