Skip to content

Eagle Virtual USDT & USDC Blacklist Tracker MCP server

com.eaglevirtual/stablecoin-freeze-trackereaglevirtual.comstreamable-httpv1.1.4Scanned

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

6 tools: 6 only read.

Tools: 0 delete, 0 irreversible, 0 write, 6 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Eagle Virtual USDT & USDC Blacklist Tracker MCP server can do

The Eagle Virtual USDT & USDC Blacklist Tracker MCP server is published by eaglevirtual.com, a domain the MCP Registry verified. It has 6 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 13, 2026, version 1.1.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Only reads 6Show 6 read-only tools
  • get_address_statusCheck one wallet address against the record of stablecoin blacklistings, freezes and seizures.No findings

    Why it is in this group

    • The name "get_address_status" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check whether a wallet has been blacklisted or frozen
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • get_biggestThe largest recorded stablecoin blacklistings, freezes, seizures and releases, ranked by amount, largest first.No findings

    Why it is in this group

    • The name "get_biggest" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Largest recorded stablecoin seizures, freezes and blacklistings
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • get_coverageThe 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 rig…No findings

    Why it is in this group

    • The name "get_coverage" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Which blockchains and stablecoins are covered, and how current
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • get_token_policyFor 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 …No findings

    Why it is in this group

    • The name "get_token_policy" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Which blacklist and freeze controls a stablecoin issuer has used
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • get_token_statisticsCounts of recorded stablecoin blacklistings, freezes and seizures — by coin, by blockchain, by month, or by year.No findings

    Why it is in this group

    • The name "get_token_statistics" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Stablecoin blacklist and freeze statistics
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • list_freeze_eventsThe 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, blo…No findings

    Why it is in this group

    • The name "list_freeze_events" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Recent stablecoin blacklistings and freezes
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:37 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.eaglevirtual.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://eaglevirtual.com
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
yes

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.1.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http stablecoin-freeze-tracker https://mcp.eaglevirtual.com/mcp
claude mcp add --transport http stablecoin-freeze-tracker https://mcp.eaglevirtual.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__stablecoin-freeze-tracker__get_address_status",
      "mcp__stablecoin-freeze-tracker__get_token_statistics",
      "mcp__stablecoin-freeze-tracker__get_token_policy",
      "mcp__stablecoin-freeze-tracker__get_coverage",
      "mcp__stablecoin-freeze-tracker__list_freeze_events",
      "mcp__stablecoin-freeze-tracker__get_biggest"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as stablecoin-freeze-tracker. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.eaglevirtual/stablecoin-freeze-tracker/verify?hash=2c121953c72a6a4e4089be8ffb9b5db95f53d45afa6c1917273e6792558700a1" | jq -e '.changed == false'

Pinned hash 2c121953c72a, from Nov 13, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.eaglevirtual/stablecoin-freeze-tracker/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.eaglevirtual/stablecoin-freeze-tracker
[![Anlyon Radar](https://radar.anlyon.com/badge/com.eaglevirtual/stablecoin-freeze-tracker.svg)](https://radar.anlyon.com/servers/com.eaglevirtual/stablecoin-freeze-tracker)

Source: MCP Registry. Synced Oct 21, 2026, 17:54 UTC.

Eagle Virtual USDT & USDC Blacklist Tracker MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 6 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Eagle Virtual USDT & USDC Blacklist Tracker MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Eagle Virtual USDT & USDC Blacklist Tracker MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Eagle Virtual USDT & USDC Blacklist Tracker MCP server have?

6 tools: 6 read. get_address_status, get_token_statistics, get_token_policy, get_coverage, list_freeze_events and get_biggest.

Does the Eagle Virtual USDT & USDC Blacklist Tracker MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Eagle Virtual USDT & USDC Blacklist Tracker MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Eagle Virtual USDT & USDC Blacklist Tracker MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 31, 2026. Every change is on this page and in its Atom feed.