Armor Crypto MCP vs GDEX Trading
A side-by-side look at the Armor Crypto MCP and GDEX Trading MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Armor Crypto MCP for finance & fintech work as a local process; choose GDEX Trading for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Armor Crypto MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
ARMOR_API_KEY.
Choose GDEX Trading when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 51/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | ARMOR_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 178 | 4 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Armor Crypto MCP | View GDEX Trading |
Tools & capabilities
Armor Crypto MCP tools
No tool names declared yet. Check the project README from the listing page.
GDEX Trading tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Armor Crypto MCP
{
"mcpServers": {
"armorwallet-armor-crypto-mcp": {
"command": "uvx",
"args": [
"armor-crypto-mcp@latest"
],
"env": {
"ARMOR_API_KEY": "YOUR_ARMOR_API_KEY_HERE"
}
}
}
}
GDEX Trading
{
"mcpServers": {
"gdex-trading": {
"command": "npx",
"args": [
"-y",
"@gemachdao/gdex-mcp-server"
]
}
}
}
Frequently asked questions
Armor Crypto MCP is categorized under Finance & Fintech and uses a local stdio subprocess. GDEX Trading belongs to Finance & Fintech and uses a local stdio subprocess. Pick Armor Crypto MCP for finance & fintech work and GDEX Trading for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Armor Crypto MCP is listed as a paid service. Auth: api key required. GDEX Trading has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add armorwallet-armor-crypto-mcp and gdex-trading as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Armor Crypto MCP has a quality signal of 51/100 (Good) with 4 views, 0 installs and 178 GitHub stars. GDEX Trading has 37/100 (Fair) with 0 views, 0 installs and 4 GitHub stars.