Security & Testing

tnt-audit.com

Provides on-chain security risk analysis for Solana tokens, including safety scores, insider cluster detection, authority status, and market metrics.

x402 supported1 endpoint3 known toolsFirst detected September 3, 2026Last detected September 3, 2026

ENDPOINT 1

https://tnt-audit.com/api/mcp

No auth detected

MCP server metadata

Name: tnt-house-risk-data-api
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

check_token_risk works with NO API key for your first 5 calls/day (no signup) — just call the tool directly. get_token_risk_history is also free/unmetered, key or no key. Need more check_token_risk calls? Get a free key with a 15/day quota — for an autonomous agent, self-serve one with no human required: POST {"email":"you@example.com"} to https://tnt-audit.com/api/v1/signup, the JSON response includes api_key directly. (Human-friendly form at https://tnt-audit.com/risk-api works too.) Already have an x402-capable wallet? Skip signup entirely: GET https://tnt-audit.com/api/v1/token-risk/x402?mint=<mint> pays per call in USDC on Solana via the standard x402 402-Payment-Required flow, no key or account at all. check_token_risk_batch requires a key or x402 — no anonymous batch calls.

Known tools 3

check_token_risk

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.

Inferred read-only

check_token_risk_batch

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.

Inferred read-only

get_token_risk_history

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).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.tnt-house-risk-data-api]
url = "https://tnt-audit.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "tnt-house-risk-data-api": {
      "type": "http",
      "url": "https://tnt-audit.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: tnt-house-risk-data-api
Remote MCP URL: https://tnt-audit.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "tnt-house-risk-data-api": {
      "url": "https://tnt-audit.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "tnt-house-risk-data-api": {
      "type": "http",
      "url": "https://tnt-audit.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "tnt-house-risk-data-api",
  "transport": "streamable-http",
  "url": "https://tnt-audit.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.