Data Workbench
NPM · @THREE-WS/DATA-WORKBENCH-MCP · 2 COMPONENTS · SCANNED SEP 23
Pump.fun creator rewards, DexScreener pair search, crypto headlines, and USD candles.
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 & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 64 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 440 tokens (~110/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
How do I install the Data Workbench MCP server?
Data Workbench runs locally as an npm package, launched with npx -y @three-ws/data-workbench-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 · @three-ws/data-workbench-mcp
claude mcp add nirholas-data-workbench-mcp -- npx -y @three-ws/data-workbench-mcp
{
"mcpServers": {
"nirholas-data-workbench-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/data-workbench-mcp"
]
}
}
} {
"servers": {
"nirholas-data-workbench-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/data-workbench-mcp"
]
}
}
} codex mcp add nirholas-data-workbench-mcp -- npx -y @three-ws/data-workbench-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nirholas-data-workbench-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@three-ws/data-workbench-mcp"
],
"enabled": true
}
}
} openclaw mcp add nirholas-data-workbench-mcp --command npx --arg -y --arg @three-ws/data-workbench-mcp
mcp_servers:
nirholas-data-workbench-mcp:
command: "npx"
args: ["-y", "@three-ws/data-workbench-mcp"] {
"McpServers": {
"nirholas-data-workbench-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@three-ws/data-workbench-mcp"
]
}
}
} assistant mcp add nirholas-data-workbench-mcp -t stdio -c npx -a -y @three-ws/data-workbench-mcp
{
"mcpServers": {
"nirholas-data-workbench-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/data-workbench-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.
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.80 functional
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 23 Sept 2026 · Analysed npm/@three-ws/data-workbench-mcp@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 | 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 →
coin_news Coin headlines (live + archive) ~108
Headlines for a ticker over the last N days, merged from the three.ws live feed (192 publishers) and its 660k-article historical archive. Each item carries source, timestamp, sentiment, and link. Archive queries have a free per-IP daily quota.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Lookback window in days (default 7) |
| limit | integer | – | Max headlines (default 30) |
| ticker | string | yes | Asset ticker, e.g. BTC, SOL, THREE |
No output schema declared.
No examples provided.
creator_rewards Pump.fun creator rewards ~114
Lifetime and per-day pump.fun creator-fee earnings for a coin mint, wallet address, pump.fun username, or linked social identity (github:user, x:user). Per-coin figures are summed from distribution timelines and reconcile with the wallet's lifetime claimed total to ~0.001%.
| Name | Type | Req | Description |
|---|---|---|---|
| breakdown | boolean | – | Include the per-coin earnings breakdown (slower: walks every coin's timeline). Default false. |
| query | string | yes | Coin mint, wallet address, pump.fun username, github:user, or x:user |
No output schema declared.
No examples provided.
ohlc USD candles ~97
OHLC candles in USD for a coin over 1/7/14/30/90 days. Tries CoinGecko by coin id, then Coinbase Exchange and Kraken public data by ticker. Returns [isoTime, open, high, low, close] ascending.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | CoinGecko id (bitcoin) or exchange ticker (BTC) |
| days | number | – | Window in days (default 30) |
No output schema declared.
No examples provided.
search_pairs DexScreener pair search ~121
Every DexScreener trading pair matching a query: ticker, token name, contract/mint address, pair address, or a dexscreener.com URL. Returns chain, dex, price, 24h change, liquidity, volume, and the pair address (chartable at https://dexscreener.com/<chainId>/<pairAddress>).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max pairs to return (default 10) |
| query | string | yes | Ticker, name, CA/mint, pair address, or dexscreener.com URL |
No output schema declared.
No examples provided.
What is the Data Workbench MCP server?
Data Workbench is an MCP server listed in the public MCP registry as io.github.nirholas/data-workbench-mcp. Pump.fun creator rewards, DexScreener pair search, crypto headlines, and USD candles. This page covers its npm package (@three-ws/data-workbench-mcp).
Is the Data Workbench MCP server safe to use?
Data Workbench scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 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 Data Workbench MCP server expose?
Data Workbench exposes 4 tools: creator_rewards, search_pairs, coin_news, ohlc. Their descriptions and schemas cost roughly 440 tokens of context every time the server is loaded.
Is the Data Workbench MCP server still maintained?
Data Workbench is still listed as active in the MCP registry. We last reached this channel on 23 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 Data Workbench MCP server under?
Data Workbench declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.