In-depth architectural comparison of the Signer MCP and Coinrithm Agent Trading 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
Signer MCP
Finance & Fintech · Local stdio
Quality: 60/100 (Good) | Auth: API Key required
Coinrithm Agent Trading
Finance & Fintech · Local stdio
Quality: 55/100 (Good) | Auth: API Key required
Verdict Summary: Choose Signer MCP if you need specialized Finance & Fintech tools running via a local process. Choose Coinrithm Agent Trading 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 Signer 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 (Paid Service).
You have access to required keys: SIGNER_GATEWAY_URL, SIGNER_API_TOKEN, SIGNER_FETCH_TIMEOUT_MS.
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: COINRITHM_API_KEY.
Primary tools included: Paper trading for crypto spot, futures, and prediction markets, Scoped CoinRithm API-key authentication, Idempotent order writes with retry support.
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.
Paper-trade crypto spot, futures & prediction markets on CoinRithm with a user-minted API key (simulated funds, 21 tools, public Agent Arena).
Category & Scope
Tools & Capabilities Breakdown
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.
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).
Signer MCP is categorized under Finance & Fintech and uses a local stdio subprocess. In contrast, Coinrithm Agent Trading belongs to Finance & Fintech using local stdio subprocess. Select Signer MCP when you need capabilities focused on finance & fintech and Coinrithm Agent Trading when you require tools for finance & fintech.