Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

LIGHTHOUSE (МАЯК) — USDT freeze risk

REMOTE · USDTBANNED.COM

USDT freeze risk for any address: Tether blacklist status and open multisig freeze proposals.

Available components

64 Trust /100

Last scanned (23 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability57
  • 33% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1785 tokens (~93/item across 19 items; 15 tools + 4 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 87% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 0
    • Tool “check_address” rewrote its description, which is the text the model reads security
  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 15 Nov 26 61

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://usdtbanned.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usdtbanned.com CN=YE2,O=Let's Encrypt,C=US 15 Nov 2026 13 Feb 2027 ECDSA 256 ECDSA-SHA384 6eb3b5ea5b58347a46796ceb85c3f53a9e6
SANs: usdtbanned.com, www.usdtbanned.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of usdtbanned.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
usdtbanned.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://usdtbanned.com/mcp Verified 200
http (plaintext) http://usdtbanned.com/mcp HTTPS enforced 301 https://usdtbanned.com/mcp
MCP tools · 15 exposed · ~1,567 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_address ~214

Check available signals of a USDT (Tether) freeze. Covers Ethereum, Tron, Avalanche, Celo, Solana and TON. Returns risk level 0–3 (0 no signals found, not a safety guarantee; 1 freeze proposal open; 2 second of three signatures; 3 evidence of a freeze), recommended manual review, per-chain reasons and freshness, USDT balance, open proposals and past episodes. Timing, completeness and future execution are not guaranteed. Use for counterparty due diligence or checking whether an address has freeze signals. Does not authorise or perform asset operations.

NameTypeReqDescription
addressstringyesAddress: 0x… (Ethereum/Avalanche/Celo), T… (Tron), TON (EQ…/UQ…) or Solana base58.
langstring–Language of texts in the result. Default: Russian unless the client prefers English.
liveboolean–Also read status and balance from a node right now (default true). false is faster.

No output schema declared.

No examples provided.

check_addresses ~91

Check up to 20 addresses at once for USDT freeze risk (database check without live node calls). Returns level 0–3, label and action for each address, sorted by risk. Use for screening payout lists, deposit addresses or CSV exports.

NameTypeReqDescription
addressesarrayyesAddresses to check.
langstring–Language of texts in the result. Default: Russian unless the client prefers English.

No output schema declared.

No examples provided.

create_order ~254

Create an order for a LIGHTHOUSE plan paid in crypto. payment_method=usdt_trc20 (default): returns the Tron address and the exact USDT amount (unique cents identify the order), valid 60 minutes; after sending, call submit_payment with the tx hash, then get_order returns the API key. payment_method=x402: returns x402 v2 PaymentRequired (USDC on Base); retry the same call with the signed payload in _meta["x402/payment"] and the API key is returned immediately. Without sign-in the key is not linked to an account; extend=true requires sign-in; monitoring needs the key to be linked to an account. Never send funds without the user's explicit approval.

NameTypeReqDescription
extendboolean–Extend the signed-in user's existing API key instead of issuing a new one.
langstring–Language of texts in the result. Default: Russian unless the client prefers English.
payment_methodstring–Default usdt_trc20.
planstringyesapi30: 30 days, api365: 1 year. Both include an API key, dashboard, webhooks and monitoring of up to 10 addresses (monitoring needs sign-in).

No output schema declared.

No examples provided.

fetch ~42

Fetch the full text of a search result by id (address:<address>, doc:<name> or stats:overview).

NameTypeReqDescription
idstringyesId from search results.

No output schema declared.

No examples provided.

get_account ~55

Show the signed-in user's LIGHTHOUSE plan, expiry dates, monitoring subscription and how many addresses are monitored. Requires sign-in.

NameTypeReqDescription
langstring–Language of texts in the result. Default: Russian unless the client prefers English.

No output schema declared.

No examples provided.

get_freeze_statistics ~90

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

NameTypeReqDescription
langstring–Language of texts in the result. Default: Russian unless the client prefers English.

No output schema declared.

No examples provided.

get_order ~81

Get the status of a LIGHTHOUSE order (pending, paid, expired). When paid, returns the API key (for api plans) or the monitoring expiry (for watch plans). Checks incoming transfers on each call.

NameTypeReqDescription
langstring–Language of texts in the result. Default: Russian unless the client prefers English.
order_idstringyes–

No output schema declared.

No examples provided.

get_plans ~107

List 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). Address checks are free; buy a plan when you need the REST API at scale, open freeze proposals or monitoring.

NameTypeReqDescription
langstring–Language of texts in the result. Default: Russian unless the client prefers English.

No output schema declared.

No examples provided.

list_open_proposals ~113

List freeze (addBlackList) and unfreeze proposals that are open in Tether multisigs but not yet executed — the early-warning signal before an address is frozen. Each item has address, chain, signatures collected/required, age, probability of execution within 10 min and 1 h, and USDT amount at risk. Requires sign-in.

NameTypeReqDescription
chainstring–Optional chain filter.
langstring–Language of texts in the result. Default: Russian unless the client prefers English.

No output schema declared.

No examples provided.

list_recent_freezes ~109

Log of executed blacklist operations, newest first: freezes (add), unfreezes (rem) or fund destructions (des), with address, chain, time, delay from proposal and amount. Requires sign-in.

NameTypeReqDescription
chainstring–Optional chain filter.
langstring–Language of texts in the result. Default: Russian unless the client prefers English.
limitinteger–Default 20.
opstring–Operation type, default add (freeze).

No output schema declared.

No examples provided.

search ~64

Search 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). Returns result ids for the fetch tool.

NameTypeReqDescription
querystringyesAddress or keywords.

No output schema declared.

No examples provided.

submit_payment ~123

After sending USDT TRC-20 for an order, pass the order_id and the Tron transaction hash. The service finds the transfer on-chain, checks recipient and exact amount and, once confirmed (~1 minute), issues or extends the API key. Returns a verdict: paid, unconfirmed, wrong_amount, wrong_recipient or not_found.

NameTypeReqDescription
langstring–Language of texts in the result. Default: Russian unless the client prefers English.
order_idstringyes–
tx_hashstringyesTron transaction id, 64 hex characters.

No output schema declared.

No examples provided.

watchlist_add ~114

Put an address on LIGHTHOUSE monitoring (up to 10 per account). Risk is re-checked every 10 minutes and right after Tether multisig events; the user gets a Telegram or e-mail notification when the level changes. Requires sign-in and an active monitoring subscription or LIGHTHOUSE plan.

NameTypeReqDescription
addressstringyes–
langstring–Language of texts in the result. Default: Russian unless the client prefers English.
notestring–Optional label, e.g. 'hot wallet'.

No output schema declared.

No examples provided.

watchlist_list ~57

List the user's addresses on LIGHTHOUSE monitoring with their current risk level, last check time and last level change. Requires sign-in.

NameTypeReqDescription
langstring–Language of texts in the result. Default: Russian unless the client prefers English.

No output schema declared.

No examples provided.

watchlist_remove ~53

Remove an address from the user's LIGHTHOUSE monitoring list. Requires sign-in.

NameTypeReqDescription
addressstringyes–
langstring–Language of texts in the result. Default: Russian unless the client prefers English.

No output schema declared.

No examples provided.

Install

How do I install the LIGHTHOUSE (МАЯК) — USDT freeze risk MCP server?

LIGHTHOUSE (МАЯК) — USDT freeze risk is a hosted endpoint at https://usdtbanned.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · usdtbanned.com

# add to Claude Code
claude mcp add --transport http com-usdtbanned-mayak 'https://usdtbanned.com/mcp'
Common questions

What is the LIGHTHOUSE (МАЯК) — USDT freeze risk MCP server?

LIGHTHOUSE (МАЯК) — USDT freeze risk is an MCP server listed in the public MCP registry as com.usdtbanned/mayak. USDT freeze risk for any address: Tether blacklist status and open multisig freeze proposals. This page covers its hosted endpoint (https://usdtbanned.com/mcp).

Is the LIGHTHOUSE (МАЯК) — USDT freeze risk MCP server safe to use?

LIGHTHOUSE (МАЯК) — USDT freeze risk scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the LIGHTHOUSE (МАЯК) — USDT freeze risk MCP server expose?

LIGHTHOUSE (МАЯК) — USDT freeze risk exposes 15 tools: check_address, check_addresses, get_freeze_statistics, search, fetch, and 10 more. Their descriptions and schemas cost roughly 1,567 tokens of context every time the server is loaded.

Does the LIGHTHOUSE (МАЯК) — USDT freeze risk MCP server require authentication?

No. We connected to LIGHTHOUSE (МАЯК) — USDT freeze risk without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the LIGHTHOUSE (МАЯК) — USDT freeze risk MCP server still maintained?

LIGHTHOUSE (МАЯК) — USDT freeze risk is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the LIGHTHOUSE (МАЯК) — USDT freeze risk MCP server?

VerifyMCP ran 13 checks on LIGHTHOUSE (МАЯК) — USDT freeze risk, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.