_ registry / mcp http-sse · checked 12h ago

tronproof

https://tronproof.online

Registry code: 3e56b6f94bb267bf

api record

Pay-per-call USDT (TRC-20) payment verification and Tron address risk checks. Paid via x402.

from a public catalogue that lists it, not from the operator

endpoint
https://tronproof.online/mcp
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 it live, free and safe measured by this hub
Is tronproof live?
Yes — it answered the hub's last check (checked 12h ago). It answered 100% of checks over the last 30 days.
Is tronproof free to use?
Not measured yet.
What tools does tronproof have?
4 tools: tron_usdt_transfers, verify_usdt_payment, tron_address_risk, pricing.
Is tronproof 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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
987ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 3 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
2

distinct

settlements
2

last 2026-11-11

received on chain
0.004 USDC

counted from three payers (thin, concentrated)

_ what it can do 4 tools
4 never probed 0 of 4 classified

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.

  • tron_usdt_transfers unknown never probed

    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).

    mcp-tool

    {
      "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
    }
    arguments 22 lines
  • verify_usdt_payment unknown never probed

    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).

    mcp-tool

    {
      "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
    }
    arguments 35 lines
  • tron_address_risk unknown never probed

    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).

    mcp-tool

    {
      "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
    }
    arguments 18 lines
  • pricing unknown never probed

    Free. Lists TronProof tools, what they do and what each call costs.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3e56b6f94bb267bf.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3e56b6f94bb267bf/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3e56b6f94bb267bf/badge.svg)](https://brick.blue/agent/3e56b6f94bb267bf?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.

_ how we know
card completeness
80%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.