AKShare MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_stock_historical_dataC | Get stock historical data from HTTP sources. |
| get_stock_realtime_dataC | Get stock real-time data from HTTP sources. |
| get_stock_listC | Get stock list from HTTP sources. |
| get_fund_listC | Get fund list from HTTP sources. |
| search_stockC | Search stock information from HTTP sources. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct resource or data type: funds vs. stocks, and within stocks: historical data, real-time data, list, and search. No overlapping purposes.
All tool names follow a verb_noun pattern in snake_case (get_fund_list, get_stock_historical_data, etc.). The only slight variation is 'search_stock' instead of 'get_search_stock', but it still maintains the verb_noun structure.
With 5 tools covering both fund and stock data retrieval, the count is well-scoped for a financial data API. It provides essential operations without being overwhelming.
The tool set covers core read operations for stocks and funds but lacks fund historical and real-time data, which are minor gaps. The primary domain (stock and fund lookups) is well-covered.