# datasinking-mcp

MCP server for DataSinking — full-text Asian financial reports (China, Korea, Japan, Taiwan) as clean Markdown, for Claude, Cursor and other AI agents.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.2.12
- **Author:** DataSinking
- **License:** MIT
- **npm:** datasinking-mcp
- **PyPI:** datasinking
- **Endpoints:** streamable-http https://api.datasink.ing/mcp
- **Source:** https://github.com/heubme2020/datasinking
- **Endpoint health:** reachable (last checked 2026-09-23T11:29:46.558Z, 1 sample) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-23T16:52:57.432Z
- **Version scanned:** 0.2.12
- **CVEs:** none found by OSV at scan time

## Tools

6 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `list_exchanges` — List the exchanges DataSinking covers. Returns exchange codes (sse / szse / bj / ksc / koe / knx / jpx / twse / tpex) with the number of reports available per e
- `list_stocks` — List the stocks on one exchange, including the report count per company.
- `list_reports` — 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 tha
- `get_report` — Fetch one report's full text (metadata + Markdown body). The `source` field names the official disclosure platform; keep that attribution when you cite it. Expe
- `list_sections` — 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 ent
- `get_section` — Fetch only one section of a report by keyword — much cheaper than get_report, best for RAG.

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"datasinking\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"datasinking-mcp\"\n      ],\n      \"env\": {\n        \"DATASINK_API_KEY\": \"<YOUR_DATASINK_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `DATASINK_API_KEY` — Datasink API Key (required)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Moderate blast radius — runs locally and hosted; holds an api key.
- Floor 27, ceiling 27 (tier: moderate)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/datasinking-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/datasinking-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/datasinking-mcp
- HTML page: https://forgeregistry.com/registry/datasinking-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.