Zano MCP Server

zano-mcp npm v0.1.3

Published by pravaga — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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
Minimal
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 = 99/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 − 1 = 99. 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
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 46

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

  • accept_swapno sensitive capability
  • apply_orderno sensitive capability
  • burn_assetno sensitive capability
  • cancel_orderno sensitive capability
  • confirm_tradeno sensitive capability
  • create_orderno sensitive capability
  • create_swap_proposalno sensitive capability
  • deploy_assetno sensitive capability
  • dex_authenticateno sensitive capability
  • emit_assetno sensitive capability
Show 36 more tools ↓
  • get_active_tradeno sensitive capability
  • get_addressno sensitive capability
  • get_alias_by_addressno sensitive capability
  • get_asset_infono sensitive capability
  • get_assets_listno sensitive capability
  • get_balanceno sensitive capability
  • get_block_by_hashno sensitive capability
  • get_block_by_heightno sensitive capability
  • get_block_detailsno sensitive capability
  • get_heightno sensitive capability
  • get_last_blockno sensitive capability
  • get_mining_historyno sensitive capability
  • get_my_ordersno sensitive capability
  • get_network_infono sensitive capability
  • get_order_bookno sensitive capability
  • get_pool_infono sensitive capability
  • get_recent_transactionsno sensitive capability
  • get_swap_infono sensitive capability
  • get_trading_pairno sensitive capability
  • get_transactionno sensitive capability
  • get_transactionsno sensitive capability
  • get_wallet_statusno sensitive capability
  • make_integrated_addressno sensitive capability
  • remove_asset_from_whitelistno sensitive capability
  • resolve_aliasno sensitive capability
  • save_walletno sensitive capability
  • search_blockchainno sensitive capability
  • search_transactionsno sensitive capability
  • sign_messageno sensitive capability
  • split_integrated_addressno sensitive capability
  • sweep_belowno sensitive capability
  • transferno sensitive capability
  • transfer_asset_ownershipno sensitive capability
  • update_assetno sensitive capability
  • validate_signatureno sensitive capability
  • whitelist_assetno 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.1.3 latest A 99/100 0 1.9.0 2026-07-24

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 · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/zano-mcp/badge.svg)](https://mcptrustchecker.com/registry/zano-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/zano-mcp"><img src="https://mcptrustchecker.com/registry/zano-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/zano-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 zano-mcp --online

Use the free API → How scoring works

More in Developer Tools