mcp server
tnt-house-risk-data-api
Solana token risk-scoring MCP server for AI trading agents with insider wallet cluster detection.
Description as published by the maintainer. Source
- version 1.0.0
- active
- evaluation
active — Registry entry last updated 2026-07-25. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
3 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
check_token_risk(mint)- 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. Required: mint.
check_token_risk_batch(mints)- 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. Required: mints.
get_token_risk_history(days, mint)- 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). Does not count against the free/subscription call quota — pure read from stored history, no live upstream call. Required: mint.
Last successful function declaration observed on . Source: https://tnt-audit.com/api/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://tnt-audit.com/api/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-25 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-25 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 3 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | tnt-audit.com | |
| mcp endpoint status | ok | The server listed 3 functions when asked. | as of probe | tnt-audit.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json