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.

Eagle Virtual USDT & USDC Blacklist Tracker

REMOTE · MCP.EAGLEVIRTUAL.COM

USDT & USDC blacklist, freeze and seizure records for any wallet. Dated, cited, no risk scores.

0 this week 87 Trust /100

Last scanned (12 hours ago)

Scores higher than 94% of remote servers

Reachable. Last reached 7 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 Security83
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1718 tokens (~286/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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.

  • 7 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 3 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 31 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 30 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 23 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • “get_address_status” reworded the description of “address” cosmetic
  • 2 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 30 Sept 26 0
    • Tool “get_coverage” rewrote its description, which is the text the model reads security
    • “get_biggest” reworded the description of “kind” cosmetic
    • “list_freeze_events” reworded the description of “kind” cosmetic
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 7 Nov 2026 · Probed https://mcp.eaglevirtual.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=eaglevirtual.com CN=WE1,O=Google Trust Services,C=US 20 Oct 2026 18 Jan 2027 ECDSA 256 ECDSA-SHA256 80e0941a57af9b130e2b04e6bba84f3a
SANs: eaglevirtual.com, mcp.eaglevirtual.com, *.mcp.eaglevirtual.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.eaglevirtual.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
eaglevirtual.com. DS published 2371 13 Verified
mcp.eaglevirtual.com. Verified address RRset verified with the apex keys
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
strict-transport-security max-age=31536000; includeSubDomains

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.eaglevirtual.com/mcp Verified 200
http (plaintext) http://mcp.eaglevirtual.com/mcp HTTPS enforced 301 https://mcp.eaglevirtual.com/mcp
MCP tools · 6 exposed · ~1,432 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
get_address_status ~234

Check one wallet address against the record of stablecoin blacklistings, freezes and seizures. Returns every recorded action against that address — which issuer took it, on which blockchain, on what date, and in which transaction and block, so it can be verified independently. Covers USDT, USDC and every other coin in this record, on every blockchain it checks. Returns a dated record of what an issuer did, never a risk score, rating, or opinion about the address or its owner. Needs no account.

NameTypeReqDescription
addressstringyesThe wallet address to check, in any format the chain uses. Accepts Ethereum-style addresses (used by Ethereum and many other chains), addresses on Tron, Solana, Stellar, TON, the XRP Ledger, Aptos, S…

No output schema declared.

No examples provided.

get_biggest ~326

The largest recorded stablecoin blacklistings, freezes, seizures and releases, ranked by amount, largest first. Answers "what is the largest blacklist", "the biggest freeze", and "the biggest seizure". Filter by coin, blockchain or kind. A blacklisting or freeze is ranked by the balance the wallet held when it was restricted; a seizure by the balance that was taken. They are two different quantities and each row says which it is. The default scope ranks the 25 latest recorded events, with the wallet, date, block and transaction for each. Set scope to "all_time" for the largest in the whole record, which names no wallet, transaction or block.

NameTypeReqDescription
chainstring–Blockchain name or chain id, e.g. Tron or 1.
kindstring–Restrict to one kind of action. "blacklist" is a deny-list entry in the token contract; "freeze" locks an account; "seizure" took the balance; "release" lifted a restriction; "sanctions" is an on-cha…
limitinteger–Rows to return, up to 50. Defaults to 10.
scopestring–Defaults to "recent": the 25 latest recorded events, with the wallet, block and transaction on every row. "all_time" ranks the whole record from its first event and names no wallet, transaction or bl…
tokenstring–Coin symbol, e.g. USDT. Omit for every coin.

No output schema declared.

No examples provided.

get_coverage ~163

The blockchains and coins covered by this stablecoin blacklist and freeze record, the date of the most recent recorded event, and which blockchains have records that are behind right now, so we cannot vouch for them. Call this to find out whether a chain or coin is in scope before relying on an answer about it, and to check whether any part of the record is behind. `chains_claimed`, `coins_covered`, `contracts_checked` and `companies_checked` are what a check covers; the `coins` array lists only the coins that have at least one recorded event, which is a smaller set. A coin is one name run by one issuer, so a name that two issuers use appears once per issuer, with the issuer after it.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_token_policy ~154

For a given coin, the record of which restriction controls the issuer has actually used — blacklisting, freezing, taking a balance, lifting a restriction — with the on-chain event signature, how many times, and the first and most recent dates. Reports what has happened, dated. It does not report what a contract is capable of: contract capability inspection is not published yet, and this tool says so rather than inferring that a coin cannot freeze from an absence of records. Discloses no wallets.

NameTypeReqDescription
tokenstring–Coin ticker, e.g. USDT, USDC, EURC. A ticker two issuers use returns both coins, each with its issuer. Omit for every coin on record.

No output schema declared.

No examples provided.

get_token_statistics ~210

Counts of recorded stablecoin blacklistings, freezes and seizures — by coin, by blockchain, by month, or by year. Answers questions like "how many wallets has Tether blacklisted", "which coin is frozen most often", and "how many seizures happened in 2025". Returns counts and dates only; no wallet addresses are returned by this tool.

NameTypeReqDescription
chainstring–Optional blockchain name or chain id, e.g. Ethereum or 1.
group_bystring–Which breakdown to return. Defaults to token.
limitinteger–How many coins the by-coin breakdown returns, the coins with the most recorded events first. Defaults to 20, up to 200. The totals count every coin whatever the limit. The other breakdowns are short…
tokenstring–Optional coin ticker, e.g. USDT. A ticker two issuers use returns both coins, each with its issuer. Omit for every coin.

No output schema declared.

No examples provided.

list_freeze_events ~345

The published feed of recent stablecoin blacklist, freeze, seizure, release and on-chain sanctions events, the same rows eaglevirtual.com shows publicly, with the wallet, coin, blockchain, date, block and transaction for each. Covers every coin on every chain: omit the filters and it returns all of them, newest first. Filter by coin, blockchain, event kind or date to narrow it. This is a published sample of the record, not the full corpus, and there is no way to page beyond it. Add month (YYYY-MM) for one whole recorded month: every caller gets the month’s totals, and the events behind them need a paid account. To check a specific wallet, use get_address_status; for totals use get_token_statistics.

NameTypeReqDescription
chainstring–Blockchain name or chain id, e.g. Tron or 1.
kindstring–Restrict to one kind of event. "blacklist" is a deny-list entry in the token contract; "freeze" locks an account; "seizure" took the balance; "release" lifted a restriction; "sanctions" is an on-chai…
limitinteger–Rows to return, up to 100. Defaults to 25.
monthstring–One whole recorded month, YYYY-MM, instead of the recent feed. Every caller gets the month’s totals; the events behind them need a paid account.
sincestring–Only events on or after this date, YYYY-MM-DD.
tokenstring–Coin symbol, e.g. USDT.

No output schema declared.

No examples provided.

Install

How do I install the Eagle Virtual USDT & USDC Blacklist Tracker MCP server?

Eagle Virtual USDT & USDC Blacklist Tracker is a hosted endpoint at https://mcp.eaglevirtual.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 · mcp.eaglevirtual.com

# add to Claude Code
claude mcp add --transport http com-eaglevirtual-stablecoin-freeze-tracker 'https://mcp.eaglevirtual.com/mcp'
Common questions

What is the Eagle Virtual USDT & USDC Blacklist Tracker MCP server?

Eagle Virtual USDT & USDC Blacklist Tracker is an MCP server listed in the public MCP registry as com.eaglevirtual/stablecoin-freeze-tracker. USDT & USDC blacklist, freeze and seizure records for any wallet. Dated, cited, no risk scores. This page covers its hosted endpoint (https://mcp.eaglevirtual.com/mcp).

Is the Eagle Virtual USDT & USDC Blacklist Tracker MCP server safe to use?

Eagle Virtual USDT & USDC Blacklist Tracker scores 87 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 Eagle Virtual USDT & USDC Blacklist Tracker MCP server expose?

Eagle Virtual USDT & USDC Blacklist Tracker exposes 6 tools: get_address_status, get_token_statistics, get_token_policy, get_coverage, list_freeze_events, get_biggest. Their descriptions and schemas cost roughly 1,432 tokens of context every time the server is loaded.

Does the Eagle Virtual USDT & USDC Blacklist Tracker MCP server require authentication?

No. We connected to Eagle Virtual USDT & USDC Blacklist Tracker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Eagle Virtual USDT & USDC Blacklist Tracker MCP server still maintained?

Eagle Virtual USDT & USDC Blacklist Tracker is still listed as active in the MCP registry. We last reached this channel on 7 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 Eagle Virtual USDT & USDC Blacklist Tracker MCP server?

VerifyMCP ran 13 checks on Eagle Virtual USDT & USDC Blacklist Tracker, 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.