Virtuals Protocol Acp
Virtual-Protocol/openclaw-acp
Hire specialised agents to handle any task — data analysis, trading, content generation, research, on-chain operations, 3D printing, physical goods, gift delivery, and more.
Scan TRON tokens for total supply, market cap, price, rating, launch time, holders.
Install Tronscan Token Scanner
$ npx skills add LeoYeAI/openclaw-master-skills --skill tronscan-token-scanner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills tronscan-token-scanner --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tronscan-token-scanner .claude/skills/tronscan-token-scanner && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "tronscan-token-scanner" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/tronscan-token-scanner into .claude/skills/tronscan-token-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tronscan-token-scanner", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/tronscan-token-scannerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LeoYeAI/openclaw-master-skills --skill tronscan-token-scanner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills tronscan-token-scanner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/tronscan-token-scanner .agents/skills/tronscan-token-scanner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tronscan-token-scanner" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/tronscan-token-scanner into .agents/skills/tronscan-token-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tronscan-token-scanner", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill tronscan-token-scanner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills tronscan-token-scanner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/tronscan-token-scanner .cursor/skills/tronscan-token-scanner && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "tronscan-token-scanner" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/tronscan-token-scanner into .cursor/skills/tronscan-token-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tronscan-token-scanner", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LeoYeAI/openclaw-master-skills.git --path skills/tronscan-token-scanner--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LeoYeAI/openclaw-master-skills --skill tronscan-token-scanner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills tronscan-token-scanner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/tronscan-token-scanner .gemini/skills/tronscan-token-scanner && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "tronscan-token-scanner" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/tronscan-token-scanner into .gemini/skills/tronscan-token-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tronscan-token-scanner", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LeoYeAI/openclaw-master-skills tronscan-token-scannerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LeoYeAI/openclaw-master-skills --skill tronscan-token-scanner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/tronscan-token-scanner .github/skills/tronscan-token-scanner && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "tronscan-token-scanner" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/tronscan-token-scanner into .github/skills/tronscan-token-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tronscan-token-scanner", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill tronscan-token-scanner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills tronscan-token-scanner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/tronscan-token-scanner .opencode/skills/tronscan-token-scanner && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "tronscan-token-scanner" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/tronscan-token-scanner into .opencode/skills/tronscan-token-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tronscan-token-scanner", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
tronscan-token-scanner- GitHub stars
- 2.2k
- Token cost
- ~4.1k tokens
- SKILL.md length
- 1,930 words
- Files
- 2
- Skills in repo
- 1,235
- Repo updated
- First seen
- Licence
- MIT
At a glance
Scan TRON tokens for total supply, market cap, price, rating, launch time, holders.
- Works in 7 steps: TRX price, TRX supply, TRX market cap:… → Token Overview: Get name, symbol,… → Holder Analysis: Use… → …
- User asks how is this token
- SKILL.md covers Overview, Use Cases, MCP Server and Tools, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Tronscan Token Scanner is an agent skill from LeoYeAI/openclaw-master-skills. Scan TRON tokens for total supply, market cap, price, rating, launch time, holders. Includes TRX: TRX price, TRX supply, market cap, daily net change, and supply trend. Use when user asks "how is this token", "USDT price", "top holders", "TRX market cap", "token due diligence", "supply of contract address", or provides a token contract address. Do NOT use for token list or trending rankings (use tronscan-token-list or tronscan-data-insights).
Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `_meta.json`).
It sits in Business, Finance & HR, covering Smart contracts and Fundraising and pitch decks. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
When your agent uses it
- User asks how is this token
- Token due diligence
- Supply of contract address
- Provides a token contract address
Example prompts
- “how is this token”
- “USDT price”
- “top holders”
- “/tronscan-token-scanner”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- TRX price, TRX supply, TRX market cap: Use getTokenPrice (default token is TRX) for current price; use getFunds for real-time TRX supply…
- Token Overview: Get name, symbol, supply, holders, price via getTrc20TokenDetail or getTrc10TokenDetail.
- Holder Analysis: Use getTrc20TokenHolders / getTrc10TokenHolders for list; use getTokenPositionDistribution for concentration.
- Price & Valuation: Use getTokenPrice and detail tools for market cap.
- Supply: Use getTrc20TotalSupply for TRC20 supply/circulation.
- Launch Time: Available in token detail responses (creation/deploy time).
- NFT / Multi-token: Use getTrc721Inventory and getTrc1155Inventory for inventory.
What it can do on your machine
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
mcpdoc.tronscan.orgtronscan.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Tronscan Token Scanner loads about 4.1k tokens when it runs. Until then it costs about 117 tokens; SKILL.md has 1,930 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,930 words, ~4,055 tokens.
Download SKILL.mdSave it as
.claude/skills/tronscan-token-scanner/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- tronscan-token-scanner
- description
- Scan TRON tokens for total supply, market cap, price, rating, launch time, holders. Includes TRX: TRX price, TRX supply, market cap, daily net change, and supply trend. Use when user asks "how is this token", "USDT price", "top holders", "TRX market cap", "token due diligence", "supply of contract address", or provides a token contract address. Do NOT use for token list or trending rankings (use tronscan-token-list or tronscan-data-insights).
- metadata.author
- tronscan-mcp
- metadata.version
- 1.0
- metadata.mcp-server
- https://mcp.tronscan.org/mcp
Token Scanner
Overview
| Tool | Function | Use Case |
|---|---|---|
| getTokenPrice | Token price (default TRX) | TRX price or any token price |
| getFunds | TRX supply & market | TRX supply, market cap, burn |
| getTrxVolume | TRX history | TRX historical price, volume, market cap |
| getTurnover | TRX turnover | TRX turnover, supply, revenue, mint/burn |
| getTrxVolumeSourceList | TRX price sources | TRX price data source list |
| getTrc20TokenDetail | TRC20/721/1155 detail | Name, symbol, supply, holders, price |
| getTrc10TokenDetail | TRC10 detail | Name, issuer, supply, description |
| getTrc20TokenHolders | TRC20/721/1155 holders | Holder list, balance, share |
| getTrc10TokenHolders | TRC10 holders | TRC10 holder list |
| getTokenPositionDistribution | Position distribution | Holder count by balance range |
| getTrc20TotalSupply | TRC20 supply | Circulating / total supply |
| getTrc721Inventory | TRC721 inventory | NFT contract inventory |
| getTrc1155Inventory | TRC1155 inventory | Multi-token contract inventory |
| getToken10Transfers | TRC10 transfers | TRC10 token transfer records for an address |
| getTokenAnalysis | Token analysis | Token transfer and holder analysis data |
| getTokenAssetValueInfo | Asset value chart | Asset value change chart for a token in an account |
| getTokenBalanceFlow | Balance flow | Token balance flow records for an account |
| getTokenTransferAnalysis | Transfer amount | Transfer amount of core tokens on TRON |
| getTokenTvc | Token TVC | On-chain Total Value Captured (TVC) data |
| getTrc1155TokenInventory | TRC1155 token holders | Holder info for a specific token ID in TRC1155 |
| getTrc20TransferCount | TRC20 transfer count | Transfer count stats for a TRC20 token in an account |
| getTrc721Transfers | TRC721 transfers | Transfer history for a specific TRC721 NFT |
| getTrxTransfers | TRX transfers | TRX transfer records for an address |
Use Cases
- TRX price, TRX supply, TRX market cap: Use
getTokenPrice(default token is TRX) for current price; usegetFundsfor real-time TRX supply, market cap, and burn; usegetTrxVolumefor historical price/volume; usegetTurnoverfor supply, mint/burn, turnover. - Token Overview: Get name, symbol, supply, holders, price via
getTrc20TokenDetailorgetTrc10TokenDetail. - Holder Analysis: Use
getTrc20TokenHolders/getTrc10TokenHoldersfor list; usegetTokenPositionDistributionfor concentration. - Price & Valuation: Use
getTokenPriceand detail tools for market cap. - Supply: Use
getTrc20TotalSupplyfor TRC20 supply/circulation. - Launch Time: Available in token detail responses (creation/deploy time).
- NFT / Multi-token: Use
getTrc721InventoryandgetTrc1155Inventoryfor inventory.
MCP Server
- Prerequisite: TronScan MCP Guide
Tools
getTokenPrice
- API:
getTokenPrice— Get token price (default: TRX) - Use when: User asks for "TRX price", "current TRX price", or any token price.
- Note: Omit or pass default to get TRX price.
getFunds
- API:
getFunds— Get TRX real-time supply, market cap, and burn data - Use when: User asks for "TRX supply", "TRX circulation", "TRX market cap", or "TRX burn".
getTrxVolume
- API:
getTrxVolume— Get TRX historical price, volume, and market cap data - Use when: User asks for "TRX history", "TRX price history", or "TRX volume trend".
- Input: startTimestamp, endTimestamp, limit, source.
getTurnover
- API:
getTurnover— Get TRX turnover, supply, revenue, mint and burn statistics - Use when: User asks for "TRX turnover", "TRX mint/burn", or "TRX supply change".
- Input: from, start, end, type (as per API).
getTrxVolumeSourceList
- API:
getTrxVolumeSourceList— Get TRX price data source list - Use when: User asks for "TRX price source" or "where TRX price comes from".
getTrc20TokenDetail
- API:
getTrc20TokenDetail— Get TRC20/TRC721/TRC1155 token details (name, symbol, supply, holders, price, etc.) - Use when: User asks for "token info", "token details", or specifies a contract address.
- Input: Contract address (and token type if needed).
getTrc10TokenDetail
- API:
getTrc10TokenDetail— Get TRC10 token details (name, abbreviation, issuer, supply, description, etc.) - Use when: Token is TRC10 (native asset).
getTrc20TokenHolders / getTrc10TokenHolders
- API:
getTrc20TokenHolders— Get TRC20/TRC721/TRC1155 holder list (address, balance, share);getTrc10TokenHolders— Get TRC10 holder list - Use when: User asks for "token holders" or "top holders".
getTokenPositionDistribution
- API:
getTokenPositionDistribution— Get token position distribution (holder count and share by balance range) - Use when: User asks for "holder distribution" or "concentration".
getTrc20TotalSupply
- API:
getTrc20TotalSupply— Get TRC20 circulating supply and total supply - Use when: User asks for "supply" or "circulation" of a TRC20.
getToken10Transfers
- API:
getToken10Transfers— Get TRC10 token transfer records for an address - Use when: User asks for "TRC10 transfer history" for a specific token and address.
- Input:
address,trc10Id(both required); optional pagination and filters. Note: start+limit ≤ 10000.
getTokenAnalysis
- API:
getTokenAnalysis— Get analysis data for token transfers and holders - Use when: User asks for "token activity analysis", "transfer trends", or "holder stats over time".
- Input: Optional
token,startDay,endDay,type.
getTokenAssetValueInfo
- API:
getTokenAssetValueInfo— Get asset value change chart for a specific token in an account - Use when: User asks for "how has the value of my token changed" or "token asset value history".
- Input:
accountAddress,tokenAddress(both required); optionalstartTime,endTime.
getTokenBalanceFlow
- API:
getTokenBalanceFlow— Get balance flow change records for a token in an account - Use when: User asks for "token balance history" or "how my token balance changed over time".
- Input:
accountAddress,tokenAddress(both required); optionalendTime.
getTokenTransferAnalysis
- API:
getTokenTransferAnalysis— Get transfer amount of core tokens on TRON - Use when: User asks for "token transfer volume", "core token transfer analysis".
- Input: Optional
token,days.
getTokenTvc
- API:
getTokenTvc— Get token on-chain Total Value Captured (TVC) data (default last 7 days) - Use when: User asks for "token TVC", "on-chain value captured", or "token economic activity".
- Input: Optional
startTime,endTime.
getTrc1155TokenInventory
- API:
getTrc1155TokenInventory— Get holder info for a specific token ID in a TRC1155 contract - Use when: User asks for "who holds token ID X in this TRC1155 contract".
- Input:
contract,tokenId(both required); optionalstart,limit. Note: start+limit ≤ 10000.
getTrc20TransferCount
- API:
getTrc20TransferCount— Get transfer count statistics for a TRC20 token in an account - Use when: User asks for "how many times has this address transferred this token".
- Input:
accountAddress,tokenAddress(both required).
getTrc721Transfers
- API:
getTrc721Transfers— Get transfer history for a specific TRC721 NFT token - Use when: User asks for "NFT transfer history" for a specific contract and token ID.
- Input:
contract,tokenId(both required); optionalstart,limit. Note: start+limit ≤ 10000.
getTrxTransfers
- API:
getTrxTransfers— Get TRX transfer records for an address - Use when: User asks for "TRX transfer history", "TRX in/out", or "TRX transaction records".
- Input:
address(required); optionaldirection,startTimestamp,endTimestamp,start,limit. Note: start+limit ≤ 10000.
Token Risk Fields
TronScan token APIs return several risk-related fields. No single field is conclusive — always combine multiple signals before drawing a safety conclusion.
tokenLevel
API field name: tokenLevel (string "0"–"4").
| Value | Rating | Meaning |
|---|---|---|
"0" | Unknown | Cannot be determined |
"1" | Neutral | Neutral |
"2" | OK | Passes basic security checks |
"3" | Suspicious | Suspicious |
"4" | Unsafe | Unsafe |
Always convert to the rating label before presenting to users. Never show the raw numeric string (e.g. show "OK", not "2").
tokenLevel is an auxiliary signal only. A token rated "2" (OK) may still be a counterfeit — always cross-verify with the fields below.
tokenCanShow
Boolean. Indicates whether TronScan considers this token suitable for display. false means TronScan has flagged the token as unsuitable for general display (e.g. spam, extreme risk). tokenCanShow is independent of tokenLevel — do not infer one from the other.
blueTag
String. The name of the recognized project this token officially belongs to (e.g. "Tether", "TRON Foundation"). An empty string means no project association. A non-empty blueTag is a strong positive trust signal.
publicTag
String. A public category label assigned to the token by TronScan (e.g. "Stablecoin", "DeFi"). An empty string means no public tag. A non-empty value indicates the token is a known, categorized asset.
Show full SKILL.md (780 more words)Show less
vip
Boolean. Indicates whether the token or its project has VIP/premium status on TronScan. Treat as a secondary positive trust signal when true.
red_tag
Returned by the /api/security/account/data endpoint. String enum:
| Value | Meaning |
|---|---|
"Suspicious" | The address or token has been flagged as suspicious / potentially fraudulent |
"" (empty) | No fraud warning |
If red_tag is "Suspicious", treat it as the strongest negative signal and warn the user immediately.
Recommended Risk Judgment Order
When assessing whether a token is safe or official, apply signals in this priority order:
- red_tag — Highest priority. If
"Suspicious", the address/token has been flagged for fraud or scam — warn the user immediately. - vip — VIP/premium project indicator.
- blueTag / publicTag — Whether the token is affiliated with a known project or public category.
- tokenLevel — Auxiliary. Use for additional context, not as primary evidence.
- Holder concentration — Use
getTokenPositionDistribution; a top-heavy distribution is a red flag.
Rule: Never declare a token "safe" or "official" based on a single field.
Example: Counterfeit Token Scenario
User: "Is this USDT contract safe?"
A malicious actor may deploy a token named "Tether USD" with symbol "USDT" that passes tokenLevel = "2" (OK). Correct check:
red_tag— Not flagged (new token, not yet reported)blueTag— Empty string (no project affiliation)publicTag— Empty string- Conclusion: Despite
tokenLevel = "2", this token is suspicious. The real USDT hasblueTag: "Tether". Advise the user to verify the contract address matches the known USDT address (TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t).
Workflow: Query Token Info
User: "What is USDT?" or "Tell me about this token" (provides token name/symbol as text)
- Resolve text to address — If user provides name/symbol (e.g. "USDT", "BTT"), use tronscan-search
searchwithtermandtype: "token"to get contract address (token_idin result). If user already provides contract address, skip this step. - tronscan-token-scanner — Call
getTrc20TokenDetail(orgetTrc10TokenDetail) with the contract address / asset ID from step 1. - Convert tokenLevel — Map raw
tokenLevel(0–4) to rating text before presenting:"0"→ Unknown |"1"→ Neutral |"2"→ OK |"3"→ Suspicious |"4"→ Unsafe
- Optional —
getTrc20TokenHolders/getTokenPositionDistributionfor holder list;getTokenPricefor USD conversion if values are in TRX. - Present to user — Return name, symbol, supply, holders, price, market cap (prefer USD), and rating (converted text, not raw level).
Key: Never show raw tokenLevel (e.g. "2") to users; always convert to rating label (e.g. "OK"). Also check tokenCanShow, blueTag, and red_tag before drawing safety conclusions — see Token Risk Fields section.
Workflow: Query TRX Info
User: "What is TRX?" or "TRX price/supply/market cap/detail/info" (queries TRON native token)
- tronscan-token-scanner — Call
getTrc10TokenDetailwith asset ID = 0. TRX is TRON's native token (TRC10), id = 0. - Enrich with —
getFunds(supply, market cap, burn);getTokenPrice(current USD price);getTurnover(turnover, mint/burn);getTrxVolume(24h volume, price change, historical);getTrc10TokenHolders(holder count). For total/yesterday transfer count, use tronscan-transaction-infogetTransactionStatisticsor tronscan-data-insights if needed. - Present to user — Return a rich summary including:
- Basic: name, symbol, description, issuance time
- Supply: total supply, circulating supply
- Price: current price (USD), 24h change
- Market: market cap (USD), 24h volume
- Chain: burn amount, turnover, mint/burn stats (if available)
- Activity: holders, total transfer count, yesterday's transfer count
- Links: whitepaper, media links (if available)
Note: No search step needed; TRX is always asset ID 0.
Workflow: Search by Name, Then Analyze
User: "What is the USDT contract address on TRON? Who are the top holders?"
- tronscan-search — Use
searchwithterm: "USDT",type: "token"to resolve name/symbol to TRC20 contract address (token_idin result). - tronscan-token-scanner — Call
getTrc20TokenDetailwith contract address for supply, holders, price, market cap, rating. - tronscan-token-scanner —
getTrc20TokenHolders/getTokenPositionDistributionfor top holders and concentration. - Optional tronscan-account-profiler — For top holder addresses, call
getAccountDetailorgetTokenAssetOverviewfor wallet profile.
Data handoff: Contract address from step 1 feeds into tronscan-token-scanner in steps 2–3; holder addresses from step 3 feed into tronscan-account-profiler in step 4.
Troubleshooting
- MCP connection failed: If you see "Connection refused", verify TronScan MCP is connected in Settings > Extensions.
- API rate limit / 429: TronScan API has call count and frequency limits when no API key is used. If you encounter rate limiting or 429 errors, go to TronScan Developer API to apply for an API key, then add it to your MCP configuration and retry.
Invalid contract address or asset ID
TRC20/TRC721/TRC1155 require contract address; TRC10 requires asset ID. Do not mix them.
Notes
- For TRX: use
getTokenPrice,getFunds,getTrxVolume,getTurnoverfor price, supply, market cap, and trends. - For "rating" or risk metrics, combine with contract analysis (contract verification, holders, distribution).
- TRC20/TRC721/TRC1155 use contract address; TRC10 uses asset ID.
- market_cap, price, volume units: Check whether values are in USD or TRX. Prefer returning USD to users. If only TRX is available, query TRX price via
getTokenPriceand convert to USD before returning.
© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/tronscan-token-scanner of LeoYeAI/openclaw-master-skills.
- SKILL.md
- _meta.json
Open the folder on GitHubat commit e5199b5
Compare with similar skills
Tronscan Token Scanner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Tronscan Token Scanner this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Virtuals Protocol AcpVirtual-Protocol/openclaw-acp | 168 | 1 repos | ~6.4k | Automated safety check: Pass | None | |
| Messari X402moonpay/skills | 113 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Okx Cex Earnokx/agent-skills | 186 | 2 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Onchain Pay Open APInpc-live/clawfirm | 156 | 1 repos | ~4.9k | Automated safety check: Pass | MIT | |
| Aptos Explorer Urlsaptos-labs/explorer | 124 | — | ~1.2k | Automated safety check: Pass | None |
Similar skills
Messari X402
moonpay/skills
Access Messari's full API via x402 pay-per-request — no API key needed.
Okx Cex Earn
okx/agent-skills
Manages OKX Simple Earn (flexible savings/lending), Flash Earn, On-chain Earn (staking/DeFi), Dual Investment (DCD/双币赢), and AutoEarn (自动赚币) via the okx CLI.
Onchain Pay Open API
npc-live/clawfirm
Binance Onchain Pay enables users to buy cryptocurrency with fiat (e.g., EUR, USD) or send existing crypto from their Binance account directly to any external on-chain wallet address in a single…
Aptos Explorer Urls
aptos-labs/explorer
Map questions about Aptos blockchain entities (transactions, accounts, blocks, validators, coins, fungible assets, NFTs, Move objects, ANS names) to canonical Aptos Explorer URLs at…
Bridge Stablecoin
circlefin/skills
Build browser or server USDC bridging with Circle App Kit or standalone Bridge Kit and CCTP.
More from LeoYeAI/openclaw-master-skills
All 1,235 skills in this repoDevOps Pipeline Management
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
Feishu Document Collaboration
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
Files Memory System
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
GEO-Claw AI Visibility Agent
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
Google Workspace CLI
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
HealthFit Health Advisors
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Related
Categories
Questions about Tronscan Token Scanner
What does Tronscan Token Scanner do?
Scan TRON tokens for total supply, market cap, price, rating, launch time, holders. Tronscan Token Scanner is an agent skill from LeoYeAI/openclaw-master-skills. Scan TRON tokens for total supply, market cap, price, rating, launch time, holders.
When should I use Tronscan Token Scanner?
Tronscan Token Scanner fits situations like: user asks how is this token; token due diligence; supply of contract address; provides a token contract address.
How do I install Tronscan Token Scanner in Claude Code?
Run `npx skills add LeoYeAI/openclaw-master-skills --skill tronscan-token-scanner -a claude-code`. Or copy the skill folder (skills/tronscan-token-scanner in LeoYeAI/openclaw-master-skills) into .claude/skills/tronscan-token-scanner in your project. Claude Code loads it when a task matches its description.
How do I install Tronscan Token Scanner in Codex?
Run `npx skills add LeoYeAI/openclaw-master-skills --skill tronscan-token-scanner -a codex`. Or copy the skill folder (skills/tronscan-token-scanner in LeoYeAI/openclaw-master-skills) into .agents/skills/tronscan-token-scanner in your project. Codex loads it when a task matches its description.
Can I use Tronscan Token Scanner in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill tronscan-token-scanner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tronscan-token-scanner, .gemini/skills/tronscan-token-scanner, .github/skills/tronscan-token-scanner and .opencode/skills/tronscan-token-scanner in your project.
What does Tronscan Token Scanner need to run?
SKILL.md names no scripts, command-line tools or credentials: Tronscan Token Scanner is instructions for the agent only.
Does Tronscan Token Scanner access the network?
SKILL.md names 2 domains. As links in the text: mcpdoc.tronscan.org and tronscan.org. This is read from the text; nothing was executed.
Is Tronscan Token Scanner safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Tronscan Token Scanner use?
Tronscan Token Scanner is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Tronscan Token Scanner use?
About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Tronscan Token Scanner?
Skills that share tags, products or a category with Tronscan Token Scanner: Virtuals Protocol Acp (Virtual-Protocol/openclaw-acp, 168 stars), Messari X402 (moonpay/skills, 113 stars), Okx Cex Earn (okx/agent-skills, 186 stars) and Onchain Pay Open API (npc-live/clawfirm, 156 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Tronscan Token Scanner?
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,160 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.