Stock Analysis MCP Server
This project is a server built using the FastMCP framework, providing various tools for accessing and analyzing stock market data.
Features
The server exposes the following tools:
- Concept Power Tools (
/stock): Analyzes the strength of stock concept sectors based on fund flow and price change. - Finance Tools (
/finance): Provides access to stock financial core indicators and company information. - Stock F10 Tools (
/f10): Fetches and summarizes Stock F10 information. - Market Emotion Tools (
/market): Retrieves and summarizes A-share market emotion indicators. - Stock Keep Up Tools (
/stockUp): Provides lists of continuous limit-up stocks and limit-up stocks. - Web Search Tools (Tavily) (
/websearch): Provides a web search tool.
Setup and Installation
-
Clone the repository:
git clone <repository_url> cd mcp_stock
-
Create a virtual environment (recommended):
python -m venv venv source venv/bin/activate
-
Install dependencies:
Install the required packages using pip:
pip install -r requirements.txt playwright install
-
Configuration:
Some tools might require API keys or other configuration. Please refer to the
config.pyfile and potentially create a.envfile if necessary (based onos.getenvusage inserver.py).TAVILY_API_KEY= -
Run the server:
You can run the server using the
server.pyscript. The server will listen on the port specified by thePORTenvironment variable, defaulting to 8000.fastmcp run server.py --transport=sse --port=8000 --host=0.0.0.0
To run on a specific port:
fastmcp run server.py --transport=sse --port=8000 --host=0.0.0.0
Usage
Once the server is running, you can interact with the tools via the /mcp prefix followed by the tool's mount path (e.g., /mcp/stock, /mcp/finance). The specific endpoints and expected parameters for each tool can be found by examining the tool definitions within each tool's Python file.
Metadata
Release files for iflow-mcp_parsedark-mcp_stock 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_parsedark_mcp_stock-0.1.0.tar.gz | 10.5 kB | Without provenance | Details for iflow_mcp_parsedark_mcp_stock-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_parsedark_mcp_stock-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_parsedark_mcp_stock-0.1.0-py3-none-any.whl |
Total release size: 26.3 kB
Release files / iflow_mcp_parsedark_mcp_stock-0.1.0.tar.gz
| Download URL | iflow_mcp_parsedark_mcp_stock-0.1.0.tar.gz |
|---|---|
| Size | 10.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5faf25784f2f686949b3739797d389574009cc6bc393ff8bb5721a2881d80de1
|
|
BLAKE2b-256 checksum How to use checksums |
5348c2606a9b7b7247fd43e61f4021286ff8b0ab7d4abf9137333508a3fe850e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.8
|
Release files / iflow_mcp_parsedark_mcp_stock-0.1.0-py3-none-any.whl
| Download URL | iflow_mcp_parsedark_mcp_stock-0.1.0-py3-none-any.whl |
|---|---|
| Size | 15.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e66e7b0e324e790269bf19fd085ef7bdbb3e91f5b8d087bb929c057456895fa1
|
|
BLAKE2b-256 checksum How to use checksums |
9ec4429616a0ffff66918457d7fcc4c4b802cde0778e08566841423e9d8bf117
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.8
|
Security for iflow-mcp_parsedark-mcp_stock 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.