tnt-house-risk-data-api
Registry code: a58e1d2e37b5be80
check_token_risk works with no signup: 5 free anonymous calls/day — just call the tool directly. On a quota refusal, read error_code + options[] and follow one to continue (free key, x402, or top up). get_free_api_key(email) issues a free key for 15 calls/day; pass it via the Authorization: Bearer header or the api_key argument (header wins). Pay per call with x402: GET https://www.tnt-audit.com/api/v1/token-risk/x402?mint=<mint> ($0.02 USDC on Solana, no account). check_token_risk_batch (max 25 mints) needs a key or x402; N mints = N calls, all-or-nothing. get_token_risk_history is…
- endpoint
- https://www.tnt-audit.com/api/mcp
- door code
- dabdd39a7fda09f9
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is tnt-house-risk-data-api live?
- Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.
- Is tnt-house-risk-data-api free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does tnt-house-risk-data-api have?
- 6 tools: check_token_risk, check_payment, get_token_risk_history, create_topup_invoice, get_free_api_key, check_token_risk_batch.
- Is tnt-house-risk-data-api safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.7%· all time 100%
last good check
of 6 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- degraded → live
- used for
- score a solana token for rug risk
- check risk for many tokens at once
- get token risk history
- takes → gives
- text → data
- tools
- 3 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
check_token_risk_batch reads auth-required 14h ago
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. Needs an API key (Authorization header or api_key argument) or x402 — no anonymous batch calls.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "mints" ], "properties": { "mints": { "type": "array", "items": { "type": "string" }, "maxItems": 25, "minItems": 1, "description": "1-25 Solana token mint addresses" }, "api_key": { "type": "string", "maxLength": 200, "description": "Optional. Your RiskDataApi key, for MCP hosts that cannot send an Authorization header. If both are present, the Authorization header wins." } }, "additionalProperties": false }arguments 24 linescheck_token_risk reads unknown 14h ago
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 anonymous calls/day, no signup. Then call get_free_api_key (15/day) or pay per call via x402; pass a key via the Authorization header or the api_key argument. Quota refusals return error_code + options[] with the exact next step.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "mint" ], "properties": { "mint": { "type": "string", "description": "The Solana token mint address to check" }, "api_key": { "type": "string", "maxLength": 200, "description": "Optional. Your RiskDataApi key, for MCP hosts that cannot send an Authorization header. If both are present, the Authorization header wins." } }, "additionalProperties": false }arguments 19 linescheck_payment unknown never probed
Checks on-chain whether an invoice from create_topup_invoice has been paid and, if so, credits your key. Safe to call repeatedly (idempotent), at most once every 5 seconds per payment_id (after 30 checks per hour per key, once a minute); if throttled it returns error_code verify_rate_limited with retry_after seconds. Returns verified true/false with a reason.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "payment_id" ], "properties": { "api_key": { "type": "string", "maxLength": 200, "description": "Optional. Your RiskDataApi key, for MCP hosts that cannot send an Authorization header. If both are present, the Authorization header wins." }, "payment_id": { "type": "string", "maxLength": 100, "description": "payment_id returned by create_topup_invoice" } }, "additionalProperties": false }arguments 20 linesget_token_risk_history reads unknown 14h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "mint" ], "properties": { "days": { "type": "number", "maximum": 90, "minimum": 1, "description": "How many days of history to return (default 30, max 90)" }, "mint": { "type": "string", "description": "The Solana token mint address" } }, "additionalProperties": false }arguments 20 linescreate_topup_invoice unknown never probed
Creates a Solana payment invoice for your API key: kind "topup" adds call credit ($5-$500, usd_amount, default $5); kind "subscription" buys 30 days. Returns payment_id, the exact pay_amount and wallet_address. Send exactly pay_amount, then call check_payment. Max 3 pending invoices per key.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "kind": { "enum": [ "topup", "subscription" ], "type": "string", "description": "topup (default) or subscription" }, "api_key": { "type": "string", "maxLength": 200, "description": "Optional. Your RiskDataApi key, for MCP hosts that cannot send an Authorization header. If both are present, the Authorization header wins." }, "currency": { "enum": [ "USDC", "SOL", "MRDT" ], "type": "string", "description": "Payment currency (default USDC)" }, "usd_amount": { "type": "number", "description": "Top-up amount in USD, 5-500 (default 5); ignored for subscription" } }, "additionalProperties": false }arguments 33 linesget_free_api_key unknown never probed
Issues a free RiskDataApi key for an email address (15 checks/day instead of 5 anonymous calls/day). No email verification. One active key per email; the key is returned once and also emailed. Use it when you hit the anonymous daily limit.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "email" ], "properties": { "email": { "type": "string", "maxLength": 200, "description": "Email address to register the free key to" } }, "additionalProperties": false }arguments 15 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's ida58e1d2e37b5be80.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/a58e1d2e37b5be80/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/a58e1d2e37b5be80?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.