DataSinking
Registry code: 29f7c981c5e50b9e
DataSinking serves full-text financial reports (annual / semi-annual / quarterly) from the US, China, Japan, Korea and Taiwan as clean Markdown, ready for LLM reading and RAG. Use FMP-style symbols: AAPL (Apple), 600519.SS (Kweichow Moutai), 7203.T (Toyota), 005930.KS (Samsung Electronics), 2330.TW (TSMC). To save tokens, prefer get_section to pull one chapter (e.g. MD&A) instead of get_report for the whole document.
- endpoint
- https://api.datasink.ing/mcp
- protocol
- streamable-http ·2024-11-05
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is DataSinking live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is DataSinking free to use?
- Partly — some of its tools are open, others need a key or payment.
- What tools does DataSinking have?
- 6 tools: list_stocks, list_sections, get_section, list_exchanges, list_reports, get_report.
- Is DataSinking safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 6 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_exchanges open 1h ago
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 / 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, UK = FCA NSM, Nepal = NEPSE, Brazil = CVM, Belarus = ЕПФР, Sri Lanka = CSE, Pakistan = PSX, Serbia = SEC register.
{ "type": "object", "properties": {} }arguments 4 lineslist_reports auth-required 1h ago
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').
{ "type": "object", "properties": { "size": { "type": "integer", "default": 10, "description": "Number of reports to return (default 10)." }, "symbol": { "type": "string", "description": "FMP-style symbol, e.g. AAPL / 600519.SS / 7203.T / 005930.KS / 2330.TW / NABIL.NP" }, "doc_type": { "enum": [ "annual", "semiannual", "q1", "q3" ], "type": "string", "default": "annual", "description": "Report type to filter on: annual / semiannual / q1 / q3. Defaults to annual. Pass semiannual for half-year reports, q1 / q3 for the quarterly reports." }, "exchange": { "type": "string", "description": "Exchange code (from list_exchanges). Use with stock_code when the code isn't ticker-shaped." }, "stock_code": { "type": "string", "description": "Exact stock_code from list_stocks. Use with exchange." } } }arguments 33 linesget_report auth-required 1h ago
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.
{ "type": "object", "required": [ "document_id" ], "properties": { "document_id": { "type": "integer", "description": "Report id, from list_reports items[].id" } } }arguments 12 lineslist_stocks unknown never probed
List the stocks on one exchange, including the report count per company.
{ "type": "object", "required": [ "exchange" ], "properties": { "limit": { "type": "integer", "default": 20, "description": "Return only the first N companies (default 20) to keep the response short." }, "exchange": { "type": "string", "description": "Exchange code, e.g. bj / br / by / jpx / koe / ksc / lk / lse / nasdaq / np / nyse / otc / pk / rs / sse / szse / tpex / twse" } } }arguments 17 lineslist_sections unknown never probed
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.
{ "type": "object", "required": [ "document_id" ], "properties": { "document_id": { "type": "integer", "description": "Report id, from list_reports items[].id" } } }arguments 12 linesget_section unknown never probed
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.
{ "type": "object", "required": [ "document_id", "section" ], "properties": { "section": { "type": "string", "description": "Heading keyword. Matches the report's own headings, and also understands cross-market concepts — MD&A / financial statements / notes / audit report / risk / governance (or their Chinese/Japanese/Korean equivalents) resolve to the right section in any market. Otherwise pass a heading in the report's language (A-share: 管理层讨论与分析 / 财务报告; English filings: \"MD&A\" / \"financial statements\" / \"notes\"). If nothing matches, the API returns 404 with the real headings — retry with one of those, or call list_sections first." }, "document_id": { "type": "integer", "description": "Report id, from list_reports items[].id" } } }arguments 17 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id29f7c981c5e50b9e.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/29f7c981c5e50b9e/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/29f7c981c5e50b9e?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.