solscan — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited solscan (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
You have access to the Solscan Pro API v2 for Solana data.
Read reference files when you need depth:
references/endpoints.md — full endpoint catalog with all parametersreferences/limits.md — CU model, rate limits, page_size gotchasreferences/batch-patterns.md — MCP vs script decision, multi-endpoints, export endpointsreferences/examples/ — ready-to-run Python scripts for common batch tasksThe #1 way this API gets wasted is calling MCP tools in a loop. Each call consumes API credits AND burns tokens in the conversation context, and serial MCP calls don't parallelize.
| Task size | Tool |
|---|---|
| 1–10 API calls, exploratory | MCP tools directly |
| 10–30 calls | Script preferred, especially if same shape of request repeats |
| > 30 calls | Always write a script |
| Any batch where responses are parsed, aggregated, or filtered | Always a script |
When writing a script: async aiohttp + asyncio.Semaphore(25), output to CSV/JSON, resume pattern (skip already-processed IDs). See references/examples/ for working templates.
Solscan charges 100 CU per request flatly, so batch endpoints are 50× cheaper than per-item loops:
| Instead of | Use |
|---|---|
50 × transaction/detail (5000 CU) | 1 × transaction/detail/multi (100 CU) |
50 × token/meta | 1 × token/meta/multi |
50 × account/metadata | 1 × account/metadata/multi |
Paginating account/defi/activities past 10k rows | account/defi/activities/export |
Paginating account/transfer for full history | account/transfer/export |
Before writing a loop, check if a multi-endpoint exists (see references/endpoints.md).
Allowed values: 10, 20, 30, 40, 60, 100.
page_size=50 → fails silently or returns errorpage_size=100 → works, use this for batchpage_size=200+ → failsDefault is often 20 — always set 100 for batch work.
| MCP tool | Endpoint | When to use |
|---|---|---|
solscan_account_info | account/detail | SOL balance, account type, owner |
solscan_account_tokens | account/token-accounts | SPL balances |
solscan_account_transfers | account/transfer | Transfer history (single wallet exploration) |
solscan_account_transactions | account/transactions | Raw tx list |
solscan_account_defi_activities | account/defi/activities | Swaps/liquidity/staking |
solscan_transaction | transaction/detail | One tx |
solscan_token_info | token/meta | Token metadata |
solscan_token_holders | token/holders | Top holders (paginated) |
solscan_token_price | token/price | Price history |
solscan_token_markets | token/markets | DEX pools |
solscan_token_transfers | token/transfer | Recent transfers across wallets |
solscan_nft_info | nft/info | NFT metadata |
solscan_nft_activities | nft/activities | Sales/transfers |
solscan_search | search | Find by name/partial addr |
For batch work not covered by MCP (multi-endpoints, exports): use direct HTTP with the same key. See references/examples/.
Step 1 — Identify input type
solscan_account_info → solscan_account_tokenssolscan_token_infosolscan_transactionsolscan_search first to get mintsolscan_nft_infoStep 2 — Assess size If the request involves > 10 items (N wallets, N tokens, N signatures) → go to references/batch-patterns.md and write a script. Don't loop MCP calls.
Step 3 — Apply Rules 1–3 above
page_size=100, async semaphore=25, multi-endpoints where possibledatafile/downloadStep 4 — Present results
So11...1112 (first 4 + last 4)https://solscan.io/account/<addr> or https://solscan.io/tx/<sig>0x prefixSo11111111111111111111111111111111111111112EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1vEs9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYBDezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263EKpQGSJtjMFqKZ9KQanSqYXRcF8fBopzLHYxdM65zcjmJUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN4k3Dyjzvzp8eMZWUXbBCjEvwSkkk59S5iCNLY3QrkX6RAll Solscan endpoints use unix timestamps in seconds.
from_time = now - 86400from_time = now - 604800from_time = now - 2592000Historical depth (see references/limits.md):
SOLSCAN_API_KEY env varreferences/limits.md — Tier 2 is 1000/min, above that you need exponential backoff or lower concurrency)solscan_searchCheck consumption with monitor/usage endpoint if the user suspects CU drain.
transaction/detail/multi~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.