# so.blackforge/mcp (npm · @blackforge-so/mcp)

Crypto market data: order book depth, liquidity lifetimes and taker flow on 9 spot venues

- Trust score: 78/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `@blackforge-so/mcp`: 78/100 (this document), [markdown](https://verifymcp.io/servers/so-blackforge-mcp/blackforge-so-mcp.md), [page](https://verifymcp.io/servers/so-blackforge-mcp/blackforge-so-mcp)

## Channel facts

- Registry: `npm`
- Package: `@blackforge-so/mcp`
- Version: `0.2.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-09-20.

- **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 96 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 14 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 994 tokens (~165/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 5 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.
  - Supports UI / widget rendering.

## Install

### How do I install the so.blackforge/mcp server?

so.blackforge/mcp runs locally as an npm package, launched with npx -y @blackforge-so/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 so-blackforge-mcp -- npx -y @blackforge-so/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "so-blackforge-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@blackforge-so/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "so-blackforge-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@blackforge-so/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add so-blackforge-mcp -- npx -y @blackforge-so/mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add so-blackforge-mcp --command npx --arg -y --arg @blackforge-so/mcp
```

### Hermes

```yaml
mcp_servers:
  so-blackforge-mcp:
    command: "npx"
    args: ["-y", "@blackforge-so/mcp"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add so-blackforge-mcp -t stdio -c npx -a -y @blackforge-so/mcp
```

### Other

```json
{
  "mcpServers": {
    "so-blackforge-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@blackforge-so/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-09-20 (score 78, +1)

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

### 2026-09-17 (score 77, +1)

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

### 2026-09-15 (score 76, +1)

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

### 2026-09-14 (score 75, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-07 (score 71, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-06 (score 56)

First indexed and scored.

## MCP tools (5)

### `blackforge_catalog` (~153 tokens)

BlackForge catalog

List every venue BlackForge covers (9 spot exchanges) and every column it measures (one wide row per (exchange, symbol) per 5-minute window: order-book depth and shape, resting-liquidity lifetimes, trade-explained vs book-implied volume, spreads, and market-wide context). `metricCount` is the exact number of columns available now. Each metric carries a precise measurement definition, unit, family, and the minimum plan that includes it; the `qualityFlags` metric also carries the `bits` table that decodes the per-row quality mask. This route needs no API key. CALL THIS FIRST to learn the exact `exchange` and `metric` identifiers the other tools accept.

### `blackforge_symbols` (~119 tokens)

BlackForge symbols

List the trading pairs (symbols) a given venue trades, as an array of symbol strings. Use these values as the `symbol` argument to blackforge_latest and blackforge_series. Valid `exchange` values come from blackforge_catalog (e.g. binance, bybit, coinbase, kraken, okx). A venue outside the caller's plan returns HTTP 403 with the plan and an upgrade URL.

Input parameters:

- `exchange` (string, required): Venue identifier from blackforge_catalog, e.g. binance, okx, coinbase.

### `blackforge_latest` (~271 tokens)

BlackForge latest bucket

Return the latest completed 5-minute window for one (exchange, symbol): a `values` object mapping each column key to its measured number (or null when not observed), plus the window timestamp `ts` in epoch milliseconds. Omit `columns` to get every column your plan includes; pass a subset of column keys (from blackforge_catalog) to narrow the payload. Columns your plan does not cover are dropped and reported in `columnsOmitted` so you can see why a key is absent. WHEN PRESENT, a `quality` object reports the row's measurement quality — `flags` names what went wrong during the window and `contaminates` lists which figures it flags, with a plain-English `qualityNote` beside it. Read it before trusting an unusual value. A `quality.raw` of 32768 means the row predates the quality rail and was never assessed — that is unknown, not bad. When the key is absent, the row carries no quality assessment at all.

Input parameters:

- `columns` (array): Optional subset of column keys from blackforge_catalog. Omit for all plan-included columns.
- `exchange` (string, required): Venue identifier, e.g. binance.
- `symbol` (string, required): Trading pair from blackforge_symbols, e.g. BTCUSDT.

### `blackforge_series` (~346 tokens)

BlackForge time series

Return a time series for one column of one (exchange, symbol): `points` is an ascending array of { ts, value } where `ts` is epoch milliseconds and `value` is the measured number (or null). `from`/`to` are ISO-8601 datetimes; `interval` is one of 5m, 1h, 1d (higher intervals may be plan-gated). The server caps a response at 50,000 points. If the requested `metric` is above your plan, `points` comes back empty and the column is listed in `columnsOmitted` — that is why it is empty. WHEN ANY BUCKET IS FLAGGED, a `qualitySummary` object reports how many of the buckets carry a quality flag and which flags they are (`{ flaggedBuckets, of, flags }`); per-bucket quality is deliberately not repeated on every point. No `qualitySummary` means no bucket in the range was flagged.

Input parameters:

- `exchange` (string, required): Venue identifier, e.g. binance.
- `from` (string, required): Start datetime, ISO-8601, e.g. 2026-07-01T00:00:00Z.
- `interval` (string, required): Bucket size: 5m, 1h, or 1d.
- `metric` (string, required): Column key from blackforge_catalog, e.g. spreadMean.
- `symbol` (string, required): Trading pair, e.g. BTCUSDT.
- `to` (string, required): End datetime, ISO-8601, e.g. 2026-07-02T00:00:00Z.

### `blackforge_usage` (~70 tokens)

BlackForge usage

Report the calling key's recent usage: `days` is a per-day breakdown of request counts and the last request time, and `rowsRemaining` is the monthly row quota still available (omitted for usage-based plans that have no monthly ceiling). Use this to check headroom before a large pull.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/so-blackforge-mcp/blackforge-so-mcp#diagnostics

## Score history

- 2026-09-20: 78
- 2026-09-19: 77
- 2026-09-18: 77
- 2026-09-17: 77
- 2026-09-16: 76
- 2026-09-15: 76
- 2026-09-14: 75
- 2026-09-13: 71
- 2026-09-12: 71
- 2026-09-11: 71
- 2026-09-10: 71
- 2026-09-09: 71
- 2026-09-08: 71
- 2026-09-07: 71
- 2026-09-06: 56

## Common questions

### What is the so.blackforge/mcp server?

so.blackforge/mcp is listed in the public MCP registry as so.blackforge/mcp. Crypto market data: order book depth, liquidity lifetimes and taker flow on 9 spot venues. This page covers its npm package (@blackforge-so/mcp).

### Is the so.blackforge/mcp server safe to use?

so.blackforge/mcp scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 so.blackforge/mcp server expose?

so.blackforge/mcp exposes 5 tools: blackforge_catalog, blackforge_symbols, blackforge_latest, blackforge_series, blackforge_usage. Their descriptions and schemas cost roughly 959 tokens of context every time the server is loaded.

### Is the so.blackforge/mcp server still maintained?

so.blackforge/mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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 so.blackforge/mcp server under?

so.blackforge/mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@blackforge-so/mcp
- Socket report: https://socket.dev/npm/package/@blackforge-so/mcp
- Repository: https://github.com/blackforge-so/mcp
- Website: https://blackforge.so/
- Changelog RSS feed: https://verifymcp.io/servers/so-blackforge-mcp/blackforge-so-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/so-blackforge-mcp/blackforge-so-mcp.json
- HTML version of this page: https://verifymcp.io/servers/so-blackforge-mcp/blackforge-so-mcp