21e14 MCP Server

@21e14/mcp-server npm v1.0.5 Source verified

Published by xcp — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for the Counterparty token protocol on Bitcoin. Query balances, assets, orders, dispensers, and compose/sign/broadcast transactions.

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/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 = 97/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 − 3 = 97. 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

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

medium Hardcoded egress to an external endpoint (dist/tools/bitcoin.js)MTC-SRC-003

In the server's implementation (`dist/tools/bitcoin.js:54`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const response = await fetch('https://mempool.space/api/v1/fees/recommended', { signal: AbortSignal.timeout

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/tools/bitcoin.js

Tools 49

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

  • api_requestno sensitive capability
  • broadcast_transactionno sensitive capability
  • compose_attachno sensitive capability
  • compose_broadcastno sensitive capability
  • compose_btcpayno sensitive capability
  • compose_cancelno sensitive capability
  • compose_destroyno sensitive capability
  • compose_detachno sensitive capability
  • compose_dispenseno sensitive capability
  • compose_dispenserno sensitive capability
Show 39 more tools ↓
  • compose_dividendno sensitive capability
  • compose_fairmintno sensitive capability
  • compose_fairminterno sensitive capability
  • compose_issuanceno sensitive capability
  • compose_movetoutxono sensitive capability
  • compose_mpmano sensitive capability
  • compose_orderno sensitive capability
  • compose_sendno sensitive capability
  • compose_sweepno sensitive capability
  • compose_xcp420_fairminterno sensitive capability
  • decode_transactionno sensitive capability
  • get_address_dispensersno sensitive capability
  • get_address_ordersno sensitive capability
  • get_address_transactionsno sensitive capability
  • get_asset_balancesno sensitive capability
  • get_asset_infono sensitive capability
  • get_asset_ordersno sensitive capability
  • get_assetsno sensitive capability
  • get_balanceno sensitive capability
  • get_balancesno sensitive capability
  • get_dispenserno sensitive capability
  • get_dispensersno sensitive capability
  • get_dispensers_by_assetno sensitive capability
  • get_dispensesno sensitive capability
  • get_dividendsno sensitive capability
  • get_fee_estimateno sensitive capability
  • get_issuancesno sensitive capability
  • get_latest_blockno sensitive capability
  • get_orderno sensitive capability
  • get_order_matchesno sensitive capability
  • get_ordersno sensitive capability
  • get_orders_by_pairno sensitive capability
  • get_owned_assetsno sensitive capability
  • get_sendsno sensitive capability
  • get_server_infono sensitive capability
  • get_transactionno sensitive capability
  • get_utxo_balancesno sensitive capability
  • sign_and_broadcastno sensitive capability
  • unpack_transactionno 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.5 latest A 97/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 · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/21e14-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/21e14-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/21e14-mcp-server"><img src="https://mcptrustchecker.com/registry/21e14-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/21e14-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 @21e14/mcp-server --online

Use the free API → How scoring works

More in Business & CRM