DeepSeek Harness Plugin

sensedeal/cue-skills#cue-data-mcp

Stars ★ 6 Category Tools & Capabilities Added 2026-08-27

Exposes Cue public data MCP services to DeepSeek Harness: 15 streamable-http domains (~104 tools) for regulatory, macro, disclosures, statute, holdings, entity, academic, IPO, ESOP, buyback, footnote and fact-index data as native mcp__cue_<domain>__* tools.

Install

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:sensedeal/cue-skills#path:/dsh/cue-data-mcp

Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).

README

English · 中文

A DeepSeek Harness bundle that exposes Cue's public data MCP services as native mcp__cue_<domain>__* tools in any Harness profile. Each live data domain is wired as one @deepseek-ai/dsh-mcp-client instance (transport: streamable-http) against Cue's own endpoints — no SSRF guard needed, the URLs are fixed Cue endpoints and the tool set is the data surface.

15 live domains / ~104 tools (as of 2026-08-24): regulatory (OFAC/EU/BIS, 11), China regulatory (16), macro (15), US disclosures SEC EDGAR (5), CN disclosures (5), statute full text (3), institutional (2), entity data (2), academic (3), fact index (4), IPO (9), ESOP (10), buyback (2), footnote (14), margin (3). omni-reader is excluded — it has its own dedicated cue-omni-reader skill.

Install

dsh plugin --profile web add @cueai/dsh-cue-data-mcp
# or one-off
dsh web --patch ./dsh/cue-data-mcp/cordis.patch.yml

Configure

Only one credential is needed — env-driven:

# $DSH_HOME/.env (or export before launching dsh)
CUE_API_KEY=sk-...     # from https://cuecue.cn/hub/api-key

Each server sends Authorization: Bearer $CUE_API_KEY and the streamable-http Accept header.

Usage

After a restart the model sees mcp__cue_<domain>__* per domain (e.g. mcp__cue_regulatory__*, mcp__cue_macro__*, mcp__cue_ipo__*). Discover the live tool names with tools/list per endpoint; call them with tools/call.

Verify

dsh --profile web --dump-config     # should list 15 `mcp-cue_*` rows
# then in a session confirm the mcp__cue_* tools and a small data call succeed.

Security & scope

  • Requires CUE_API_KEY; the model can query Cue's data tool set but the endpoints are Cue-owned and fixed, so there is no arbitrary egress/SSRF surface.
  • Never put the key in chat, command arguments, this file, logs, or generated JSON.
  • The data endpoints are streamable-http; DSH bridges them with @deepseek-ai/dsh-mcp-client (peer dependency, ^0.1.1-rc.2).

Versioning / Rollback

  • @deepseek-ai/dsh-mcp-client is a peer dependency (Harness profile provides it).
  • Roll back: dsh plugin --profile web remove @cueai/dsh-cue-data-mcp.

License

MIT — see LICENSE.

Content from the project README on GitHub ↗

Links

GitHub repository ↗ Install via dsh-market ↗

More in this category

View the whole category →

Community comments

Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.