WalnutLink A-share Depth Desk

Name: WalnutLink A-share Depth Desk
Author: ai.walnutlink

MCP serverMCP

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

by ai.walnutlinkrepository ↗homepage ↗v1.3.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"walnutlink-a-share-depth-desk","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability16/16 checks ok

when	check	result	http	latency	detail
4 h ago	mcp initialize	ok	200	619 ms	server walnutlink-a-share 1.2.0 · protocol 2025-06-18 · 3 tools
13 h ago	mcp initialize	ok	200	756 ms	server walnutlink-a-share 1.2.0 · protocol 2025-06-18 · 3 tools
21 h ago	mcp initialize	ok	200	902 ms	server walnutlink-a-share 1.2.0 · protocol 2025-06-18 · 3 tools
29 h ago	mcp initialize	ok	200	681 ms	server walnutlink-a-share 1.2.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	862 ms	server walnutlink-a-share 1.2.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	699 ms	server walnutlink-a-share 1.2.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	366 ms	server walnutlink-a-share 1.2.0 · protocol 2025-06-18 · 3 tools
3 d ago	mcp initialize	ok	200	731 ms	server walnutlink-a-share 1.2.0 · protocol 2025-06-18 · 3 tools
3 d ago	mcp initialize	ok	200	642 ms	server walnutlink-a-share 1.2.0 · protocol 2025-06-18 · 3 tools
3 d ago	mcp initialize	ok	200	723 ms	server walnutlink-a-share 1.2.0 · protocol 2025-06-18 · 3 tools

Tools observed via MCP handshake

a_share_deep_research — 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 com
a_share_chain_edge — 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 ov
a_share_answer_by_id — 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 te

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryai.walnutlink/walnutlink-a-share

first seen 5 d ago · fetched 2 d agoopen ↗

Field history (7 recent events)

5 d ago · declared · summary → "China A-share filings: why a number moved, does the trend continue, who supplies whom."
5 d ago · declared · description → "China A-share filings: why a number moved, does the trend continue, who supplies whom."
5 d ago · declared · publisherName → "ai.walnutlink"
5 d ago · declared · homepageUrl → "https://walnutlink.ai"
5 d ago · declared · repoUrl → "https://github.com/WalnutLink/walnutlink-mcp"
5 d ago · declared · version → "1.3.0"
5 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from