TRON USDT Risk Checker MCP server
io.github.chico10117/tron-usdt-mcpchico10117streamable-httpv1.0.1Scanned
TRON USDT risk: free Tether blacklist check, paid sanctions screen and AML report.
3 tools: 3 change things.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the TRON USDT Risk Checker MCP server can do
The TRON USDT Risk Checker MCP server is published by the GitHub account chico10117. It has 3 tools. It can create or change data (3 tools: check_tron_usdt_blacklist, screen_tron_address and tron_usdt_aml_report), but cannot delete data. None of its tools only reads.
3 tools bring in text other people can write (check_tron_usdt_blacklist, screen_tron_address and tron_usdt_aml_report).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 8, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 3Claude Code: ask
check_tron_usdt_blacklistFree.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
screen_tron_addressPaid.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
tron_usdt_aml_reportPaid.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 16, 2026, 14:21 UTC, unchanged since Nov 9, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://usdt.chikocorp.com/mcp: tools/list returned 3 tools to an anonymous client, including check_tron_usdt_blacklist (write), screen_tron_address (write), tron_usdt_aml_report (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http tron-usdt https://usdt.chikocorp.com/mcpclaude mcp add --transport http tron-usdt https://usdt.chikocorp.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__tron-usdt__check_tron_usdt_blacklist",
"mcp__tron-usdt__screen_tron_address",
"mcp__tron-usdt__tron_usdt_aml_report"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tron-usdt. Review it before you use it.
Capability tags behind 3 rules
- mcp__tron-usdt__check_tron_usdt_blacklist untrusted-input
- mcp__tron-usdt__screen_tron_address untrusted-input
- mcp__tron-usdt__tron_usdt_aml_report untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.chico10117/tron-usdt-mcp/verify?hash=7193da9338ca54cc8bf2d53c914a2313b98908b78030c191fa3edf49b326fa9e" | jq -e '.changed == false'Pinned hash 7193da9338ca, from Nov 8, 2026, 20:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.chico10117/tron-usdt-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.chico10117/tron-usdt-mcp)Source: MCP Registry · repository. Synced Nov 8, 2026, 21:17 UTC.
TRON USDT Risk Checker MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the TRON USDT Risk Checker MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the TRON USDT Risk Checker MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the TRON USDT Risk Checker MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the TRON USDT Risk Checker MCP server have?
- 3 tools: 3 write. check_tron_usdt_blacklist, screen_tron_address and tron_usdt_aml_report.
Does the TRON USDT Risk Checker MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the TRON USDT Risk Checker MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the TRON USDT Risk Checker MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.