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

Crypto liquidation data: liquidation maps, totals, funding, open interest and fear and greed.

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/liqscope`
- 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.
  - 30 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 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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/liqscope MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-liqscope": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/liqscope",
        "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-16 (score 71, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-15 (score 56)

First indexed and scored.

## MCP tools (4)

### `liquidation_map` (~218 tokens)

Liquidation map

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.

Input parameters:

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

### `liquidations` (~136 tokens)

Liquidations

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.

Input parameters:

- `coin` (string): One of BTC, ETH, SOL, XRP, DOGE, HYPE, BNB; omit it for the whole crypto market

### `derivatives` (~146 tokens)

Funding, open interest, long/short

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.

Input parameters:

- `coin` (string): Coin ticker such as BTC, ETH or SOL; omit it for the ten largest coins

### `fear_greed` (~88 tokens)

Fear and Greed Index

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.

Input parameters:

- `coin` (string): BTC, ETH or SOL; omit it for the whole crypto market

## Diagnostics

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

## Score history

- 2026-11-21: 71
- 2026-11-20: 71
- 2026-11-19: 71
- 2026-11-18: 71
- 2026-11-17: 71
- 2026-11-16: 71
- 2026-11-15: 56

## Common questions

### 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 npm package (@reneturcios/liqscope).

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

io.github.CloudCorpRecords/liqscope scores 71 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/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 15 checks on io.github.CloudCorpRecords/liqscope, 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/liqscope: 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/liqscope
- Socket report: https://socket.dev/npm/package/@reneturcios/liqscope
- Repository: https://github.com/CloudCorpRecords/liqscope
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-liqscope/reneturcios-liqscope.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-liqscope/reneturcios-liqscope/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-liqscope/reneturcios-liqscope.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-liqscope/reneturcios-liqscope
