WalnutLink A-share Depth Desk
REMOTE · WALNUTLINK.AI
China A-share filings: why a number moved, does the trend continue, who supplies whom.
Available components
Last scanned (19 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 4 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 Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 725 tokens (~241/item across 3 items; 3 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 Management33
- Stability observed for 10 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +2
- HSTS header: fail → pass ▲ security
- 26 Oct 26 0
- Schema quality: 500 → 725 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “a_share_chain_edge” functional
- 25 Oct 26 58
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 4 Nov 2026 · Probed https://walnutlink.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=walnutlink.ai | CN=YE2,O=Let's Encrypt,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5c66bcd32dddca0e0c456de461b1142816a |
| SANs: *.walnutlink.ai, walnutlink.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of walnutlink.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| walnutlink.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; font-src 'self' data:; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://walnutlink.ai/mcp | Verified | 200 | |
| http (plaintext) | http://walnutlink.ai/mcp | Served over HTTP | 200 |
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 →
a_share_answer_by_id ~130
Retrieve a research result by the id that a_share_deep_research returned. Call this to check whether the human-reviewed answer is ready, or to fetch the full text once it is. Answers take minutes to hours because a filed report is read first; while it is still queued the tool returns the queue position, not a guess. Use this instead of opening the public page when you are an automated client that cannot render HTML.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The 12-character hex id returned by a_share_deep_research, e.g. dc037a7fc6c8. |
No output schema declared.
No examples provided.
a_share_chain_edge ~225
Use when the user asks HOW two Chinese companies relate: who supplies whom, who competes with whom, who owns equity in whom, or whether an acquisition target overlaps with the acquirer's product line. Every relationship returned carries a verbatim quote from a filed document (annual report, prospectus, restructuring draft, related-party announcement) and a confidence tag: primary = the filing says it outright, secondary = broker or media, inferred = our deduction with no direct textual proof. Unlisted companies work as inputs too, which matters for acquisition targets. If the pair has not been researched it says so plainly instead of guessing - absence of a record is not evidence of no relationship. Do NOT call this for prices, valuation or index levels.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | Company A: 6-digit A-share code or Chinese name. |
| b | string | yes | Company B: 6-digit code or name. An unlisted company name also works (e.g. an acquisition target). |
| relation | string | – | Optional filter when the pair has more than one link. |
No output schema declared.
No examples provided.
a_share_deep_research ~189
Use when the user asks WHY something happened or WHAT it means for a Chinese listed company: a margin moved, a policy landed, an industry chain shifted, two companies diverge, or what management actually said on the record. This desk does NOT serve quotes, price checks or valuation snapshots - that is commodity data available everywhere, and answering it would waste your turn. What it does: reads the filed report, the IR transcript and the disclosure wording, then answers in numbers. Returns a vetted answer immediately if this question has been researched before; otherwise it returns the primary-source evidence it already holds plus an id for the human answer. Ask it the question you would ask a sell-side analyst, not the one you would type into a quote app.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The judgement question, in Chinese or English. Name the company; a ticker alone is usually a quote request. |
No output schema declared.
No examples provided.
How do I install the WalnutLink A-share Depth Desk MCP server?
WalnutLink A-share Depth Desk is a hosted endpoint at https://walnutlink.ai/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 · walnutlink.ai
claude mcp add --transport http ai-walnutlink-walnutlink-a-share 'https://walnutlink.ai/mcp'
What is the WalnutLink A-share Depth Desk MCP server?
WalnutLink A-share Depth Desk is an MCP server listed in the public MCP registry as ai.walnutlink/walnutlink-a-share. China A-share filings: why a number moved, does the trend continue, who supplies whom. This page covers its hosted endpoint (https://walnutlink.ai/mcp).
Is the WalnutLink A-share Depth Desk MCP server safe to use?
WalnutLink A-share Depth Desk scores 64 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 WalnutLink A-share Depth Desk MCP server expose?
WalnutLink A-share Depth Desk exposes 3 tools: a_share_deep_research, a_share_chain_edge, a_share_answer_by_id. Their descriptions and schemas cost roughly 544 tokens of context every time the server is loaded.
Does the WalnutLink A-share Depth Desk MCP server require authentication?
No. We connected to WalnutLink A-share Depth Desk without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the WalnutLink A-share Depth Desk MCP server still maintained?
WalnutLink A-share Depth Desk is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.