Enterprise Research Evidence Chain

io.github.mikeli20221102-uxPublished by GitHub account mikeli20221102-uxv0.1.1Updated Oct 27, 2026

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

The publisher's own server: Agent.chain.tokyo Address Contracts

VerifiedSTDIODesktop onlyFinanceKnowledge & Memory

Overview

AI-generated overview

Read-only enterprise research MCP that serves research frameworks, frozen stock snapshots, hypothesis records and factor summaries, each with sources and…

What you can do
  • Read research framework excerpts by domain such as enterprise, business, finance, people or brand
  • Read the latest frozen stock research snapshot for a subject
  • Read frozen hypotheses that passed a delivery evidence threshold
  • Read historical topic research radar summaries and frozen factor IC summaries
  • Run a controlled single-instrument research analysis through a safe endpoint
  • Every result carries sources, data as-of dates and falsification conditions
When to use it
For corporate investment and industry research teams that want an assistant to pull structured, sourced research material and frozen snapshots instead of live market data. Useful when conclusions need traceable sources and as-of dates, and when trading advice is explicitly out of scope.
Requirements
Runs locally as a Python package over stdio; install the diyan-research-mcp package and its requirements. A tenant credential is required in the DIYAN_API_KEY environment variable. DIYAN_TRANSPORT selects stdio, sse or streamable-http. Network access to the vendor's research data service is needed; the process starts without a key but tool calls then return configuration errors.
Before you install
The tenant credential DIYAN_API_KEY is forwarded to the vendor's research service, and tenant identity, tier and quota are decided server-side. Tool availability depends on the credential's tier; free tier covers frameworks and some snapshots, other tools return a backend error requiring a paid tenant credential. Read-only: no writes, orders, deployment or data export, and no live quotes.

Installation

In SourceWeft

  1. Open Enterprise Research Evidence Chain in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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,只在自建部署或联调时需要。

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

本地运行

bash
python -m pip install -r requirements.txtexport PYTHONPATH=srcexport DIYAN_API_KEY=<你的租户凭据>export DIYAN_TRANSPORT=stdiopython -m diyan_research_mcp.server

测试不需要网络和凭据:

bash
python -m unittest discover -s tests -v

边界

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

服务端契约

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

许可与归属

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

Source: README.md at commit 600a577

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Chain integrations