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.

io.github.CloudCorpRecords/freezeledger

OCI · GHCR.IO/CLOUDCORPRECORDS/FREEZELEDGER · 2 COMPONENTS

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

41 Trust /100

Last scanned (16 hours ago)

Scores higher than 37% of OCI servers

Category Crypto and Web3

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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.

What we tested

Checks we ran (12)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (4)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  • Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 39

    First indexed and scored.

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 21 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/freezeledger@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

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

io.github.CloudCorpRecords/freezeledger runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/freezeledger:0.1.0 mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/cloudcorprecords/freezeledger

# add to Claude Code
claude mcp add cloudcorprecords-freezeledger -- docker run --rm -i ghcr.io/cloudcorprecords/freezeledger:0.1.0 mcp
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 container image (ghcr.io/cloudcorprecords/freezeledger).

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

io.github.CloudCorpRecords/freezeledger scores 41 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 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 12 checks on io.github.CloudCorpRecords/freezeledger, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/freezeledger: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.