Pay-per-call USDT (TRC-20) payment verification and Tron address risk checks. Paid via x402.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Free. Lists TronProof tools, what they do and what each call costs.
This tool takes no arguments.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http tronproof https://tronproof.online/mcp
Free. Lists TronProof tools, what they do and what each call costs.
No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}Scores a Tron address for address-poisoning look-alikes, dust attacks, fake-USDT deposits and missing history. Pass "expected" to detect a look-alike of the address you meant to pay. Use before any outgoing USDT transfer. Costs $0.01 per call in USDC on Base (x402).
| Argument | Type | Description |
|---|---|---|
| address* | string | Tron address you are about to pay or want to inspect |
| expected | string | Optional known-good address to compare against |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"address"
],
"properties": {
"address": {
"type": "string",
"description": "Tron address you are about to pay or want to inspect"
},
"expected": {
"type": "string",
"description": "Optional known-good address to compare against"
}
},
"additionalProperties": false
}Returns recent confirmed transfers of genuine USDT for a Tron address as clean JSON with decimal amounts, direction and explorer links. Fake tokens are filtered out. Costs $0.002 per call in USDC on Base (x402).
| Argument | Type | Description |
|---|---|---|
| limit | number | Number of transfers, 1 to 200. Default 50 |
| address* | string | Tron address |
| direction | string | "in", "out" or "both" (default) |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"address"
],
"properties": {
"limit": {
"type": "number",
"description": "Number of transfers, 1 to 200. Default 50"
},
"address": {
"type": "string",
"description": "Tron address"
},
"direction": {
"type": "string",
"description": "\"in\", \"out\" or \"both\" (default)"
}
},
"additionalProperties": false
}Confirms whether a Tron address received a specific amount of genuine USDT within a time window. Ignores fake tokens that copy the USDT name. Use before releasing goods, crediting an account or marking an invoice paid. Costs $0.005 per call in USDC on Base (x402).
| Argument | Type | Description |
|---|---|---|
| to* | string | Tron address that should have received the payment |
| from | string | Optional sender address the payment must come from |
| txid | string | Optional transaction id the payment must match |
| match | string | "exact" (default) or "at_least" |
| amount* | string | Expected USDT amount, for example 25 or 25.50 |
| minutes | number | How far back to look, 1 to 10080. Default 60 |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"to",
"amount"
],
"properties": {
"to": {
"type": "string",
"description": "Tron address that should have received the payment"
},
"from": {
"type": "string",
"description": "Optional sender address the payment must come from"
},
"txid": {
"type": "string",
"description": "Optional transaction id the payment must match"
},
"match": {
"type": "string",
"description": "\"exact\" (default) or \"at_least\""
},
"amount": {
"type": "string",
"description": "Expected USDT amount, for example 25 or 25.50"
},
"minutes": {
"type": "number",
"description": "How far back to look, 1 to 10080. Default 60"
}
},
"additionalProperties": false
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 11, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.