Configuring marketingdashboard
The README documents no user-facing configuration keys or required API-key variables. The service is designed to work without API keys and uses the bundled Node proxy by default. DeepSeek Harness installs marketingdashboard in the web profile, and the plugin is delivered as a dsh bundle.
Data service and interfaces
DeepSeek Harness exposes five MCP tools supplied by marketingdashboard for A-share, Hong Kong and US quotes, sector rankings, futures, money flow and 7×24 news. The Node service aggregates public sources and serves application data under api routes, written in the README as /api/*. /api/stats reports request, upstream-fetch and 429 counters. The React frontend polls for updates, while src/lib/market.ts batch-fetches the watched codes every five seconds and distributes one quote snapshot.
Runtime requirements
The repository documents Node.js 18+ as a requirement. The service is single-process, uses no database or external storage, and keeps endpoint responses in bounded in-memory caches with LRU handling and periodic sweeps. Spot prices are collected by the server every four hours into local history files. The frontend is a React 19 application built with Vite 7 and can also run as a PWA.
How marketingdashboard behaves
Cache lifetimes vary by endpoint: quotes use five seconds, while sector membership can use up to 24 hours. In-flight request deduplication shares one upstream fetch across concurrent misses. Failure backoff applies negative caching from five seconds to two minutes, and browser-direct fallbacks are throttled per code. The upstream summary describes a three-tier fallback arrangement; the README specifically documents direct-browser fallback for some Tencent and Wallstreetcn endpoints.
The README does not specify additional command-line flags or configuration files.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub