Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Data Workbench

NPM · DATA-WORKBENCH-MCP · 2 COMPONENTS

Pump.fun creator rewards, DexScreener pair search, crypto headlines, and USD candles.

0 this week 74 Trust /100

Last scanned (23 hours ago)

Scores higher than 49% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 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 109 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
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

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.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

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 →

Changelog

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.

  • 21 Nov 26 0
    • Source repository: unverified → fail ▼ security
  • 20 Nov 26 0
    • Provenance: fail → unverified ▼ security
  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 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.

  • 8 Nov 26 −1
    • Stability: pass → 0.87 functional
  • 27 Oct 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 npm/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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~440 tokens

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 →

Tool Tokens
coin_news ~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.

NameTypeReqDescription
daysinteger–Lookback window in days (default 7)
limitinteger–Max headlines (default 30)
tickerstringyesAsset ticker, e.g. BTC, SOL, THREE

No output schema declared.

No examples provided.

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%.

NameTypeReqDescription
breakdownboolean–Include the per-coin earnings breakdown (slower: walks every coin's timeline). Default false.
querystringyesCoin mint, wallet address, pump.fun username, github:user, or x:user

No output schema declared.

No examples provided.

ohlc ~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.

NameTypeReqDescription
coinstringyesCoinGecko id (bitcoin) or exchange ticker (BTC)
daysnumber–Window in days (default 30)

No output schema declared.

No examples provided.

search_pairs ~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>).

NameTypeReqDescription
limitinteger–Max pairs to return (default 10)
querystringyesTicker, name, CA/mint, pair address, or dexscreener.com URL

No output schema declared.

No examples provided.

Install

How do I install the Data Workbench MCP server?

Data Workbench runs locally as an npm package, launched with npx -y 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 · data-workbench-mcp

# add to Claude Code
claude mcp add nirholas-data-workbench-mcp -- npx -y data-workbench-mcp
Common questions

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 (data-workbench-mcp).

Is the Data Workbench MCP server safe to use?

Data Workbench scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against 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 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 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 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.

What did VerifyMCP test on the Data Workbench MCP server?

VerifyMCP ran 15 checks on Data Workbench, 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 Data Workbench: Security disclosure. 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.