# LIGHTHOUSE (МАЯК) — USDT freeze risk (remote · usdtbanned.com)

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

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `usdtbanned.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/com-usdtbanned-mayak/usdtbanned.md), [page](https://verifymcp.io/servers/com-usdtbanned-mayak/usdtbanned)

## Channel facts

- Endpoint: `https://usdtbanned.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (watchlist_remove).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - 33% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1785 tokens (~93/item across 19 items; 15 tools + 4 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 87% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

### Claude

```bash
claude mcp add --transport http com-usdtbanned-mayak 'https://usdtbanned.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-usdtbanned-mayak": {
      "url": "https://usdtbanned.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-usdtbanned-mayak": {
      "type": "http",
      "url": "https://usdtbanned.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-usdtbanned-mayak]
url = "https://usdtbanned.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-usdtbanned-mayak": {
      "type": "remote",
      "url": "https://usdtbanned.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-usdtbanned-mayak --url 'https://usdtbanned.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-usdtbanned-mayak:
    url: "https://usdtbanned.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-usdtbanned-mayak": {
      "Transport": "http",
      "Url": "https://usdtbanned.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-usdtbanned-mayak -t streamable-http -u 'https://usdtbanned.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-usdtbanned-mayak": {
      "type": "http",
      "url": "https://usdtbanned.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 64, +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.

### 2026-11-19 (score 63, +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.

### 2026-11-18 (score 62, 0)

- [security] Tool “check_address” rewrote its description, which is the text the model reads

### 2026-11-17 (score 62, +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.

### 2026-11-16 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-15 (score 61)

First indexed and scored.

## MCP tools (15)

### `check_address` (~214 tokens)

Check USDT freeze risk

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.

Input parameters:

- `address` (string, required): Address: 0x… (Ethereum/Avalanche/Celo), T… (Tron), TON (EQ…/UQ…) or Solana base58.
- `lang` (string): Language of texts in the result. Default: Russian unless the client prefers English.
- `live` (boolean): Also read status and balance from a node right now (default true). false is faster.

### `check_addresses` (~91 tokens)

Batch check USDT freeze risk

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.

Input parameters:

- `addresses` (array, required): Addresses to check.
- `lang` (string): Language of texts in the result. Default: Russian unless the client prefers English.

### `get_freeze_statistics` (~90 tokens)

USDT blacklist statistics

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.

Input parameters:

- `lang` (string): Language of texts in the result. Default: Russian unless the client prefers English.

### `search` (~64 tokens)

Search LIGHTHOUSE

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.

Input parameters:

- `query` (string, required): Address or keywords.

### `fetch` (~42 tokens)

Fetch LIGHTHOUSE record

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

Input parameters:

- `id` (string, required): Id from search results.

### `list_open_proposals` (~113 tokens)

Open Tether freeze proposals

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.

Input parameters:

- `chain` (string): Optional chain filter.
- `lang` (string): Language of texts in the result. Default: Russian unless the client prefers English.

### `list_recent_freezes` (~109 tokens)

Recent USDT freezes

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.

Input parameters:

- `chain` (string): Optional chain filter.
- `lang` (string): Language of texts in the result. Default: Russian unless the client prefers English.
- `limit` (integer): Default 20.
- `op` (string): Operation type, default add (freeze).

### `get_account` (~55 tokens)

My LIGHTHOUSE account

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

Input parameters:

- `lang` (string): Language of texts in the result. Default: Russian unless the client prefers English.

### `watchlist_list` (~57 tokens)

My monitored addresses

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

Input parameters:

- `lang` (string): Language of texts in the result. Default: Russian unless the client prefers English.

### `watchlist_add` (~114 tokens)

Add address to monitoring

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.

Input parameters:

- `address` (string, required)
- `lang` (string): Language of texts in the result. Default: Russian unless the client prefers English.
- `note` (string): Optional label, e.g. 'hot wallet'.

### `watchlist_remove` (~53 tokens)

Remove address from monitoring

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

Input parameters:

- `address` (string, required)
- `lang` (string): Language of texts in the result. Default: Russian unless the client prefers English.

### `get_plans` (~107 tokens)

LIGHTHOUSE plans and payment methods

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.

Input parameters:

- `lang` (string): Language of texts in the result. Default: Russian unless the client prefers English.

### `create_order` (~254 tokens)

Buy a LIGHTHOUSE plan with crypto

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.

Input parameters:

- `extend` (boolean): Extend the signed-in user's existing API key instead of issuing a new one.
- `lang` (string): Language of texts in the result. Default: Russian unless the client prefers English.
- `payment_method` (string): Default usdt_trc20.
- `plan` (string, required): api30: 30 days, api365: 1 year. Both include an API key, dashboard, webhooks and monitoring of up to 10 addresses (monitoring needs sign-in).

### `submit_payment` (~123 tokens)

Submit a USDT payment for an order

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.

Input parameters:

- `lang` (string): Language of texts in the result. Default: Russian unless the client prefers English.
- `order_id` (string, required)
- `tx_hash` (string, required): Tron transaction id, 64 hex characters.

### `get_order` (~81 tokens)

Order status and API key

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.

Input parameters:

- `lang` (string): Language of texts in the result. Default: Russian unless the client prefers English.
- `order_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-usdtbanned-mayak/usdtbanned#diagnostics

## Score history

- 2026-11-21: 64
- 2026-11-20: 63
- 2026-11-19: 63
- 2026-11-18: 62
- 2026-11-17: 62
- 2026-11-16: 61
- 2026-11-15: 61

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

## Links

- Remote endpoint: https://usdtbanned.com/mcp
- Website: https://usdtbanned.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-usdtbanned-mayak/usdtbanned.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-usdtbanned-mayak/usdtbanned/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-usdtbanned-mayak/usdtbanned.json
- HTML version of this page: https://verifymcp.io/servers/com-usdtbanned-mayak/usdtbanned
