Pexbot Mcp vs Signer Mcp — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Pexbot Mcp vs Signer Mcp
In-depth architectural comparison of the Pexbot Mcp and Signer Mcp MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Pexbot Mcp
Finance & Fintech · Local stdio
Quality: 53/100 (Good) | Auth: API Key required
Signer Mcp
Finance & Fintech · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Verdict Summary: Choose Pexbot Mcp if you need specialized Finance & Fintech tools running via a local process. Choose Signer Mcp if your workspace requires Finance & Fintech integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Pexbot Mcp when:
You need dedicated capabilities in the Finance & Fintech domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: PEXBOT_API_KEY, PEXBOT_TOKEN, PEXBOT_API_URL.
AI simulated crypto trading with real-time Upbit prices. 11 tools for registration, trading, and autonomous AI investment with 100M KRW virtual balance. npx -y @pexbot/mcp
Keyless CEX/DEX signing for AI trading agents (Binance, OKX, Bybit, KuCoin, Hyperliquid, Asterdex). Signing keys never leave an AWS Nitro Enclave (attested PCR0); agents receive policy-bounded signatures, not credentials. Built to survive prompt injection and supply-chain key leaks. 5 tools, stdio. Install with npx -y @usenami/signer-mcp.
Category & Scope
Tools & Capabilities Breakdown
Pexbot Mcp Tools (22)
register
Self-register an AI agent account (PoW + fingerprint + auto API key)
activate
Register device and receive 100M KRW virtual balance
get_profile
Get account profile and activation status
get_balance
Get asset balances across all holdings
get_markets
List all available trading markets
get_ticker
Get current ticker (price, volume) for a market
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Pexbot Mcp is categorized under Finance & Fintech and uses a local stdio subprocess. In contrast, Signer Mcp belongs to Finance & Fintech using local stdio subprocess. Select Pexbot Mcp when you need capabilities focused on finance & fintech and Signer Mcp when you require tools for finance & fintech.
Place buy/sell order (limit or market) with optional `reason_ko`, `reason_en`, `confidence`, `strategy_tag
cancel_order
Cancel an open order by ID
list_orders
List your spot orders with optional status and symbol filters
get_trades
Get recent trades for a specific market
futures_transfer
Transfer funds between spot and futures wallets
+10 more tools listed on main page
Signer Mcp Tools (5)
list_venues
Returns the static manifest of venues this Signer can sign for. **Read-only**, does not contact the gateway, works without a token. Call this first to discover what's supported.
get_attestation
Returns the Nitro attestation document for the currently-running enclave. The PCR0 measurement here is what AWS signed when it booted the enclave; you can verify it matches the published build by hashing the corresponding EIF and comparing.
get_account
Returns equity, free margin, and open positions for a venue.
place_order
Place a single market or limit order. The enclave signs the payload after checking policy caps.
cancel_order
Cancels an outstanding order by its venue order id. Idempotent — cancelling an already-filled or non-existent order returns `ok: false` with a venue reason instead of erroring.