io.github.CloudCorpRecords/liqscope
OCI · GHCR.IO/CLOUDCORPRECORDS/LIQSCOPE · 2 COMPONENTS
Crypto liquidation data: liquidation maps, totals, funding, open interest and fear and greed.
Available components
Last scanned (13 hours ago)
Scores higher than 45% of OCI servers
Category Crypto and Web3
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
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 588 tokens (~147/item across 4 items; 4 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 Management20
- Stability observed for 6 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
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 →
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 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 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.
- 16 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.
- 15 Nov 26 41
First indexed and scored.
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/liqscope@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 →
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 →
derivatives Funding, open interest, long/short ~146
Funding rates, open interest and the long/short ratio of perpetual futures, for one coin or for the ten largest coins by open interest. Use it for questions like "what is the funding rate of ETH", "is open interest growing", "are traders long or short". Returns current values: the Binance funding rate and the average across exchanges per 8 hours, open interest in USD with its change over 24 hours and over the last hour, the share of Binance accounts that are long, the long/short ratio and the share of top traders' positions in longs.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | – | Coin ticker such as BTC, ETH or SOL; omit it for the ten largest coins |
No output schema declared.
No examples provided.
fear_greed Fear and Greed Index ~88
The crypto Fear and Greed Index: the mood of the market right now on a scale from 0 (extreme fear) to 100 (extreme greed), for the whole market or for BTC, ETH or SOL, with the values a day, a week and a month ago.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | – | BTC, ETH or SOL; omit it for the whole crypto market |
No output schema declared.
No examples provided.
liquidation_map Liquidation map ~218
Where forced liquidations stand around the current price of one market: USD amounts of long liquidations below the price and of short liquidations above it, on Hyperliquid (crypto, stocks, indices and commodities) and across large exchanges (Binance, OKX, Bybit, Hyperliquid, Gate). Use it for questions like "where are the liquidation levels for BTC", "where do longs get liquidated", "what is the nearest liquidation cluster". Returns one current snapshot: the price, totals within a few percent of the price, the largest levels on each side with their distance from the price, and the URL of the live map. An unknown market returns the list of valid ones.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | Market ticker: BTC, ETH, SOL, HYPE, XRP, DOGE … or a Hyperliquid market such as XAU (gold), CL (crude oil), SP500, NVDA, TSLA. Names such as Bitcoin or Gold and pair names such as BTCUSDT are accepte… |
No output schema declared.
No examples provided.
liquidations Liquidations ~136
How much was liquidated: the last 24 hours and the last hour, longs against shorts, for the whole crypto market or for one coin. Use it for questions like "how much was liquidated today", "were longs or shorts liquidated", "which exchange had the most liquidations". Returns the totals, the split by coin (whole market) or by exchange (one coin), the largest liquidations of the last hour, and the URL of the page.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | – | One of BTC, ETH, SOL, XRP, DOGE, HYPE, BNB; omit it for the whole crypto market |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/liqscope MCP server?
io.github.CloudCorpRecords/liqscope runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/liqscope: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/liqscope
claude mcp add cloudcorprecords-liqscope -- docker run --rm -i ghcr.io/cloudcorprecords/liqscope:0.1.0 mcp
What is the io.github.CloudCorpRecords/liqscope MCP server?
io.github.CloudCorpRecords/liqscope is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/liqscope. Crypto liquidation data: liquidation maps, totals, funding, open interest and fear and greed. This page covers its container image (ghcr.io/cloudcorprecords/liqscope).
Is the io.github.CloudCorpRecords/liqscope MCP server safe to use?
io.github.CloudCorpRecords/liqscope scores 44 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/liqscope MCP server expose?
io.github.CloudCorpRecords/liqscope exposes 4 tools: liquidation_map, liquidations, derivatives, fear_greed. Their descriptions and schemas cost roughly 588 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/liqscope MCP server still maintained?
io.github.CloudCorpRecords/liqscope 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/liqscope MCP server under?
io.github.CloudCorpRecords/liqscope 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/liqscope MCP server?
VerifyMCP ran 12 checks on io.github.CloudCorpRecords/liqscope, 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/liqscope: 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.