# TRON USDT Risk Checker (remote · usdt.chikocorp.com)

TRON USDT risk: free Tether blacklist check, paid sanctions screen and AML report.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `usdt.chikocorp.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/chico10117-tron-usdt-mcp/usdt.md), [page](https://verifymcp.io/servers/chico10117-tron-usdt-mcp/usdt)
- npm · `tron-usdt-mcp`: 42/100, [markdown](https://verifymcp.io/servers/chico10117-tron-usdt-mcp/tron-usdt-mcp.md), [page](https://verifymcp.io/servers/chico10117-tron-usdt-mcp/tron-usdt-mcp)

## Channel facts

- Endpoint: `https://usdt.chikocorp.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 493 tokens (~164/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the TRON USDT Risk Checker MCP server?

TRON USDT Risk Checker is a hosted endpoint at https://usdt.chikocorp.com/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.

### Claude

```bash
claude mcp add --transport http chico10117-tron-usdt-mcp 'https://usdt.chikocorp.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "chico10117-tron-usdt-mcp": {
      "url": "https://usdt.chikocorp.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "chico10117-tron-usdt-mcp": {
      "type": "http",
      "url": "https://usdt.chikocorp.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.chico10117-tron-usdt-mcp]
url = "https://usdt.chikocorp.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "chico10117-tron-usdt-mcp": {
      "type": "remote",
      "url": "https://usdt.chikocorp.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add chico10117-tron-usdt-mcp --url 'https://usdt.chikocorp.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  chico10117-tron-usdt-mcp:
    url: "https://usdt.chikocorp.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "chico10117-tron-usdt-mcp": {
      "Transport": "http",
      "Url": "https://usdt.chikocorp.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add chico10117-tron-usdt-mcp -t streamable-http -u 'https://usdt.chikocorp.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "chico10117-tron-usdt-mcp": {
      "type": "http",
      "url": "https://usdt.chikocorp.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 74, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-11-10 (score 74, +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.

### 2026-11-09 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (3)

### `check_tron_usdt_blacklist` (~106 tokens)

Check TRON USDT blacklist

Free. Reads the USDT TRC20 contract live and reports whether Tether has blacklisted (frozen) a TRON address. Point-in-time result. Limited per caller per UTC day; failed reads still count toward the limit.

Input parameters:

- `address` (string, required): Public TRON address (base58 T-address, e.g. TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t).

### `screen_tron_address` (~109 tokens)

Screen TRON address (sanctions + abuse reports)

Paid. USDT freeze status plus OFAC SDN and OpenSanctions matches, Chainabuse reports and an explainable risk score for one TRON address. Pay per call with x402 (USDC on Base) or with an API key (1 credit).

Input parameters:

- `address` (string, required): Public TRON address (base58 T-address, e.g. TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t).

### `tron_usdt_aml_report` (~116 tokens)

TRON USDT AML report

Paid. Full AML report for one TRON address: freeze status, sanctions, abuse reports, Tether freeze history, 1-hop counterparty exposure and tracing, with a short summary. Pay per call with x402 (USDC on Base) or with an API key (1 credit).

Input parameters:

- `address` (string, required): Public TRON address (base58 T-address, e.g. TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/chico10117-tron-usdt-mcp/usdt#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 77
- 2026-11-15: 76
- 2026-11-14: 76
- 2026-11-13: 75
- 2026-11-12: 75
- 2026-11-11: 74
- 2026-11-10: 74
- 2026-11-09: 73
- 2026-11-08: 73

## Common questions

### What is the TRON USDT Risk Checker MCP server?

TRON USDT Risk Checker is an MCP server listed in the public MCP registry as io.github.chico10117/tron-usdt-mcp. TRON USDT risk: free Tether blacklist check, paid sanctions screen and AML report. This page covers its hosted endpoint (https://usdt.chikocorp.com/mcp).

### Is the TRON USDT Risk Checker MCP server safe to use?

TRON USDT Risk Checker scores 79 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 TRON USDT Risk Checker MCP server expose?

TRON USDT Risk Checker exposes 3 tools: check_tron_usdt_blacklist, screen_tron_address, tron_usdt_aml_report. Their descriptions and schemas cost roughly 331 tokens of context every time the server is loaded.

### Does the TRON USDT Risk Checker MCP server require authentication?

No. We connected to TRON USDT Risk Checker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the TRON USDT Risk Checker MCP server still maintained?

TRON USDT Risk Checker is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the TRON USDT Risk Checker MCP server?

VerifyMCP ran 13 checks on TRON USDT Risk Checker, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://usdt.chikocorp.com/mcp
- Repository: https://github.com/chico10117/tron-usdt-mcp
- Website: https://usdt.chikocorp.com/api-docs
- Changelog RSS feed: https://verifymcp.io/servers/chico10117-tron-usdt-mcp/usdt.xml
- Changelog JSON feed: https://verifymcp.io/servers/chico10117-tron-usdt-mcp/usdt/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/chico10117-tron-usdt-mcp/usdt.json
- HTML version of this page: https://verifymcp.io/servers/chico10117-tron-usdt-mcp/usdt
