洋葱财报OnionData-MCP
REMOTE · API.ONIONREPORT.COM
洋葱财报OnionData-MCP 提供 A 股上市公司多口径财报数据,覆盖利润表、资产负债表、现金流量表,支持单季同比/环比、逐季度 TTM、年度与最新报告期近 10 期查询。
Available components
Last scanned (18 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1612 tokens (~268/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 0
- First check of Authorization: partial security
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 2026.11.16 → 2026.11.19 functional
- 19 Nov 26 0
- Tool “company_records” rewrote its description, which is the text the model reads security
- Tool “get_usage” rewrote its description, which is the text the model reads security
- 18 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://api.onionreport.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.onionreport.com | CN=TrustAsia DV TLS RSA CA 2024,O=TrustAsia Technologies\, Inc.,C=CN | 2 Nov 2026 | 31 Jan 2027 | RSA 2048 | SHA256-RSA | 41f2051a5187785da0f3c0ec1c3450d1f0e86374 |
| SANs: api.onionreport.com | ||||||
| CN=TrustAsia DV TLS RSA CA 2024,O=TrustAsia Technologies\, Inc.,C=CN (CA) | CN=TrustAsia TLS RSA Root CA,O=TrustAsia Technologies\, Inc.,C=CN | 15 May 2024 | 15 May 2034 | RSA 4096 | SHA384-RSA | 1c9e6b412deb0a85461de03dbe30984d0573888b |
| CN=TrustAsia TLS RSA Root CA,O=TrustAsia Technologies\, Inc.,C=CN (CA) | CN=Certum Trusted Network CA,OU=Certum Certification Authority,O=Unizeto Technologies S.A.,C=PL | 7 Oct 2025 | 14 Jan 2029 | RSA 4096 | SHA384-RSA | b2dc4c34932d709cd4bf0b099401695c |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.onionreport.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| onionreport.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", resource_metadata="https://api.onionreport.com/.well-known/oauth-protected-resource/mcp"
Bearer error="invalid_token", resource_metadata="https://api.onionreport.com/.well-known/oauth-protected-resource/mcp" | Header | Value |
|---|---|
| strict-transport-security | max-age=86400 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer-when-downgrade |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Protected resource metadata
| Document | https://api.onionreport.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://api.onionreport.com/mcp |
| Authorisation server | https://oauth.onionreport.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.onionreport.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.onionreport.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
company_records 财务取数(单公司多期 / 多公司单期) ~683
读取 A 股上市公司财报明细(China A-share financial statements):唯一取数入口,覆盖利润表 income、资产负债表 balance、现金流量表 cashflow、业绩预告 predict。 支持单季度同比、单季度环比、逐季度 TTM、年度与最新报告期五种口径,由 repoterm 指定(各取值与释义见 inputSchema)。 scode 传 1 个为单公司多期(periods 1–10,默认 1);传 2–10 个为多公司单期横切,省略 report_date 时取所选公司该口径的最近报告期。多公司不支持 periods,periods 与 report_date 互斥(同时传返回 dimension_conflict);业绩预告 predict 仅支持 format=long。 结果上界按报表计:long 每张 250 行 / wide 每张 10 行,reponame 最多 4 张(逗号分隔),超出返回 result_too_large,不截断。 数值为原始值(元),增幅以百分点表示(12.3 即 12.3%)。notice_date_to 为时点快照(重述会移动公告日),notice_date_from 为增量(含重述)。 按实际返回数据量加权计积分,空结果不计;单公司与多公司横切均不要求 VIP。
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | long 一行一指标;wide 一行一(公司, 报告期) |
| notice_date_from | string | – | 公告日下界(含)YYYY-MM-DD;响应 meta.notice_date_max 可作下次水位线 |
| notice_date_to | string | – | 公告日上界(含)YYYY-MM-DD,用于时点快照 |
| periods | integer | – | 报告期数 1–10,默认 1(最近一期),仅单公司可用(多公司传会报 dimension_conflict) |
| repoitem_key | array | – | 指标 key 列表;省略=该报表全部指标 |
| reponame | string | yes | 报表名:income 利润表(income statement)/ balance 资产负债表(balance sheet)/ cashflow 现金流量表(cash flow statement)/ predict 业绩预告;多张报表用逗号分隔(最多 4 个),如 income,balance |
| report_date | string | – | 报告期 YYYY-MM-DD;与 periods 互斥,多公司不传则取最近报告期 |
| repoterm | string | yes | 单一口径:new 最新报告期 latest / quarter_t 单季度同比 YoY / quarter_h 单季度环比 QoQ / ttm 逐季度 TTM / year 年度 annual |
| repotype | string | – | 指标类别:basic 基础指标 / operation 运营指标;省略=该报表全部指标 |
| scode | array | yes | A 股 6 位代码列表(1–10 个):1 个=单公司多期,多个=多公司单期横切;只需传一次数组 |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| dataset | string | – | – |
| format | string | yes | – |
| meta | object | yes | – |
| object | string | yes | – |
| page | object | yes | – |
| quota | object | yes | – |
No examples provided.
get_dimensions 查询维度与指标字典 ~124
获取报表与指标目录(financial statement catalog):可用报表 income 利润表、balance 资产负债表、cashflow 现金流量表、predict 业绩预告,以及各指标中文名、单位、是否比率与 repotype(basic 基础指标 / operation 运营指标)。是调用 company_records 前的机器可读字典。本工具不计积分。需要 API Token。
| Name | Type | Req | Description |
|---|---|---|---|
| reponame | string | – | 只返回指定报表下的指标 |
| repotype | string | – | basic / operation |
| Name | Type | Req | Description |
|---|---|---|---|
| metrics | array | yes | – |
| reports | array | yes | – |
| repoterms | array | yes | – |
No examples provided.
get_usage 查询额度 ~81
查询本账号额度(quota / usage):当前档位 free / VIP / SVIP、日调用护栏与积分余额的上限、已用、剩余与重置时间,以及最近到期的积分包。本工具不计积分,积分耗尽后仍可用;仍受账号维度的每分钟限流约束。
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| credit_packs | array | – | – |
| credits_free | integer | yes | – |
| credits_nearest_expiry_at | string|null | – | – |
| credits_paid | integer | yes | – |
| credits_total | integer | yes | – |
| daily_call_limit | integer | yes | – |
| daily_call_remaining | integer | yes | – |
| daily_call_reset_at | integer | – | – |
| daily_call_used | integer | yes | – |
| date | string | yes | – |
| max_credits_per_call | integer | – | – |
| subscribe_hint | string | – | – |
| tier | string | yes | – |
| token_prefix | string|null | – | – |
No examples provided.
list_indicators 查询指标字典 ~68
获取财务指标字典(China A-share financial indicators dictionary):指标 key 到中文名与单位的映射,全市场统一口径,与公司无关。取数前用它确认 repoitem_key 与金额单位(元)。本工具不计积分。需要 API Token。
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| indicators | object | yes | – |
| note | string | – | – |
| units | object | yes | – |
No examples provided.
list_report_periods 查询报告期 ~176
查询 A 股股票可用报告期(A-share report periods):先确认时间范围再取数。repoterm 决定口径——new 最新报告期(latest,默认)、quarter_t 单季度同比(single-quarter YoY)、quarter_h 单季度环比(single-quarter QoQ)、ttm 逐季度滚动四季合计(TTM)、year 年度(annual)。本工具不计积分。需要 API Token。
| Name | Type | Req | Description |
|---|---|---|---|
| repoterm | string | – | 报告期口径:new 最新报告期(latest,默认)、quarter_t 单季度同比(YoY)、quarter_h 单季度环比(QoQ)、ttm 逐季度 TTM、year 年度(annual) |
| scode | string | yes | A 股 6 位证券代码 |
| Name | Type | Req | Description |
|---|---|---|---|
| periods | array | yes | – |
| repoterm | string | yes | – |
| scode | string | yes | – |
No examples provided.
search_companies 搜索公司 ~104
搜索 A 股上市公司(China A-share company search):按 6 位证券代码(ticker)、公司简称或拼音首字母匹配,返回最多 10 条 {scode, sname},供后续取数确定证券代码。truncated=true 表示结果已截断,请细化关键词。本工具不计积分。需要 API Token。
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | 证券代码、简称或拼音首字母 |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | – |
| query | string | yes | – |
| results | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
How do I install the 洋葱财报OnionData-MCP server?
洋葱财报OnionData-MCP is a hosted endpoint at https://api.onionreport.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.onionreport.com
claude mcp add --transport http com-onionreport-oniondata-mcp 'https://api.onionreport.com/mcp'
What is the 洋葱财报OnionData-MCP server?
洋葱财报OnionData-MCP is listed in the public MCP registry as com.onionreport/oniondata-mcp. 洋葱财报OnionData-MCP 提供 A 股上市公司多口径财报数据,覆盖利润表、资产负债表、现金流量表,支持单季同比/环比、逐季度 TTM、年度与最新报告期近 10 期查询。 This page covers its hosted endpoint (https://api.onionreport.com/mcp).
Is the 洋葱财报OnionData-MCP server safe to use?
洋葱财报OnionData-MCP scores 74 out of 100 on VerifyMCP. 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 洋葱财报OnionData-MCP server expose?
洋葱财报OnionData-MCP exposes 6 tools: search_companies, list_report_periods, list_indicators, company_records, get_dimensions, get_usage. Their descriptions and schemas cost roughly 1,236 tokens of context every time the server is loaded.
Does the 洋葱财报OnionData-MCP server require authentication?
Yes. 洋葱财报OnionData-MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the 洋葱财报OnionData-MCP server still maintained?
洋葱财报OnionData-MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the 洋葱财报OnionData-MCP server?
VerifyMCP ran 12 checks on 洋葱财报OnionData-MCP, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about 洋葱财报OnionData-MCP: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.