mcpField
T
ton-nfts

ton-nfts

github.com/ton-orgOther10112 installsUpdated 25w ago
Repository

About ton-nfts

ton-nfts is a skill for viewing and transferring NFTs on the TON blockchain. It guides an agent through NFT lookup, transaction simulation, and user confirmation before a transfer.

Key features

  1. 01List NFTs in the active wallet
  2. 02Look up NFTs by address
  3. 03View NFT details
  4. 04Transfer NFTs with confirmation
  5. 05Simulate transactions before sending

Use cases

  1. 01Review NFTs held in the active wallet
  2. 02Check details for a known NFT address
  3. 03Send an NFT after user approval
  4. 04Preview expected effects and fees

MCP support

The skill describes MCP tools for listing, looking up, viewing, sending, and simulating TON NFT transactions. MCP clients can use these tools to perform the stated NFT workflows.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ton-org/skills --skill ton-nfts

After installing, type/ton-nftsin Claude Code to confirm it loaded.

Details

From the project README

TON NFT Operations

View and transfer NFTs on the TON blockchain.

MCP Tools

ToolRequiredOptional
get_nfts—limit, offset, walletSelector
get_nfts_by_addressaddresslimit, offset
get_nftnftAddress—
send_nftnftAddress, toAddresscomment, walletSelector
emulate_transactionmessagesvalidUntil

Workflows

List My NFTs
  1. Call get_nfts to list NFTs in the active wallet
  2. Use limit and offset for pagination
View NFT Details
  1. Call get_nft with the nftAddress
Send an NFT
  1. Call get_nfts to find the NFT address if the user doesn't have it
  2. Ask one short yes/no confirmation before transferring the NFT
  3. Call send_nft with nftAddress and toAddress
  4. Poll get_transaction_status with the returned normalizedHash until status is completed or failed (see ton-balance skill)

Notes

  • Use emulate_transaction to dry-run any transaction before sending — it returns expected balance changes, fees, and high-level actions so you can verify the outcome
  • Always confirm with the user before transferring an NFT; prefer the host client's structured confirmation UI when available, otherwise accept natural-language yes/no and do not require a fixed confirmation phrase
  • If no wallet is configured, use the ton-create-wallet skill first

Comments

Markdown supported