Full-text Asian financial reports (China, Korea, Japan) as clean Markdown — API
Full-text Asian financial reports (China, Korea, Japan) as clean Markdown — API + MCP server
active Production-safe Score 90/100 http auth required
At a glance
| Endpoint | https://api.datasink.ing/mcp |
|---|---|
| Source | https://github.com/heubme2020/datasinking |
| Transport | http |
| Tools | 8 |
| Auth | bearer (bearer) |
| First seen | 2026-09-04 03:17:52 |
| Last checked | 2026-11-17 21:50:05 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 351 / 731 ms |
| Last successful check | 2026-11-17 21:50:05 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (8)
list_exchanges— List the exchanges DataSinking covers. Returns exchange codes (bj / br / by / jpx / koe / ksc / lk / lse / nasdaq / np / nyse / otc / pk / rlist_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 disclosurget_report— Fetch one report's full text (metadata + Markdown body). The `source` field names the official disclosure platform; keep that attribution whlist_sections— List every section of a report with its size, before you decide what to pull. Returns `sections` (titles, in order) plus `section_details` —get_section— Fetch only one section of a report by keyword — much cheaper than get_report, best for RAG. Content is annotated with block markers (`<!-- dsubmit_feedback— Request a full backfill of a stock whose reports look missing or broken, and return its current status. Idempotent — if the stock was alreadget_feedback_status— Check the progress of a submitted feedback request. status is one of pending / processing / done / failed.
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:50:05 | ✓ | ✓ | 440 ms | 90 | active |
| 2026-11-17 21:35:04 | ✓ | ✓ | 798 ms | 90 | active |
| 2026-11-17 21:20:03 | ✓ | ✓ | 1279 ms | 87 | active |
| 2026-11-17 21:05:01 | ✓ | ✓ | 377 ms | 90 | active |
| 2026-11-17 20:49:59 | ✓ | ✓ | 420 ms | 90 | active |
| 2026-11-17 20:34:59 | ✓ | ✓ | 481 ms | 90 | active |
| 2026-11-17 20:19:59 | ✓ | ✓ | 492 ms | 90 | active |
| 2026-11-17 20:04:58 | ✓ | ✓ | 360 ms | 90 | active |
| 2026-11-17 19:49:57 | ✓ | ✓ | 526 ms | 90 | active |
| 2026-11-17 19:34:56 | ✓ | ✓ | 551 ms | 90 | active |
| 2026-11-17 19:19:56 | ✓ | ✓ | 573 ms | 90 | active |
| 2026-11-17 19:04:55 | ✓ | ✓ | 593 ms | 90 | active |
| 2026-11-17 18:49:54 | ✓ | ✓ | 472 ms | 90 | active |
| 2026-11-17 18:34:53 | ✓ | ✓ | 451 ms | 90 | active |
| 2026-11-17 18:19:53 | ✓ | ✓ | 654 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://api.datasink.ing/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/api-datasink-ing-mcp # JSON