Skip to content

DataSinking MCP server

io.github.heubme2020/datasinkingheubme2020streamable-httpv0.2.17Scanned

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

8 tools: 1 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 1 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the DataSinking MCP server can do

The DataSinking MCP server is published by the GitHub account heubme2020. It has 8 tools. It can create or change data (1 tool: submit_feedback), but cannot delete data. 7 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 0.2.17.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 1Claude Code: ask
  • submit_feedbackRequest a full backfill of a stock whose reports look missing or broken, and return its current status.No findings

    Why it is in this group

    • The name "submit_feedback" says "submit": a word for a change.
    Description, as the server wrote it
    Request a full backfill of a stock whose reports look missing or broken, and return its current status. Idempotent — if the stock was already submitted recently (within the last 127 feedback records), it returns that existing status instead of queueing a duplicate; otherwise it queues a re-fetch from the IPO prospectus onward and returns status 'pending' plus the new id (poll get_feedback_status). Free keys: once per 3 seconds, 31 stocks per 7 days per key. Yearly keys: 3 per second, 8,191 stocks per 7 days per key.

    Annotations the server declares

    • title: Submit feedback
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 7Show 7 read-only tools
  • get_feedback_statusCheck the progress of a submitted feedback request.No findings

    Why it is in this group

    • The name "get_feedback_status" says "get": a word for reading.
    Description, as the server wrote it
    Check the progress of a submitted feedback request. status is one of pending / processing / done / failed.

    Annotations the server declares

    • title: Get feedback status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_reportFetch one report's full text (metadata + Markdown body).No findings

    Why it is in this group

    • The name "get_report" says "get": a word for reading.
    Description, as the server wrote it
    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. Content is annotated with block markers (`<!-- ds:block:N -->`) so you can cite a specific paragraph or table.

    Annotations the server declares

    • title: Get report
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_sectionFetch only one section of a report by keyword — much cheaper than get_report, best for RAG.No findings

    Why it is in this group

    • The name "get_section" says "get": a word for reading.
    Description, as the server wrote it
    Fetch only one section of a report by keyword — much cheaper than get_report, best for RAG. Content is annotated with block markers (`<!-- ds:block:N -->`) so you can cite a specific paragraph or table.

    Annotations the server declares

    • title: Get section
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_exchangesList the exchanges DataSinking covers.No findings

    Why it is in this group

    • The name "list_exchanges" says "list": a word for reading.
    Description, as the server wrote it
    List the exchanges DataSinking covers. Returns exchange codes (bj / br / by / jpx / koe / ksc / lk / lse / nasdaq / np / nyse / otc / pk / rs / sse / szse / tpex / tr / twse) with the number of reports available per exchange. Call this first to discover coverage. Sources: US = SEC EDGAR, A-shares = cninfo.com.cn, Japan = EDINET, Korea = DART, Taiwan = MOPS, Europe = filings.xbrl.org (ESEF), Nepal = NEPSE, Brazil = CVM, Belarus = ЕПФР, Sri Lanka = CSE, Pakistan = PSX, Serbia = SEC register, Turkey = KAP (kap.org.tr).

    Annotations the server declares

    • title: List exchanges
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_reportsList a company's reports — metadata only (id, title, period), no body text.No findings

    Why it is in this group

    • The name "list_reports" says "list": a word for reading.
    Description, as the server wrote it
    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. Look up by `symbol` (FMP-style, e.g. AAPL / 600519.SS / NABIL.NP) or by `exchange` + `stock_code` (from list_stocks) for markets whose codes aren't ticker-shaped (e.g. Brazil CNPJ, Sri Lanka 'AAA.N0000').

    Annotations the server declares

    • title: List reports
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_sectionsList every section of a report with its size, before you decide what to pull.No findings

    Why it is in this group

    • The name "list_sections" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List sections
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_stocksList the stocks on one exchange, including the report count per company.No findings

    Why it is in this group

    • The name "list_stocks" says "list": a word for reading.
    Description, as the server wrote it
    List the stocks on one exchange, including the report count per company.

    Annotations the server declares

    • title: List stocks
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:05 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.datasink.ing/mcp: tools/list returned 8 tools to an anonymous client, including submit_feedback (write)

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 0 to 1

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff
  2. Tools2 added, 1 changed.+2 added~1 changedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 1.View diff
    • Tools that change things, listed without credentials: 0 to 1

Install

Pinned to version 0.2.17. Values in angle brackets are yours to fill in.

claude mcp add --transport http datasinking https://api.datasink.ing/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http datasinking https://api.datasink.ing/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__datasinking__list_exchanges",
      "mcp__datasinking__list_stocks",
      "mcp__datasinking__list_reports",
      "mcp__datasinking__get_report",
      "mcp__datasinking__list_sections",
      "mcp__datasinking__get_section",
      "mcp__datasinking__get_feedback_status"
    ],
    "ask": [
      "mcp__datasinking__submit_feedback"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as datasinking. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.heubme2020/datasinking/verify?hash=f2afb8536b072b25fa1970801d7c1ffd6674f767d110848836b51e2d3688322d" | jq -e '.changed == false'

Pinned hash f2afb8536b07, from Nov 19, 2026, 20:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.heubme2020/datasinking/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.heubme2020/datasinking
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.heubme2020/datasinking.svg)](https://radar.anlyon.com/servers/io.github.heubme2020/datasinking)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:35 UTC.

DataSinking MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the DataSinking MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the DataSinking MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the DataSinking MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the DataSinking MCP server have?

8 tools: 1 write, 7 read. submit_feedback, list_exchanges, list_stocks, list_reports, get_report, list_sections, get_section and get_feedback_status.

Does the DataSinking MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the DataSinking MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the DataSinking MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.