TronScan Token List

Get TRC20 token list on TRON with price, 24h change, 24h volume, market cap, holder count. Use when user asks "token list", "TRC20 list", "hot tokens", "tren...

Security Scan

The skill's declared purpose (return TRON TRC20 token lists and metrics) matches its instructions and there are no unexpected installs or credential requests, but the SKILL.md is vague about how authentication is provided and assumes a platform-level MCP configuration.

Purpose & Capability

Name/description describe listing TRON tokens with price/volume/mcap/holders. The SKILL.md only describes calling TronScan MCP APIs (getTokenList, getPricedTokenList, getTrc20TokenDetail, getHotSearch, getSearchBar), which is consistent with the stated purpose.

Instruction Scope

Instructions are scoped to calling the TronScan MCP APIs and using token list/detail endpoints. They do not ask the agent to read arbitrary local files or unrelated credentials. However the SKILL.md is high-level and does not document exact endpoint paths, request/response formats, or error-handling—so it relies on the agent/platform having a preconfigured MCP integration.

Install Mechanism

Instruction-only skill with no install spec and no code files; nothing is written to disk or downloaded by the skill itself.

Credentials

The skill declares no required environment variables or credentials, which is plausible if the platform provides MCP credentials centrally. The docs mention applying for an API key and adding it to 'MCP configuration' but do not declare how that key is supplied to the skill (env var, platform setting, or other). There are no unrelated credential requests.

Persistence & Privilege

always is false and the skill does not request any persistent system-wide privileges or attempt to modify other skills or agent settings. It expects the platform to have a configured MCP connection.

Assessment

This skill appears to just instruct the agent to call TronScan's MCP APIs to return TRC20 token lists, which matches its description. Before installing: confirm that your agent/platform already has a trusted MCP integration or that you understand where an API key would be stored (the SKILL.md references adding a key in Settings > Extensions rather than declaring an env var). Verify you trust the MCP server (https://mcp.tronscan.org/mcp) because API calls will go to that external endpoint. If you need stronger assurance, ask the skill author for the exact request schemas/endpoints and how authentication is provided (platform-managed config vs. environment variables) and inspect any platform settings that store the API key to ensure it won’t be exposed elsewhere.

Token List

Overview

Tool	Function	Use Case
getTokenList	Token list	Filter by type, sort by price/change/volume/mcap/holders
getPricedTokenList	Priced tokens	All tokens with price data
getTrc20TokenDetail	Single token	Full TRC20/721/1155 detail for list item
getHotSearch	Hot search	Hot tokens and contracts with metrics and price
getSearchBar	Search bar	Popular search results (hot token list)

Use Cases

1. TRC20 Token List: Use getTokenList with type filter for TRC20; use getPricedTokenList for tokens with price.
2. Price & 24h Change: Token list and priced list include price and change; use detail for full 24h data.
3. 24h Volume: Available in list or detail (e.g. getTrc20TokenDetail) and in getHotSearch.
4. Market Cap: In token list/detail and hot search.
5. Holder Count: In token list/detail.
6. Discover Quality Projects: Sort by volume, market cap, or holders; combine with getHotSearch for trending.

MCP Server

• Prerequisite: TronScan MCP Guide

Tools

getTokenList

• API: getTokenList — Get token list with type filter and sort by price/change/volume/holders/mcap
• Use when: User asks for "token list", "TRC20 list", or "tokens by volume/mcap".
• Input: type, sort field, order, pagination.
• Response: List of tokens with key metrics.

getPricedTokenList

• API: getPricedTokenList — Get all tokens with price data
• Use when: User asks for "tokens with price" or "priced token list".
• Response: Tokens with price and related fields.

getTrc20TokenDetail

• API: getTrc20TokenDetail — Get TRC20/TRC721/TRC1155 token details (name, symbol, supply, holders, price, etc.)
• Use when: User needs full metrics for a token from the list (e.g. 24h volume, holders).
• Input: Contract address.

getHotSearch

• API: getHotSearch — Get hot tokens and contracts (trading metrics and price data)
• Use when: User asks for "trending tokens" or "hot tokens on TRON".
• Response: Hot tokens/contracts with price and activity metrics.

getSearchBar

• API: getSearchBar — Get popular search results (hot token list)
• Use when: User asks for "popular tokens" or "search suggestions".

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.

Notes

• For "quality projects", combine sort (volume, mcap, holders) with hot search and optional token detail for due diligence.
• List tools support pagination; use limit/skip or page/size as per TronScan MCP API.