Zetrix MCP Server

zetrix-mcp-server npm v1.0.27

Published by zetrix-chain — 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.

MCP server for Zetrix blockchain with 55 tools - HTTP RPC, WebSocket (protobuf), SDK transactions, Crypto, and smart contract development. Supports stdio and HTTP transport.

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/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
High
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 = 93/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 − 7 = 93. 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
−6 capability blast radius (high) — client exposure if the model is manipulated
−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 1

high Shell/command execution in server code (dist/index.js)MTC-SRC-002

In the server's implementation (`dist/index.js:2038`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: cSync } = await import("child_process"); try { const cwd = workingDirectory

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/index.js

Tools 55

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

  • zetrix_contract_get_token_standardreads sensitive data
  • zetrix_call_contractno sensitive capability
  • zetrix_check_healthno sensitive capability
  • zetrix_contract_generate_advancedno sensitive capability
  • zetrix_contract_get_chain_functionsno sensitive capability
  • zetrix_contract_get_structure_guideno sensitive capability
  • zetrix_contract_get_testing_guideno sensitive capability
  • zetrix_contract_get_utils_functionsno sensitive capability
  • zetrix_contract_init_dev_environmentno sensitive capability
  • zetrix_create_keypairno sensitive capability
Show 45 more tools ↓
  • zetrix_crypto_decrypt_keyno sensitive capability
  • zetrix_crypto_encrypt_keyno sensitive capability
  • zetrix_crypto_generate_keypairno sensitive capability
  • zetrix_crypto_get_addressno sensitive capability
  • zetrix_crypto_get_public_keyno sensitive capability
  • zetrix_crypto_signno sensitive capability
  • zetrix_crypto_validate_keyno sensitive capability
  • zetrix_crypto_verifyno sensitive capability
  • zetrix_get_accountno sensitive capability
  • zetrix_get_account_assetsno sensitive capability
  • zetrix_get_account_baseno sensitive capability
  • zetrix_get_account_metadatano sensitive capability
  • zetrix_get_balanceno sensitive capability
  • zetrix_get_blockno sensitive capability
  • zetrix_get_latest_blockno sensitive capability
  • zetrix_get_ledgerno sensitive capability
  • zetrix_get_transactionno sensitive capability
  • zetrix_get_transaction_blobno sensitive capability
  • zetrix_get_transaction_cacheno sensitive capability
  • zetrix_get_transaction_historyno sensitive capability
  • zetrix_multi_queryno sensitive capability
  • zetrix_sdk_activate_accountno sensitive capability
  • zetrix_sdk_call_contractno sensitive capability
  • zetrix_sdk_create_accountno sensitive capability
  • zetrix_sdk_create_contractno sensitive capability
  • zetrix_sdk_create_logno sensitive capability
  • zetrix_sdk_get_balanceno sensitive capability
  • zetrix_sdk_get_nonceno sensitive capability
  • zetrix_sdk_invoke_contractno sensitive capability
  • zetrix_sdk_invoke_contract_by_assetno sensitive capability
  • zetrix_sdk_is_activatedno sensitive capability
  • zetrix_sdk_issue_assetno sensitive capability
  • zetrix_sdk_send_assetno sensitive capability
  • zetrix_sdk_send_gasno sensitive capability
  • zetrix_sdk_set_metadatano sensitive capability
  • zetrix_sdk_set_privilegeno sensitive capability
  • zetrix_sdk_upgrade_contractno sensitive capability
  • zetrix_submit_transactionno sensitive capability
  • zetrix_test_transactionno sensitive capability
  • zetrix_versionno sensitive capability
  • zetrix_ws_connectno sensitive capability
  • zetrix_ws_disconnectno sensitive capability
  • zetrix_ws_statusno sensitive capability
  • zetrix_ws_submit_transactionno sensitive capability
  • zetrix_ws_subscribe_txno 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
v1.0.27 latest A 93/100 1 1.13.0 2026-09-07

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

Use the free API → How scoring works

More in Finance & Commerce