Enterprise Research Evidence Chain

Official registry Search and web

Read-only enterprise research MCP: frameworks, frozen snapshots, sourced results. No trading advice.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

PYPI package diyan-research-mcp
Claude Code
claude mcp add enterprise-research-evidence-chain -e 'DIYAN_API_KEY=<your diyan_api_key>' -e 'DIYAN_TRANSPORT=<DIYAN_TRANSPORT>' -- uvx diyan-research-mcp==0.1.1
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "enterprise-research-evidence-chain": {
            "command": "uvx",
            "args": [
                "diyan-research-mcp==0.1.1"
            ],
            "env": {
                "DIYAN_API_KEY": "<your diyan_api_key>",
                "DIYAN_TRANSPORT": "<DIYAN_TRANSPORT>"
            }
        }
    }
}

Environment variables

  • DIYAN_API_KEY required secret Tenant credential issued by Diyan. Fill this on the MCP detail page.
  • DIYAN_TRANSPORT stdio, sse, or streamable-http. Defaults to sse in hosted environments; use stdio for local clients.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. diyan-research-mcp · 企业研究证据链
  2. 这个仓库里没有数据
  3. 工具
  4. 配置
  5. 本地运行
  6. 边界
  7. 服务端契约
  8. 许可与归属

diyan-research-mcp · 企业研究证据链

面向企业投研与产业研究团队的只读研究 MCP,提供研究框架、冻结快照与历史因子摘要,每条结论附来源、数据截至日与证伪条件,不输出交易建议。

这个仓库里没有数据

本仓库只包含转发壳,职责是三件事:校验入参、携带租户凭据调用研究数据服务、在返回前剥掉交易类字段。研究框架、冻结快照、假设台账和因子摘要都存放在服务端,不随代码分发。

AI 客户端  ──MCP──▶  diyan-research-mcp(本仓库)  ──HTTPS──▶  研究数据服务
                     入参校验 / 凭据转发 / 输出过滤        数据、租户、档位、配额、审计

这样分层有三个后果,都是有意为之:

  • 壳可以公开审阅,因为它不含任何专有数据,也不含任何密钥。
  • 租户身份、档位和配额一律由服务端裁定,壳不做信任判断,也就无法被绕过。
  • 输出过滤留在壳内而不是只放在服务端,即便服务端出错或被篡改,交易类表述也无法离开进程。

工具

工具说明
framework_excerpt读取研究框架片段,可选 enterprise / business / finance / people / brand
stock_snapshot_latest读取最新冻结的股票研究快照
hypothesis_get读取通过交付证据门槛的冻结假设
cognition_radar_read读取历史主题研究雷达摘要
ic_backtest_summary读取冻结的因子历史 IC 摘要
research_analyze_safe调用受控研究接口做单标的研判

工具是否可用取决于凭据对应的档位。免费档开放研究框架与部分冻结快照,其余返回 error_type: backend 并说明需要付费租户凭据。

配置

唯一必填项是 DIYAN_API_KEY,在 MCP 详情页填写即可。其余变量见 .env.example,只在自建部署或联调时需要。

凭据缺失时进程仍会正常启动,但每次工具调用都会返回明确的配置错误。这是刻意的:托管环境可能在使用者填写凭据之前就拉起进程,启动即崩溃会让详情页上的服务看起来是坏的。

本地运行

python -m pip install -r requirements.txt
export PYTHONPATH=src
export DIYAN_API_KEY=<你的租户凭据>
export DIYAN_TRANSPORT=stdio
python -m diyan_research_mcp.server

测试不需要网络和凭据:

python -m unittest discover -s tests -v

边界

  • 只读。没有任何写入、下单、部署或数据导出能力。
  • 不返回实时行情。快照与摘要都是冻结产物,每条结果都带 as_of。
  • 不生成买卖、仓位、股数、跟单或收益承诺。含此类表述的提问在发出请求前就会被拒绝。
  • 不读取使用者的本地文件、本地数据库或非必要环境变量。

服务端契约

如需自建后端,接口定义见 docs/BACKEND_CONTRACT.md。

许可与归属

由深圳瞳桦文化传媒有限公司开发与维护。MIT 许可,见 LICENSE。

Frequently asked questions

What is Enterprise Research Evidence Chain?

Read-only enterprise research MCP: frameworks, frozen snapshots, sourced results. No trading advice.

How do I install Enterprise Research Evidence Chain?

It runs on your machine. In Claude Code: claude mcp add enterprise-research-evidence-chain -e 'DIYAN_API_KEY=<your diyan_api_key>' -e 'DIYAN_TRANSPORT=<DIYAN_TRANSPORT>' -- uvx diyan-research-mcp==0.1.1. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Enterprise Research Evidence Chain need an API key?

Yes. It expects DIYAN_API_KEY, which you set in its configuration.

Is Enterprise Research Evidence Chain open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Enterprise Research Evidence Chain?

It is published by mikeli20221102-ux. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.