プロトタイプ · プレビュー版:公式レジストリのすべてのサーバーを掲載し、30分ごとに同期しています。レビューとアカウント機能は今後のステップで始まります。
PopNx MCPAIを使う人のためのMCPサーバー · やさしい言葉で解説

GoTRON MCP

作者:fbsobreiraバージョン 0.4.2i★ –iパソコンでもクラウドでも
レジストリ名io.github.fbsobreira/gotron-mcp

インストール

概要

作者による説明(英語の原文)

TRON blockchain: accounts, TRC20 tokens, staking, contracts, resources and transaction builders

PopNx MCPの3つの柱

この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。

できること

このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。

  • 接続方法: パソコンでもクラウドでも
  • トランスポート: stdio, Streamable HTTP
  • カテゴリ: その他
  • 入力が必要なもの:GOTRON_NODE_API_KEY

インストール

使っているAIアプリを選んで、設定をコピーしてください。

インストールの前に

「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。

必要なもの

どのアプリを使っていますか?

上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。

ウェブ、デスクトップ、モバイルのClaudeで使えます:

  1. Settings → Connectors を開く
  2. Add custom connector を押す
  3. 下のアドレスを貼り付けて Add を押す
  4. サインインを求められたら、作者のサービスにサインインする
SettingsConnectors1+ Add2https://…3
https://mcp.gotron.sh/mcp

または、パソコンで動かす

Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます

{
  "mcpServers": {
    "gotron": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "GOTRON_MCP_NETWORK",
        "-e",
        "GOTRON_NODE_API_KEY",
        "-e",
        "GOTRON_MCP_NODE",
        "ghcr.io/fbsobreira/gotron-mcp:0.4.2",
        "--transport",
        "stdio"
      ],
      "env": {
        "GOTRON_MCP_NETWORK": "your-value",
        "GOTRON_NODE_API_KEY": "your-value",
        "GOTRON_MCP_NODE": "your-value"
      }
    }
  }
}

ターミナルでこれを実行します

claude mcp add --transport http gotron https://mcp.gotron.sh/mcp

または、パソコンで動かす

claude mcp add gotron --env GOTRON_MCP_NETWORK=your-value --env GOTRON_NODE_API_KEY=your-value --env GOTRON_MCP_NODE=your-value -- docker run -i --rm -e GOTRON_MCP_NETWORK -e GOTRON_NODE_API_KEY -e GOTRON_MCP_NODE ghcr.io/fbsobreira/gotron-mcp:0.4.2 --transport stdio

動かす前に、空欄の値を入力してください。

Cursorで開く

または、設定を自分でコピーする

プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます

{
  "mcpServers": {
    "gotron": {
      "url": "https://mcp.gotron.sh/mcp"
    }
  }
}

または、パソコンで動かす

Cursorで開く

または、設定を自分でコピーする

プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます

{
  "mcpServers": {
    "gotron": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "GOTRON_MCP_NETWORK",
        "-e",
        "GOTRON_NODE_API_KEY",
        "-e",
        "GOTRON_MCP_NODE",
        "ghcr.io/fbsobreira/gotron-mcp:0.4.2",
        "--transport",
        "stdio"
      ],
      "env": {
        "GOTRON_MCP_NETWORK": "your-value",
        "GOTRON_NODE_API_KEY": "your-value",
        "GOTRON_MCP_NODE": "your-value"
      }
    }
  }
}

ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。

VS Codeで開く

または、設定を自分でコピーする

プロジェクトの .vscode/mcp.json に貼り付けます

{
  "servers": {
    "gotron": {
      "type": "http",
      "url": "https://mcp.gotron.sh/mcp"
    }
  }
}

または、パソコンで動かす

VS Codeで開く

または、設定を自分でコピーする

プロジェクトの .vscode/mcp.json に貼り付けます

{
  "servers": {
    "gotron": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "GOTRON_MCP_NETWORK",
        "-e",
        "GOTRON_NODE_API_KEY",
        "-e",
        "GOTRON_MCP_NODE",
        "ghcr.io/fbsobreira/gotron-mcp:0.4.2",
        "--transport",
        "stdio"
      ],
      "env": {
        "GOTRON_MCP_NETWORK": "your-value",
        "GOTRON_NODE_API_KEY": "your-value",
        "GOTRON_MCP_NODE": "your-value"
      }
    }
  }
}

ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。

ChatGPTがつなげるのは、インターネット上のサーバーだけです:

  1. ウェブ版のChatGPTを開き → Settings → Connectors (Apps)
  2. Create または Add を押す(プランによっては、先に Advanced で Developer mode をオンにする必要があります)
  3. 下のアドレスを貼り付け、名前を付けて保存する
  4. サインインを求められたら、作者のサービスにサインインする
SettingsConnectors1+ Create2https://…3
https://mcp.gotron.sh/mcp

メニューの名前は、プランや時期によって少し違うことがあります。

選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。

自分で入力する値

  • GOTRON_MCP_NETWORK env
    TRON network to connect to
  • GOTRON_NODE_API_KEY 秘密 env
    TronGrid API key for higher rate limits
  • GOTRON_MCP_NODE env
    TRON gRPC node address (default: the public node for the network)

この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。

できること

ツールの名前と説明は、サーバーが2026年11月7日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。

  • analyze_account

    Comprehensive account overview: balance, resources, staking, voting, permissions, and delegations in a single call

  • analyze_transfer_cost

    Estimate the cost of a TRX or TRC20 transfer: energy, bandwidth, and TRX burn options

  • decode_abi_output

    Decode ABI-encoded output hex from a contract call. Handles return values, revert reasons (Error(string)), and panic codes (Panic(uint256)).

  • delegate_resource

    Delegate energy or bandwidth to another address (Stake 2.0). Returns unsigned transaction hex for signing.

  • estimate_energy

    Estimate energy cost for a smart contract call. Requires a full node with vm.supportConstant=true and vm.estimateEnergy=true; falls back to secondary node if primary does not support it.

  • estimate_trc20_energy

    Estimate energy cost for a TRC20 transfer without creating a transaction. Dry-runs the transfer to check energy requirements.

  • freeze_balance

    Stake TRX for energy or bandwidth (Stake 2.0). Returns unsigned transaction hex for signing.

  • get_account

    Get TRON account balance and details including TRX balance, bandwidth, energy, frozen resources, and account type

  • get_account_permissions

    Get the permission structure of a TRON account including owner, active, and witness permissions with multi-sig keys and thresholds

  • get_account_resources

    Get energy and bandwidth usage and limits for a TRON account

  • get_bandwidth_prices

    Get current and historical bandwidth prices on the TRON network

  • get_block

    Get a TRON block by number or latest. Use include_transactions to get transaction details with decoded contract data (sender, receiver, amounts) and pagination.

  • get_chain_parameters

    Get TRON network node info and current energy/bandwidth prices

  • get_contract_abi

    Get the ABI of a smart contract on TRON. Automatically resolves proxy contracts (ERC-1967). Note: many TRON contracts are deployed without on-chain ABI — if empty, check TronScan for verified source code.

  • get_contract_events

    Get decoded events emitted by a smart contract via TronGrid REST API. Returns a compact summary per event. Use a small limit and paginate with fingerprint to control response size

  • get_delegatable_amount

    Get the maximum amount of energy or bandwidth an account can still delegate

  • get_delegated_resources

    Get resources delegated to and from an account (Stake 2.0 delegation info)

  • get_energy_prices

    Get current and historical energy prices on the TRON network

  • get_network

    Get current MCP server connection info: network name, node address, and latest block

  • get_pending_by_address

    Get pending transactions for a specific address from the mempool

  • get_pending_transactions

    List pending transaction IDs and pool size from the mempool

  • get_pq_capabilities

    Report which TIP-899 post-quantum signature schemes the connected node enables and this build can sign (FN-DSA-512 needs the gotron-mcp-pq build). TIP-899 is a draft live only on Nile. can_sign reflects the node and this build; signing also needs local mode with a keystore.

  • get_proposal

    Get full details of a governance proposal by ID, including the complete list of approval addresses.

  • get_token_price

    Get the current USD price of TRX or a TRC20 token. Uses CoinGecko with caching.

  • get_transaction

    Get transaction details by transaction ID

  • get_transaction_history

    Get transaction history for a TRON address via TronGrid REST API. Returns a compact summary per transaction. Use a small limit and paginate with fingerprint to control response size

  • get_trc20_allowance

    Query how many tokens a spender is approved to transfer on behalf of the owner. Flags unlimited approvals as high risk.

  • get_trc20_balance

    Get TRC20 token balance for an account

  • get_trc20_token_info

    Get TRC20 token metadata (name, symbol, decimals, total supply)

  • get_trc20_transfers

    Get TRC20 token transfer history for a TRON address via TronGrid REST API. Returns a compact summary per transfer with token info. Use a small limit and paginate with fingerprint to control response size

  • is_transaction_pending

    Check if a specific transaction is still in the pending pool (mempool)

  • list_contract_methods

    Get a human-readable summary of a smart contract's methods with signatures, inputs, outputs, and mutability. Auto-resolves proxy contracts.

  • list_proposals

    List governance proposals on the TRON network with pagination support. Returns a compact summary per proposal (use get_proposal for full details including approval addresses). Newest first by default.

  • list_witnesses

    List super representatives (witnesses) on the TRON network with pagination support.

  • revoke_approval

    Build unsigned transaction to revoke a TRC20 token approval (sets allowance to 0)

  • transfer_trc20

    Create an unsigned TRC20 token transfer transaction. Returns transaction hex for signing.

  • transfer_trx

    Create an unsigned TRX transfer transaction. Returns transaction hex for signing.

  • trigger_constant_contract

    Call a read-only (view/pure) smart contract method. No transaction created, no fees. Returns decoded result. Provide either method+params OR data (pre-packed calldata).

  • trigger_contract

    Call a smart contract method. Returns unsigned transaction hex for signing. Provide either method+params OR data (pre-packed calldata).

  • undelegate_resource

    Reclaim previously delegated energy or bandwidth (Stake 2.0). Returns unsigned transaction hex for signing.

  • unfreeze_balance

    Unstake TRX (Stake 2.0). Returns unsigned transaction hex for signing. Note: unstaked TRX has a 14-day withdrawal period.

  • validate_address

    Validate a TRON address and convert supported inputs to TRON base58/hex. Accepts base58 (T...), TRON hex (41...), or Ethereum/EVM format (0x...).

  • vote_witness

    Vote for super representatives. Returns unsigned transaction hex for signing. Requires staked TRX (1 TRX staked = 1 vote).

  • withdraw_expire_unfreeze

    Withdraw TRX that has completed the 14-day unstaking period (Stake 2.0). Returns unsigned transaction hex for signing.

基本チェックi

誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月7日にチェック

  • ✓ 合格

    作者とリポジトリが一致

    レジストリ名は、リポジトリを所有するGitHubアカウント fbsobreira で確認済みです

  • … 未チェック

    今もメンテナンスされている

    このリポジトリはまだGitHubから読み取っていません

  • … 未チェック

    ライセンスがある

    このリポジトリはまだGitHubから読み取っていません

  • ✓ 合格

    エンドポイントが応答する

    788ミリ秒で応答(HTTP 200)

  • – 対象外

    OAuthでサインイン

    サインイン不要

  • ✓ 合格

    ツールの説明に隠れた指示がない

    44件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした

その他のほかのサーバーとの比較i

  • このカテゴリのほかの32696件のうち0%よりスターが多い
  • このカテゴリのほかの32696件のうち77%より最近レジストリに公開
  • 基本チェックの結果が、このカテゴリのほかの32696件のうち100%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

よくある質問

GoTRON MCPは安全ですか?

当てはまる基本チェック3項目のうち3項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。

どんなキーやコードが必要ですか?

入力が必要なもの:GOTRON_NODE_API_KEY

パソコンで動きますか、それともクラウドですか?

どちらでも使えます。パソコンにインストールしても、クラウド版につないでもかまいません。

今もメンテナンスされていますか?

GitHubリポジトリの最終更新は–、最新バージョン(0.4.2)がレジストリに届いたのは10 日前です。

どのアプリで使えますか?

Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URLでつながるので、リモートMCPサーバーに対応したアプリ(開発者モードのChatGPTなど)でも使えます。

代わりに使えるものは?

同じカテゴリには:Spec Driven Development, Remote Desktop Commander, LexPact UK Contracts

代わりの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i

Remote Desktop Commander

作者:desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

クラウドで動く★ 211一昨日更新
インストール

作者のREADME

READMEを開く

作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。

GoTRON MCP Server

MCP server for TRON blockchain — let AI agents query balances, tokens, blocks, and build transactions.

Built on the GoTRON SDK and the Model Context Protocol.

Two Modes

Local ModeHosted Mode
TransportstdioStreamable HTTP
Read toolsAllAll
Transaction buildersAll (unsigned tx hex)All (unsigned tx hex)
Sign/BroadcastOpt-in via keystore passphraseDisabled
InstallRequiredZero install

Install

Go Install
go install github.com/fbsobreira/gotron-mcp/cmd/gotron-mcp@latest
Homebrew
brew install fbsobreira/tap/gotron-mcp
curl
curl -fsSL gotron.sh/install-mcp | sh
Docker
docker run -p 8080:8080 ghcr.io/fbsobreira/gotron-mcp

The image starts the HTTP transport. For stdio, append --transport stdio:

docker run -i --rm ghcr.io/fbsobreira/gotron-mcp --transport stdio
MCP Registry

Published to the MCP Registry as io.github.fbsobreira/gotron-mcp on each stable release tag (vX.Y.Z), from v0.4.1, with the Docker image (stdio) and the hosted endpoint.

Hosted (zero install)

Connect directly to https://mcp.gotron.sh/mcp — no installation needed.

Claude Code plugin

The gotron plugin bundles the hosted server with skills for USDT transfers and energy estimates. The gotron-local plugin runs the gotron-mcp binary locally and supports keystore signing.

Public marketplace installation is not available yet. To connect today, use the Claude Code MCP setup below. Plugin source and configuration details are in the directories linked above.

Claude Desktop Configuration

Local mode
{

"mcpServers": { "gotron": { "command": "gotron-mcp", "args": ["--network", "mainnet"], "env": { "GOTRON_NODE_API_KEY": "your-trongrid-api-key" } } } }

Local mode with keystore signing
{

"mcpServers": { "gotron": { "command": "gotron-mcp", "args": ["--network", "mainnet"], "env": { "GOTRON_NODE_API_KEY": "your-trongrid-api-key", "GOTRON_MCP_KEYSTORE_PASSPHRASE": "your-keystore-passphrase" } } } }

Hosted mode (zero install)
{

"mcpServers": { "gotron": { "url": "https://mcp.gotron.sh/mcp" } } }

Claude Code

Choose one of the following setup options.

Project-wide local server:

claude mcp add gotron --scope project -- gotron-mcp --network mainnet

User-wide local server with keystore signing:

If a project-scoped gotron entry already exists, remove it first with claude mcp remove gotron --scope project. For a local-scoped entry, use claude mcp remove gotron --scope local. Check the selected entry with claude mcp get gotron: local and project entries take precedence over user entries, and their settings are not combined. See Claude Code's scope precedence.

Save an environment-variable reference rather than the passphrase itself. Keep the single quotes so your shell does not expand the reference while registering the server:

claude mcp add gotron --scope user -e 'GOTRON_MCP_KEYSTORE_PASSPHRASE=${GOTRON_MCP_KEYSTORE_PASSPHRASE:-}' -- gotron-mcp --network mainnet

Then launch Claude from Bash or Zsh with a hidden passphrase prompt:

(

set +x printf 'Keystore passphrase: ' IFS= read -r -s GOTRON_MCP_KEYSTORE_PASSPHRASE || exit 1 printf '\n' export GOTRON_MCP_KEYSTORE_PASSPHRASE claude )

The subshell limits the exported value to that Claude session. The prompt keeps the passphrase out of shell history and command-line arguments; it is still available in the environment of Claude and its MCP server. Repeat the prompt when starting a new signing session. Without a supplied passphrase, the reference expands to an empty value and wallet/signing tools stay disabled.

If you previously registered a literal passphrase with -e, it was stored in plain text in ~/.claude.json and may also remain in shell history. Remove the old user-scoped entry with claude mcp remove gotron --scope user, register it again using the reference above, and remove the old history entry. See Claude Code's environment-variable expansion documentation.

User-wide local server without keystore configuration:

claude mcp add gotron --scope user -- gotron-mcp --network mainnet

Hosted server (zero install):

claude mcp add gotron --scope user --transport http https://mcp.gotron.sh/mcp

Available Tools

Read-Only (both modes)
ToolDescription
get_accountGet account balance, bandwidth, energy, and details
get_account_resourcesGet energy/bandwidth usage and limits
get_trc20_balanceGet TRC20 token balance for an account
get_trc20_token_infoGet TRC20 token name, symbol, and decimals
analyze_transfer_costEstimate TRX or TRC20 transfer costs, including account activation fees for new TRX recipients
get_blockGet block by number or latest
get_transactionGet transaction details by ID
list_witnessesList all super representatives
get_contract_abiGet smart contract ABI
estimate_energyEstimate energy cost for a contract call
trigger_constant_contractCall read-only (view/pure) smart contract method
decode_abi_outputDecode ABI-encoded output or revert reasons from contract calls
list_contract_methodsGet human-readable summary of contract methods
get_chain_parametersGet network parameters
validate_addressValidate a TRON address
get_energy_pricesGet energy price history
get_bandwidth_pricesGet bandwidth price history
list_proposalsList governance proposals
get_networkGet current network connection info
get_pq_capabilitiesReport node and build support for post-quantum (TIP-899) signing
Transaction Builders (both modes)
ToolDescription
transfer_trxBuild unsigned TRX transfer
transfer_trc20Build unsigned TRC20 token transfer
freeze_balanceBuild unsigned stake TRX for energy/bandwidth (Stake 2.0)
unfreeze_balanceBuild unsigned unstake TRX (Stake 2.0)
vote_witnessBuild unsigned vote for super representatives
trigger_contractBuild unsigned smart contract call
Sign & Broadcast (local mode + keystore)
ToolDescription
sign_transactionSign transaction using local keystore
broadcast_transactionBroadcast signed transaction to network
Post-quantum signing (TIP-899, Nile)

create_wallet(name, key_type?) accepts ecdsa (default), ml_dsa_44 or fn_dsa_512; list_wallets and signing results report key_type. sign_transaction, sign_and_broadcast, sign_and_confirm and request_limit_override accept PQ wallets with the same policy limits, Telegram approval and elicitation as ECDSA wallets.

  • TIP-899 is a draft, live only on Nile (grpc.nile.trongrid.io:50051); governance switches each scheme on or off and mainnet reports none. Use get_pq_capabilities to check the node and this build.
  • Before any policy check or approval, a PQ signature requires that the node has the scheme enabled and that the wallet's address is a key of the transaction's permission (permission_id) on the owner account. A fresh PQ address must receive TRX first.
  • PQ keys are stored encrypted with GOTRON_MCP_KEYSTORE_PASSPHRASE under /pq-keys/ / (wallet-cli compatible, same layout as tronctl). Point --keystore-dir at a tronctl config root (e.g. ~/.tronctl) to reuse its keys; the passphrase must match their password. Wallet names are unique across ECDSA and PQ wallets; list_wallets flags duplicate_name: true and such a wallet cannot sign until one copy is renamed.
  • The signature goes into pq_auth_sig (txid unchanged); a transaction carries at most 5 signatures, ECDSA and PQ combined. PQ transactions are about 10-22x larger than ECDSA ones (roughly 10x for FN-DSA-512, 22x for ML-DSA-44), so they use more bandwidth.
  • ML-DSA-44 is pure Go and works in every build. FN-DSA-512 (Falcon-512, currently enabled on Nile) needs a build with -tags falcon, CGO and liboqs installed via pkg-config: CGO_ENABLED=1 go build -tags falcon ./cmd/gotron-mcp. Without it, FN-DSA create/sign returns an error pointing to the gotron-mcp-pq build; release binaries for it are planned (GOT-97).
  • Not supported yet: adding a PQ key to an existing account's permissions from MCP (GOT-98; use tronctl or the SDK guide) and co-signing one transaction with several MCP wallets (GOT-99).

Configuration

FlagEnv VarDefaultDescription
--nodeGOTRON_MCP_NODE(per network)TRON gRPC node address
--api-keyGOTRON_NODE_API_KEY—TronGrid API key
--networkGOTRON_MCP_NETWORKmainnetNetwork: mainnet, nile, shasta
--transport—stdioTransport: stdio, http
--port—8080HTTP server port
--bind—127.0.0.1HTTP server bind address
--fallback-nodeGOTRON_MCP_FALLBACK_NODE—Fallback gRPC node (auto-failover)
--keystore-dirGOTRON_MCP_KEYSTORE_DIR~/.gotron-mcp/walletsWallet directory
--keystore-passGOTRON_MCP_KEYSTORE_PASSPHRASE—Keystore passphrase; wallet and sign tools are registered only when set
--tls—falseUse TLS for gRPC connection (default: plaintext)
Network Presets
NetworkDefault Node
mainnetgrpc.trongrid.io:50051
nilegrpc.nile.trongrid.io:50051
shastagrpc.shasta.trongrid.io:50051

Explicit --node overrides network presets.

Contract reads require a node with vm.supportConstant = true. If a node reports that constant execution is unsupported, reads try --fallback-node when configured. TRC20 reads also use the fallback for empty results, since token reads require return data. General contract simulations can succeed without return data. The fallback must serve the same network. This fallback applies per call, independently of block health checks; contract reverts are returned as errors.

For TRX transfers to unactivated recipients, analyze_transfer_cost reads the account creation fees and bandwidth multiplier from chain parameters. Only staked or delegated bandwidth can cover account creation; free bandwidth cannot. If recipient activation or the required fee parameters cannot be determined, the tool returns an error instead of quoting zero.

Security

  • The server never stores or manages private keys directly
  • All write tools return unsigned transaction hex — the user decides how to sign
  • Keystore signing is opt-in: wallet and sign tools are reg

冒頭だけを表示しています。続きはリポジトリで読めます

PopNxに聞く