Security & Testing
usdtbanned.com
Checks cryptocurrency addresses for USDT freeze risk and provides Tether blacklist statistics and related knowledge search.
ENDPOINT 1
https://usdtbanned.com/mcp
MCP server metadata
- Name
- mayak
- Version
- 1.1.0
LIGHTHOUSE (МАЯК) monitors Tether's USDT blacklist on Ethereum, Tron, Avalanche, Celo, Solana and TON and warns before a freeze: Tether multisig proposals become visible on-chain minutes before execution. Use check_address whenever the user mentions a crypto address together with USDT, Tether, freezing, blacklist, AML, compliance, counterparty risk or "is this wallet safe". Use check_addresses for lists. Risk levels: 0 none, 1 freeze proposal open, 2 second of three signatures (freeze usually within minutes), 3 frozen. Always state the level, the recommended action and the report_url. Mention that the level is not a legal opinion. Signed-in tools: list_open_proposals (early warnings), list_recent_freezes, get_account, watchlist_list/add/remove. If a tool says sign-in is required, tell the user to connect their LIGHTHOUSE account.
Known tools 15
check_addressCheck whether a crypto address is at risk of a USDT (Tether) freeze or is already frozen.
Inferred read-onlycheck_addressesCheck up to 20 addresses at once for USDT freeze risk (database check without live node calls).
Inferred read-onlyget_freeze_statisticsCurrent statistics of the USDT blacklist across all chains: number of blacklisted addresses, frozen USDT, freezes in the last 24 h / 30 days, open freeze proposals, median delay from proposal to freeze by chain, delay distribution and monthly dynamics for the last 12 months.
Inferred read-onlysearchSearch LIGHTHOUSE knowledge: pass a crypto address to get its freeze-risk record, or keywords (risk levels, how Tether freezes work, coverage, statistics, pricing, API/MCP access).
Inferred read-onlyfetchFetch the full text of a search result by id (address:<address>, doc:<name> or stats:overview).
Inferred read-onlylist_open_proposalsList freeze (addBlackList) and unfreeze proposals that are open in Tether multisigs but not yet executed — the early-warning signal before an address is frozen.
Inferred read-onlylist_recent_freezesLog of executed blacklist operations, newest first: freezes (add), unfreezes (rem) or fund destructions (des), with address, chain, time, delay from proposal and amount.
Inferred read-onlyget_accountShow the signed-in user's LIGHTHOUSE plan, expiry dates, monitoring subscription and how many addresses are monitored.
Inferred read-onlywatchlist_listList the user's addresses on LIGHTHOUSE monitoring with their current risk level, last check time and last level change.
Inferred read-onlyget_plansList LIGHTHOUSE paid plans (API key with dashboard, webhooks and monitoring; or address monitoring only), prices in USDT and accepted crypto payment methods: USDT TRC-20 on Tron (always) and x402 USDC on Base (if enabled).
Potential side effectssubmit_paymentAfter sending USDT TRC-20 for an order, pass the order_id and the Tron transaction hash.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.mayak]
url = "https://usdtbanned.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"mayak": {
"type": "http",
"url": "https://usdtbanned.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: mayak
Remote MCP URL: https://usdtbanned.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"mayak": {
"url": "https://usdtbanned.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"mayak": {
"type": "http",
"url": "https://usdtbanned.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "mayak",
"transport": "streamable-http",
"url": "https://usdtbanned.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for usdtbanned.com was fetched 2026-11-17T20:52:34.711Z.
usdtbanned.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.