# WalnutLink A-share Depth Desk (remote · walnutlink.ai)

China A-share filings: why a number moved, does the trend continue, who supplies whom.

- Trust score: 64/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `walnutlink.ai`: 64/100 (this document), [markdown](https://verifymcp.io/servers/ai-walnutlink-walnutlink-a-share/walnutlink.md), [page](https://verifymcp.io/servers/ai-walnutlink-walnutlink-a-share/walnutlink)

## Channel facts

- Endpoint: `https://walnutlink.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ai-walnutlink-walnutlink-a-share 'https://walnutlink.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-walnutlink-walnutlink-a-share": {
      "url": "https://walnutlink.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-walnutlink-walnutlink-a-share": {
      "type": "http",
      "url": "https://walnutlink.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-walnutlink-walnutlink-a-share]
url = "https://walnutlink.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-walnutlink-walnutlink-a-share": {
      "type": "remote",
      "url": "https://walnutlink.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-walnutlink-walnutlink-a-share --url 'https://walnutlink.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-walnutlink-walnutlink-a-share:
    url: "https://walnutlink.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-walnutlink-walnutlink-a-share": {
      "Transport": "http",
      "Url": "https://walnutlink.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-walnutlink-walnutlink-a-share -t streamable-http -u 'https://walnutlink.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-walnutlink-walnutlink-a-share": {
      "type": "http",
      "url": "https://walnutlink.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 64, +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.

### 2026-11-01 (score 63, +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.

### 2026-10-30 (score 62, +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.

### 2026-10-28 (score 61, +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.

### 2026-10-27 (score 60, +2)

- [security improvement] HSTS header: fail → pass

### 2026-10-26 (score 58, 0)

- [functional regression] Schema quality: 500 → 725
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “a_share_chain_edge”

### 2026-10-25 (score 58)

First indexed and scored.

## MCP tools (3)

### `a_share_deep_research` (~189 tokens)

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.

Input parameters:

- `question` (string, required): The judgement question, in Chinese or English. Name the company; a ticker alone is usually a quote request.

### `a_share_chain_edge` (~225 tokens)

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.

Input parameters:

- `a` (string, required): Company A: 6-digit A-share code or Chinese name.
- `b` (string, required): 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.

### `a_share_answer_by_id` (~130 tokens)

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.

Input parameters:

- `id` (string, required): The 12-character hex id returned by a_share_deep_research, e.g. dc037a7fc6c8.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-walnutlink-walnutlink-a-share/walnutlink#diagnostics

## Score history

- 2026-11-04: 64
- 2026-11-03: 64
- 2026-11-02: 63
- 2026-11-01: 63
- 2026-10-31: 62
- 2026-10-30: 62
- 2026-10-29: 61
- 2026-10-28: 61
- 2026-10-27: 60
- 2026-10-26: 58
- 2026-10-25: 58

## Common questions

### 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.

## Links

- Remote endpoint: https://walnutlink.ai/mcp
- Repository: https://github.com/WalnutLink/walnutlink-mcp
- Website: https://walnutlink.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-walnutlink-walnutlink-a-share/walnutlink.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-walnutlink-walnutlink-a-share/walnutlink.json
- HTML version of this page: https://verifymcp.io/servers/ai-walnutlink-walnutlink-a-share/walnutlink