io.github.menantonio83-hue/tnt-house-risk-data-api
REMOTE · WWW.TNT-AUDIT.COM
RiskDataApi — Solana token risk scoring for AI agents. Safety score, insider clusters, honeypot.
Available components
Last scanned (2 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 994 tokens (~165/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 77
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://www.tnt-audit.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.tnt-audit.com | CN=YR2,O=Let's Encrypt,C=US | 29 Oct 2026 | 27 Jan 2027 | RSA 2048 | SHA256-RSA | 651f3f6d968632d6c16587851568252ea21 |
| SANs: www.tnt-audit.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.tnt-audit.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tnt-audit.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.tnt-audit.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.tnt-audit.com/api/mcp | HTTPS enforced | 308 | https://www.tnt-audit.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_payment Check an invoice payment ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional. Your RiskDataApi key, for MCP hosts that cannot send an Authorization header. If both are present, the Authorization header wins. |
| payment_id | string | yes | payment_id returned by create_topup_invoice |
No output schema declared.
No examples provided.
check_token_risk Check Solana token risk ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional. Your RiskDataApi key, for MCP hosts that cannot send an Authorization header. If both are present, the Authorization header wins. |
| mint | string | yes | The Solana token mint address to check |
No output schema declared.
No examples provided.
check_token_risk_batch Check risk for multiple Solana tokens at once ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional. Your RiskDataApi key, for MCP hosts that cannot send an Authorization header. If both are present, the Authorization header wins. |
| mints | array | yes | 1-25 Solana token mint addresses |
No output schema declared.
No examples provided.
create_topup_invoice Create a top-up or subscription invoice ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional. Your RiskDataApi key, for MCP hosts that cannot send an Authorization header. If both are present, the Authorization header wins. |
| currency | string | – | Payment currency (default USDC) |
| kind | string | – | topup (default) or subscription |
| usd_amount | number | – | Top-up amount in USD, 5-500 (default 5); ignored for subscription |
No output schema declared.
No examples provided.
get_free_api_key Get a free API key ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to register the free key to |
No output schema declared.
No examples provided.
get_token_risk_history Get historical risk trend for a Solana token ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | How many days of history to return (default 30, max 90) |
| mint | string | yes | The Solana token mint address |
No output schema declared.
No examples provided.
How do I install the io.github.menantonio83-hue/tnt-house-risk-data-api MCP server?
io.github.menantonio83-hue/tnt-house-risk-data-api is a hosted endpoint at https://www.tnt-audit.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.tnt-audit.com
claude mcp add --transport http menantonio83-hue-tnt-house-risk-data-api 'https://www.tnt-audit.com/api/mcp'
What is the io.github.menantonio83-hue/tnt-house-risk-data-api MCP server?
io.github.menantonio83-hue/tnt-house-risk-data-api is an MCP server listed in the public MCP registry as io.github.menantonio83-hue/tnt-house-risk-data-api. RiskDataApi, Solana token risk scoring for AI agents. Safety score, insider clusters, honeypot. This page covers its hosted endpoint (https://www.tnt-audit.com/api/mcp).
Is the io.github.menantonio83-hue/tnt-house-risk-data-api MCP server safe to use?
io.github.menantonio83-hue/tnt-house-risk-data-api scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.menantonio83-hue/tnt-house-risk-data-api MCP server expose?
io.github.menantonio83-hue/tnt-house-risk-data-api exposes 6 tools: check_token_risk, check_token_risk_batch, get_free_api_key, create_topup_invoice, check_payment, get_token_risk_history. Their descriptions and schemas cost roughly 825 tokens of context every time the server is loaded.
Does the io.github.menantonio83-hue/tnt-house-risk-data-api MCP server require authentication?
Yes. io.github.menantonio83-hue/tnt-house-risk-data-api asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.menantonio83-hue/tnt-house-risk-data-api MCP server still maintained?
io.github.menantonio83-hue/tnt-house-risk-data-api is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.