# io.github.CloudCorpRecords/freezeledger (npm · @reneturcios/freezeledger)

Published stablecoin freeze record: blacklist, freeze and seizure events, policies and statistics.

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

## Components

- npm · `@reneturcios/freezeledger`: 69/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-freezeledger/reneturcios-freezeledger.md), [page](https://verifymcp.io/servers/cloudcorprecords-freezeledger/reneturcios-freezeledger)
- oci · `ghcr.io/cloudcorprecords/freezeledger`: 41/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-freezeledger/ghcr-io-cloudcorprecords-freezeledger.md), [page](https://verifymcp.io/servers/cloudcorprecords-freezeledger/ghcr-io-cloudcorprecords-freezeledger)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/freezeledger`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1432 tokens (~238/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.CloudCorpRecords/freezeledger MCP server?

io.github.CloudCorpRecords/freezeledger runs locally as an npm package, launched with npx -y @reneturcios/freezeledger mcp. 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 cloudcorprecords-freezeledger -- npx -y @reneturcios/freezeledger mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-freezeledger": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/freezeledger",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-freezeledger": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/freezeledger",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-freezeledger -- npx -y @reneturcios/freezeledger mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-freezeledger": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/freezeledger",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-freezeledger --command npx --arg -y --arg @reneturcios/freezeledger --arg mcp
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-freezeledger:
    command: "npx"
    args: ["-y", "@reneturcios/freezeledger", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-freezeledger": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/freezeledger",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-freezeledger -t stdio -c npx -a -y @reneturcios/freezeledger mcp
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-freezeledger": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/freezeledger",
        "mcp"
      ]
    }
  }
}
```

## 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-20 (score 69, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-19 (score 69, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-18 (score 69, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-17 (score 54)

First indexed and scored.

## MCP tools (6)

### `get_address_status` (~234 tokens)

Check whether a wallet has been blacklisted or frozen

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.

Input parameters:

- `address` (string, required): The 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…

### `get_token_statistics` (~210 tokens)

Stablecoin blacklist and freeze statistics

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.

Input parameters:

- `chain` (string): Optional blockchain name or chain id, e.g. Ethereum or 1.
- `group_by` (string): Which breakdown to return. Defaults to token.
- `limit` (integer): 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…
- `token` (string): Optional coin ticker, e.g. USDT. A ticker two issuers use returns both coins, each with its issuer. Omit for every coin.

### `get_token_policy` (~154 tokens)

Which blacklist and freeze controls a stablecoin issuer has used

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.

Input parameters:

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

### `get_coverage` (~163 tokens)

Which blockchains and stablecoins are covered, and how current

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.

### `list_freeze_events` (~345 tokens)

Recent stablecoin blacklistings and freezes

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.

Input parameters:

- `chain` (string): Blockchain name or chain id, e.g. Tron or 1.
- `kind` (string): 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…
- `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 need a paid account.
- `since` (string): Only events on or after this date, YYYY-MM-DD.
- `token` (string): Coin symbol, e.g. USDT.

### `get_biggest` (~326 tokens)

Largest recorded stablecoin seizures, freezes and blacklistings

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.

Input parameters:

- `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; "release" lifted a restriction; "sanctions" is an on-cha…
- `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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-freezeledger/reneturcios-freezeledger#diagnostics

## Score history

- 2026-11-21: 69
- 2026-11-20: 69
- 2026-11-19: 69
- 2026-11-18: 69
- 2026-11-17: 54

## Common questions

### What is the io.github.CloudCorpRecords/freezeledger MCP server?

io.github.CloudCorpRecords/freezeledger is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/freezeledger. Published stablecoin freeze record: blacklist, freeze and seizure events, policies and statistics. This page covers its npm package (@reneturcios/freezeledger).

### Is the io.github.CloudCorpRecords/freezeledger MCP server safe to use?

io.github.CloudCorpRecords/freezeledger scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.CloudCorpRecords/freezeledger MCP server expose?

io.github.CloudCorpRecords/freezeledger 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.

### Is the io.github.CloudCorpRecords/freezeledger MCP server still maintained?

io.github.CloudCorpRecords/freezeledger 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 licence is the io.github.CloudCorpRecords/freezeledger MCP server under?

io.github.CloudCorpRecords/freezeledger declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.CloudCorpRecords/freezeledger MCP server?

VerifyMCP ran 15 checks on io.github.CloudCorpRecords/freezeledger, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/freezeledger: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/freezeledger
- Socket report: https://socket.dev/npm/package/@reneturcios/freezeledger
- Repository: https://github.com/CloudCorpRecords/freezeledger
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-freezeledger/reneturcios-freezeledger.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-freezeledger/reneturcios-freezeledger/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-freezeledger/reneturcios-freezeledger.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-freezeledger/reneturcios-freezeledger
