so.blackforge/mcp
NPM · @BLACKFORGE-SO/MCP · SCANNED SEP 20
Crypto market data: order book depth, liquidity lifetimes and taker flow on 9 spot venues
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
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 14 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 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 5 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
- Supports UI / widget rendering.Pass
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.
npm · @blackforge-so/mcp
claude mcp add so-blackforge-mcp -- npx -y @blackforge-so/mcp
{
"mcpServers": {
"so-blackforge-mcp": {
"command": "npx",
"args": [
"-y",
"@blackforge-so/mcp"
]
}
}
} {
"servers": {
"so-blackforge-mcp": {
"command": "npx",
"args": [
"-y",
"@blackforge-so/mcp"
]
}
}
} codex mcp add so-blackforge-mcp -- npx -y @blackforge-so/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"so-blackforge-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@blackforge-so/mcp"
],
"enabled": true
}
}
} openclaw mcp add so-blackforge-mcp --command npx --arg -y --arg @blackforge-so/mcp
mcp_servers:
so-blackforge-mcp:
command: "npx"
args: ["-y", "@blackforge-so/mcp"] {
"McpServers": {
"so-blackforge-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@blackforge-so/mcp"
]
}
}
} assistant mcp add so-blackforge-mcp -t stdio -c npx -a -y @blackforge-so/mcp
{
"mcpServers": {
"so-blackforge-mcp": {
"command": "npx",
"args": [
"-y",
"@blackforge-so/mcp"
]
}
}
} 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 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 14 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 7 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 6 Sept 26 56
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 20 Sept 2026 · Analysed npm/@blackforge-so/mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
blackforge_catalog BlackForge catalog ~153
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
blackforge_latest BlackForge latest bucket ~271
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.
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | – | Optional subset of column keys from blackforge_catalog. Omit for all plan-included columns. |
| exchange | string | yes | Venue identifier, e.g. binance. |
| symbol | string | yes | Trading pair from blackforge_symbols, e.g. BTCUSDT. |
No output schema declared.
No examples provided.
blackforge_series BlackForge time series ~346
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.
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | Venue identifier, e.g. binance. |
| from | string | yes | Start datetime, ISO-8601, e.g. 2026-07-01T00:00:00Z. |
| interval | string | yes | Bucket size: 5m, 1h, or 1d. |
| metric | string | yes | Column key from blackforge_catalog, e.g. spreadMean. |
| symbol | string | yes | Trading pair, e.g. BTCUSDT. |
| to | string | yes | End datetime, ISO-8601, e.g. 2026-07-02T00:00:00Z. |
No output schema declared.
No examples provided.
blackforge_symbols BlackForge symbols ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | Venue identifier from blackforge_catalog, e.g. binance, okx, coinbase. |
No output schema declared.
No examples provided.
blackforge_usage BlackForge usage ~70
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.