Armor Crypto MCP Server

armor-crypto-mcp PyPI v0.2.1

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP to interface with multiple blockchains, staking, DeFi, swap, bridging, wallet management, DCA, Limit Orders, Coin Lookup, Tracking and more

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 95/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 5 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 37

Each tool and what it can reach — statically extracted from the published source.

  • get_token_candle_datareads sensitive data
  • add_wallets_to_groupno sensitive capability
  • archive_wallet_groupno sensitive capability
  • archive_walletsno sensitive capability
  • calculate_token_conversionno sensitive capability
  • calculatorno sensitive capability
  • cancel_dca_orderno sensitive capability
  • cancel_orderno sensitive capability
  • create_dca_orderno sensitive capability
  • create_groupsno sensitive capability
Show 27 more tools ↓
  • create_orderno sensitive capability
  • create_walletno sensitive capability
  • get_all_ordersno sensitive capability
  • get_all_walletsno sensitive capability
  • get_armor_mcp_versionno sensitive capability
  • get_current_timeno sensitive capability
  • get_stake_balancesno sensitive capability
  • get_top_trending_tokensno sensitive capability
  • get_wallet_token_balanceno sensitive capability
  • list_dca_ordersno sensitive capability
  • list_groupsno sensitive capability
  • list_single_groupno sensitive capability
  • remove_wallets_from_groupno sensitive capability
  • rename_walletsno sensitive capability
  • search_official_token_addressno sensitive capability
  • search_token_detailsno sensitive capability
  • send_key_to_telegramno sensitive capability
  • stake_quoteno sensitive capability
  • stake_transactionno sensitive capability
  • swap_quoteno sensitive capability
  • swap_transactionno sensitive capability
  • transfer_tokensno sensitive capability
  • unarchive_wallet_groupno sensitive capability
  • unarchive_walletsno sensitive capability
  • unstake_quoteno sensitive capability
  • unstake_transactionno sensitive capability
  • wait_a_momentno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.2.1 latest A 95/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/armor-crypto-mcp/badge.svg)](https://mcptrustchecker.com/registry/armor-crypto-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/armor-crypto-mcp"><img src="https://mcptrustchecker.com/registry/armor-crypto-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/armor-crypto-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan armor-crypto-mcp --online --registry pypi

Use the free API → How scoring works

More in AI & Agents