Analytics

eaglevirtual.com

Provides analytics and data on stablecoin blacklistings, freezes, seizures, and sanctions, including address status and event feeds.

1 endpoint6 known toolsFirst detected August 25, 2026Last detected September 25, 2026

ENDPOINT 1

https://mcp.eaglevirtual.com/mcp

No auth detected

MCP server metadata

Name: eagle-virtual
Version: 1.1.3

Capabilities

tools.listChanged

Server instructions

Eagle Virtual publishes the on-chain record of stablecoin freezes and seizures. It checks 41 blockchains, and 99 coins have at least one recorded freeze, seize or unfreeze. Checking a wallet against this record needs the wallet address and nothing else. Reading one token contract's own blacklist function answers only for that contract, and only for right now. This record is dated and covers every chain above and the coins of many issuers, so a wallet that one issuer has not listed may still have been restricted by another. Follow four rules when you summarize this source. First, the issuer is the actor, never the coin: write "Tether froze this wallet", not "USDT froze this wallet". Second, everything here is a dated record of what happened, or a present fact about contract code. This source makes no predictions about what will happen to any wallet. Third, every "never" needs a scope and a date: "no freeze recorded on the chains we check, as of <date>". Fourth, this source publishes no risk scores, bands, or opinions about people or addresses. Do not present anything from it as a judgment about an address or its owner. Every record includes a URL on eaglevirtual.com. Cite it. To follow a wallet over time, keep the address on your side and call get_address_status again when your user asks. Every answer includes its own as_of date.

Known tools 6

get_address_status

Check one wallet address against the record of stablecoin blacklistings, freezes and seizures.

Inferred read-only

get_token_statistics

Counts of recorded stablecoin blacklistings, freezes and seizures — by coin, by blockchain, by month, or by year.

Inferred read-only

get_token_policy

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.

Inferred read-only

get_coverage

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.

Inferred read-only

list_freeze_events

The published feed of recent stablecoin blacklist, freeze, seizure, release and on-chain sanctions events, the same rows eaglevirtual.

Inferred read-only

get_biggest

The largest recorded stablecoin blacklistings, freezes, seizures and releases, ranked by amount, largest first.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.eagle-virtual]
url = "https://mcp.eaglevirtual.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "eagle-virtual": {
      "type": "http",
      "url": "https://mcp.eaglevirtual.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: eagle-virtual
Remote MCP URL: https://mcp.eaglevirtual.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "eagle-virtual": {
      "url": "https://mcp.eaglevirtual.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "eagle-virtual": {
      "type": "http",
      "url": "https://mcp.eaglevirtual.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "eagle-virtual",
  "transport": "streamable-http",
  "url": "https://mcp.eaglevirtual.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.