Eagle Virtual USDT & USDC Blacklist Tracker
REMOTE · MCP.EAGLEVIRTUAL.COM · SCANNED SEP 20
USDT & USDC blacklist, freeze and seizure records for any wallet. Dated, cited, no risk scores.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1472 tokens (~245/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 Management76
- Stability check failed: schema churn in the 27 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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
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
claude mcp add --transport http com-eaglevirtual-stablecoin-freeze-tracker 'https://mcp.eaglevirtual.com/mcp'
{
"mcpServers": {
"com-eaglevirtual-stablecoin-freeze-tracker": {
"url": "https://mcp.eaglevirtual.com/mcp"
}
}
} {
"servers": {
"com-eaglevirtual-stablecoin-freeze-tracker": {
"type": "http",
"url": "https://mcp.eaglevirtual.com/mcp"
}
}
} [mcp_servers.com-eaglevirtual-stablecoin-freeze-tracker] url = "https://mcp.eaglevirtual.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-eaglevirtual-stablecoin-freeze-tracker": {
"type": "remote",
"url": "https://mcp.eaglevirtual.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-eaglevirtual-stablecoin-freeze-tracker --url 'https://mcp.eaglevirtual.com/mcp' --transport streamable-http
mcp_servers:
com-eaglevirtual-stablecoin-freeze-tracker:
url: "https://mcp.eaglevirtual.com/mcp" {
"McpServers": {
"com-eaglevirtual-stablecoin-freeze-tracker": {
"Transport": "http",
"Url": "https://mcp.eaglevirtual.com/mcp"
}
}
} assistant mcp add com-eaglevirtual-stablecoin-freeze-tracker -t streamable-http -u 'https://mcp.eaglevirtual.com/mcp'
{
"mcpServers": {
"com-eaglevirtual-stablecoin-freeze-tracker": {
"type": "http",
"url": "https://mcp.eaglevirtual.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
- Server version: 1.1.2 → 1.1.3 functional
- 18 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.1.1 → 1.1.2 functional
- 17 Sept 26 +1
- Tool “get_biggest” rewrote its description, which is the text the model reads security
- Tool “list_freeze_events” rewrote its description, which is the text the model reads security
- “get_biggest” reworded the description of “scope” cosmetic
- “list_freeze_events” reworded the description of “month” cosmetic
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 59 to 62.
- 15 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_biggest” rewrote its description, which is the text the model reads security
- “get_biggest” reworded the description of “scope” cosmetic
- 14 Sept 26 +1
- Server version: 1.1.0 → 1.1.1 functional
- 13 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_address_status” rewrote its description, which is the text the model reads security
- Tool “get_coverage” rewrote its description, which is the text the model reads security
- Tool “get_token_policy” rewrote its description, which is the text the model reads security
- Tool “list_freeze_events” rewrote its description, which is the text the model reads security
- Server version: 1.0.0 → 1.1.0 functional
- “list_freeze_events” added an optional parameter “month” cosmetic
- “get_token_policy” reworded the description of “token” cosmetic
- “get_token_statistics” reworded the description of “token” cosmetic
- 12 Sept 26 +1
- Tool “get_biggest” rewrote its description, which is the text the model reads security
- “get_biggest” reworded the description of “scope” cosmetic
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 20 Sept 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 | 22 Aug 2026 | 20 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 1ba5ee37279428aa0e4121cdef1932b1 |
| 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. | present | 19718 | 13 | Verified |
| eaglevirtual.com. | present | 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 |
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 →
get_address_status Check whether a wallet has been blacklisted or frozen ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The wallet address to check, in any format the chain uses. Accepts EVM, TRON, Solana and Stellar forms; casing does not matter. |
No output schema declared.
No examples provided.
get_biggest Largest recorded stablecoin seizures, freezes and blacklistings ~308
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Blockchain name or chain id, e.g. Tron or 1. |
| kind | string | – | Restrict to one kind of action. "blacklist" is a deny-list entry in the token contract; "freeze" locks an account; "seizure" took the balance. Omit for all. |
| limit | integer | – | Rows to return, up to 50. Defaults to 10. |
| scope | string | – | 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… |
| token | string | – | Coin symbol, e.g. USDT. Omit for every coin. |
No output schema declared.
No examples provided.
get_coverage Which blockchains and stablecoins are covered, and how current ~153
The blockchains and coins covered by this stablecoin blacklist and freeze record, the date of the most recent recorded event, and which lanes we cannot currently vouch for. 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 Which blacklist and freeze controls a stablecoin issuer has used ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | 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 Stablecoin blacklist and freeze statistics ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Optional blockchain name or chain id, e.g. Ethereum or 1. |
| group_by | string | – | Which breakdown to return. Defaults to token. |
| token | string | – | 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 Recent stablecoin blacklistings and freezes ~286
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: the month’s totals on every plan, and every event behind them on the Business plan. To check a specific wallet, use get_address_status; for totals use get_token_statistics.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Blockchain name or chain id, e.g. Tron or 1. |
| kind | string | – | Restrict to one kind of event. |
| limit | integer | – | Rows to return, up to 100. Defaults to 25. |
| month | string | – | One whole recorded month, YYYY-MM, instead of the recent feed. Every caller gets the month’s totals; the events behind them come with the Business plan. |
| since | string | – | Only events on or after this date, YYYY-MM-DD. |
| token | string | – | Coin symbol, e.g. USDT. |
No output schema declared.
No examples provided.
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 84 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,205 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.