RiskDataApi — Insider Cluster Detection for Solana Tokens
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TNT_API_KEY | Yes | Your API key for the TNT House Risk-Data API. Get it at https://www.tnt-audit.com/risk-api |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_token_riskA | Returns a 0-100 safety score, on-chain insider wallet clusters (wallets sharing a first funder), mint/freeze authority status, holder concentration, and live price/liquidity/volume for a single Solana token mint. Use before recommending or executing a trade on any Solana token. 5 free MCP calls/day, no signup. Then email key or x402. |
| check_token_risk_batchA | Same as check_token_risk but for up to 25 mints in one call — N mints charged as N calls, same per-call economics as check_token_risk, no bulk discount. All-or-nothing: if the batch can't be fully covered by remaining quota/credit, the whole batch is rejected rather than partially processed. |
| get_token_risk_historyA | Returns hourly historical data points (safety_score, insider_cluster_count, holder_count, price, liquidity, volume) for a mint over the last N days (max 90). Free and unmetered — no quota, works with or without an API key — pure read from stored history, no live upstream call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools are clearly distinct: check_token_risk covers a single token snapshot, check_token_risk_batch explicitly handles multiple mints, and get_token_risk_history addresses historical data. There is no meaningful overlap or ambiguity between current risk checking, batch risk checking, and historical trends.
All tool names follow a consistent snake_case verb_noun pattern: check_token_risk, check_token_risk_batch, and get_token_risk_history. The shared token_risk core with clear qualifiers makes the toolset predictable and easy to navigate.
Three tools is appropriately scoped for a focused insider-cluster risk API: single-token checks, batch checks, and historical data. Each tool serves a distinct and necessary purpose without redundancy or bloat.
The toolset covers the core domain completely: immediate single-token risk assessment, scaled batch assessment, and historical trend analysis. Since the API is read-only risk intelligence, no create/update/delete operations are expected, and no significant capability gap is apparent.