# DataSinking (npm · datasinking-mcp)

Full-text Asian financial reports (China, Korea, Japan, Taiwan) as clean Markdown for RAG agents.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `api.datasink.ing`: 28/100, [markdown](https://verifymcp.io/servers/heubme2020-datasinking/api.md), [page](https://verifymcp.io/servers/heubme2020-datasinking/api)
- npm · `datasinking-mcp`: 72/100 (this document), [markdown](https://verifymcp.io/servers/heubme2020-datasinking/datasinking-mcp.md), [page](https://verifymcp.io/servers/heubme2020-datasinking/datasinking-mcp)
- pypi · `datasinking`: 40/100, [markdown](https://verifymcp.io/servers/heubme2020-datasinking/datasinking.md), [page](https://verifymcp.io/servers/heubme2020-datasinking/datasinking)

## Channel facts

- Registry: `npm`
- Package: `datasinking-mcp`
- Version: `0.2.10`
- 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-25.

- **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 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/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 2 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 767 tokens (~127/item across 6 items; 6 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 DataSinking MCP server?

DataSinking runs locally as an npm package, launched with npx -y datasinking-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 heubme2020-datasinking -- npx -y datasinking-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "heubme2020-datasinking": {
      "command": "npx",
      "args": [
        "-y",
        "datasinking-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "heubme2020-datasinking": {
      "command": "npx",
      "args": [
        "-y",
        "datasinking-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add heubme2020-datasinking -- npx -y datasinking-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add heubme2020-datasinking --command npx --arg -y --arg datasinking-mcp
```

### Hermes

```yaml
mcp_servers:
  heubme2020-datasinking:
    command: "npx"
    args: ["-y", "datasinking-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "heubme2020-datasinking": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "datasinking-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add heubme2020-datasinking -t stdio -c npx -a -y datasinking-mcp
```

### Other

```json
{
  "mcpServers": {
    "heubme2020-datasinking": {
      "command": "npx",
      "args": [
        "-y",
        "datasinking-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-25 (score 72, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-22 (score 72)

First indexed and scored.

## MCP tools (6)

### `list_exchanges` (~88 tokens)

List the exchanges DataSinking covers. Returns exchange codes (sse / szse / bj / ksc / koe / knx / jpx / twse / tpex) with the number of reports available per exchange. Call this first to discover coverage. Sources: A-shares = cninfo.com.cn, Korea = DART, Japan = EDINET, Taiwan = MOPS.

### `list_stocks` (~83 tokens)

List the stocks on one exchange, including the report count per company.

Input parameters:

- `exchange` (string, required): Exchange code, e.g. sse / szse / bj / ksc / koe / knx / jpx / twse / tpex
- `limit` (integer): Return only the first N companies (default 20) to keep the response short.

### `list_reports` (~118 tokens)

List a company's reports — metadata only (id, title, period), no body text. Each item carries a `source` field naming the official disclosure platform; keep that attribution when you cite it.

Input parameters:

- `doc_type` (string): Report type to filter on. Defaults to annual.
- `size` (integer): Number of reports to return (default 10).
- `symbol` (string, required): FMP-style symbol, e.g. 600519.SS / 005930.KS / 7203.T / 2330.TW

### `get_report` (~71 tokens)

Fetch one report's full text (metadata + Markdown body). The `source` field names the official disclosure platform; keep that attribution when you cite it. Expensive in tokens — prefer get_section when you only need one chapter.

Input parameters:

- `document_id` (integer, required): Report id, from list_reports items[].id

### `list_sections` (~141 tokens)

List every section of a report with its size, before you decide what to pull. Returns `sections` (titles, in order) plus `section_details` — same order, one entry per section with `title`, `has_tables`, `chars` and `estimated_tokens`. Use `estimated_tokens` to avoid pulling a chapter that would blow your context, and `has_tables` to know whether the chapter needs special handling (tables are the part RAG pipelines usually get wrong). Then call get_section with a heading keyword — the headings are in the report's own language.

Input parameters:

- `document_id` (integer, required): Report id, from list_reports items[].id

### `get_section` (~154 tokens)

Fetch only one section of a report by keyword — much cheaper than get_report, best for RAG.

Input parameters:

- `document_id` (integer, required): Report id, from list_reports items[].id
- `section` (string, required): Heading keyword, matched as a substring against the report's OWN headings, so pass it in the report's language. A-share reports have Chinese headings (e.g. 第三节管理层讨论与分析) — use 管理层讨论与分析 / 财务报告 there. F…

## Diagnostics

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

## Score history

- 2026-09-25: 72
- 2026-09-24: 72
- 2026-09-23: 72
- 2026-09-22: 72

## Common questions

### What is the DataSinking MCP server?

DataSinking is an MCP server listed in the public MCP registry as io.github.heubme2020/datasinking. Full-text Asian financial reports (China, Korea, Japan, Taiwan) as clean Markdown for RAG agents. This page covers its npm package (datasinking-mcp).

### Is the DataSinking MCP server safe to use?

DataSinking scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 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 DataSinking MCP server expose?

DataSinking exposes 6 tools: list_exchanges, list_stocks, list_reports, get_report, list_sections, get_section. Their descriptions and schemas cost roughly 655 tokens of context every time the server is loaded.

### Is the DataSinking MCP server still maintained?

DataSinking is still listed as active in the MCP registry. We last reached this channel on 25 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 DataSinking MCP server under?

DataSinking 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/datasinking-mcp
- Socket report: https://socket.dev/npm/package/datasinking-mcp
- Repository: https://github.com/heubme2020/datasinking
- Website: https://datasink.ing/
- Changelog RSS feed: https://verifymcp.io/servers/heubme2020-datasinking/datasinking-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/heubme2020-datasinking/datasinking-mcp.json
- HTML version of this page: https://verifymcp.io/servers/heubme2020-datasinking/datasinking-mcp