TRC20 payment instruments MCP server
com.trycloudflare.expanded-oven-hardwood-cheque/trc20-instrumentsexpanded-oven-hardwood-cheque.trycloudflare.comstreamable-httpv1.0.1Scanned
Measured USDT-TRC20 facts: postage, market-vs-cluster payers, reference codec.
7 tools: 1 do something that can't be undone, 4 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 4
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
5 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the TRC20 payment instruments MCP server can do
The TRC20 payment instruments MCP server is published by expanded-oven-hardwood-cheque.trycloudflare.com, a domain the MCP Registry verified. It has 7 tools. It can do things that cannot be undone, such as sending, paying or publishing (trc20_transfer_cost) and create or change data (4 tools: are_these_a_market, tron_address_facts, chain_params and wayback_check), but cannot delete data. 2 tools only read.
2 tools bring in text other people can write (fetch_free and fetch_with_receipt); 4 tools can send data out of your system (fetch_free, trc20_transfer_cost, wayback_check and 1 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Nov 5, 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.
7 tools
Can't be undone 1Claude Code: ask
trc20_transfer_costWhat a USDT-TRC20 transfer costs the sender right now: energy band (activated vs new recipient), TRX burned at the live chain price, and whether the recipient is activated.Can send data outNo findings
Why it is in this group
- The name "trc20_transfer_cost" says "transfer": a word for a change that another call does not undo.
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it What a USDT-TRC20 transfer costs the sender right now: energy band (activated vs new recipient), TRX burned at the live chain price, and whether the recipient is activated. Free.
Changes things 4Claude Code: ask
are_these_a_marketGiven up to 8 TRON addresses, report how many PAYER addresses they share (shared_share).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Given up to 8 TRON addresses, report how many PAYER addresses they share (shared_share). High means they are a few wallets transacting with each other, not independent businesses. Free.
chain_paramsLive TRON chain parameters (getEnergyFee, fees, memo fee) with a signed receipt.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Live TRON chain parameters (getEnergyFee, fees, memo fee) with a signed receipt. Free.
tron_address_factsPublic chain facts about a TRON address before you send USDT to it: activated or not, age, TRX balance, USDT balance, transaction count.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Public chain facts about a TRON address before you send USDT to it: activated or not, age, TRX balance, USDT balance, transaction count. Free.
wayback_checkHas the Wayback Machine archived this URL, and when.Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Has the Wayback Machine archived this URL, and when. Free.
Only reads 2Show 2 read-only tools
fetch_freeFree signed fetch of an allowlisted public URL (no key, no account).Reads text others writeCan send data outNo findings
Why it is in this group
- The name "fetch_free" says "fetch": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it Free signed fetch of an allowlisted public URL (no key, no account). Returns http_status, bytes, sha256, preview and an ES256 signature.
fetch_with_receiptPAID (5 USDT TRC20 buys ten URL-days): one public URL fetched once, with a signed receipt: status, bytes, sha256, content-type, elapsed ms, UTC times.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "fetch_with_receipt" says "fetch": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it PAID (5 USDT TRC20 buys ten URL-days): one public URL fetched once, with a signed receipt: status, bytes, sha256, content-type, elapsed ms, UTC times. Calling this free tool explains exactly how to pay and what you get.
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.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out4
- 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 19, 2026, 17:23 UTC, unchanged since Nov 12, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- 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
The probe stopped: expanded-oven-hardwood-cheque.trycloudflare.com does not resolve.
Posture changes
- Nov 12, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 5 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://expanded-oven-hardwood-cheque.trycloudflare.com/.well-known/oauth-protected-resource/mcp to none
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.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 3 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 5 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://expanded-oven-hardwood-cheque.trycloudflare.com/.well-known/oauth-protected-resource/mcp to none
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http trc20-instruments https://expanded-oven-hardwood-cheque.trycloudflare.com/mcpclaude mcp add --transport http trc20-instruments https://expanded-oven-hardwood-cheque.trycloudflare.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__trc20-instruments__are_these_a_market",
"mcp__trc20-instruments__fetch_free",
"mcp__trc20-instruments__tron_address_facts",
"mcp__trc20-instruments__trc20_transfer_cost",
"mcp__trc20-instruments__chain_params",
"mcp__trc20-instruments__wayback_check",
"mcp__trc20-instruments__fetch_with_receipt"
],
"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 trc20-instruments. Review it before you use it.
Capability tags behind 4 rules
- mcp__trc20-instruments__fetch_free untrusted-input, outbound
- mcp__trc20-instruments__trc20_transfer_cost outbound
- mcp__trc20-instruments__wayback_check outbound
- mcp__trc20-instruments__fetch_with_receipt untrusted-input, outbound
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/com.trycloudflare.expanded-oven-hardwood-cheque/trc20-instruments/verify?hash=6361110511a9d9574ffbdd0d1d40721d8c895173a30822bb8b5aece55b1969e6" | jq -e '.changed == false'Pinned hash 6361110511a9, from Nov 5, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.trycloudflare.expanded-oven-hardwood-cheque/trc20-instruments/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.trycloudflare.expanded-oven-hardwood-cheque/trc20-instruments)Source: MCP Registry. Synced Nov 5, 2026, 00:17 UTC.
TRC20 payment instruments MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the TRC20 payment instruments MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 5 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 TRC20 payment instruments MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the TRC20 payment instruments MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: trc20_transfer_cost.
What tools does the TRC20 payment instruments MCP server have?
- 7 tools: 1 irreversible, 4 write, 2 read. trc20_transfer_cost, are_these_a_market, tron_address_facts, chain_params, wayback_check, fetch_free and fetch_with_receipt.
Does the TRC20 payment instruments MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the TRC20 payment instruments MCP server send data to outside services?
- 4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): fetch_free, trc20_transfer_cost, wayback_check and fetch_with_receipt.
Has the TRC20 payment instruments MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 5, 2026.