Syl Pulse

io.sylai由 sylai.io 发布官方发布者v0.1.0更新于 Oct 30, 2026

Causal analytics: ask a business question, get a deterministic causal answer and charts.

发布方自己的服务:Syl Guardian

已验证Streamable HTTP可网页运行数据与分析AI 与机器学习

概览

AI 生成的概览

托管式因果分析服务器,让助手基于数据集估计因果效应,并返回含图表的完整报告。

可以做什么
  • 对提供的数据集和业务问题执行因果分析,返回调整后的效应值、置信区间、分渠道效应、注意事项和图表
  • 支持以 CSV 文本或行对象列表传入数据,并可指定原因、结果、混杂因素、多个结果列和时间列
  • 可选择估计方法(调整 OLS、AIPW、IPW、PSM、DML 森林或确定性的规则默认值)
  • 可逐步在固定规则与 LLM 辅助之间切换,并可选返回 pass/caution/hold 结论或削减投放测试设计
适用场景
适合让助手用自有数据回答“广告投入是否驱动销售”这类业务问题,并给出确定性的统计报告而非模型猜测。也适合估算测试所需样本量或对某个主张做快速判断。
运行要求
远程 streamable HTTP 端点,无需本地安装包。所有请求(包括列出工具)都需在 X-API-Key 请求头中提供 Syl API 密钥(与 Syl Guardian 同一密钥,可申请试用密钥)。每次成功分析都会消耗 Pulse 配额或试用额度。
安装前请注意
API 密钥随每个请求以请求头形式发送,需妥善保密。数据集和问题会发送到托管服务;cleaning、discovery、summary 三步默认启用 LLM,除非改为 rule,否则数据可能传给第三方模型。分析会消耗配额。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Syl Pulse,将其添加到工作区。
  2. 连接 X-API-Key 凭据。它们会被私密存储,绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.sylai%2Fpulse/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "syl-pulse": {
      "type": "http",
      "url": "https://pulse.sylai.io/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

Syl Pulse MCP

Syl Pulse is causal analytics for business questions. Give your agent a dataset and a question like "Does ad spend drive sales?" and get back the full Pulse report: the adjusted causal effect with its confidence interval, a by-channel breakdown, caveats and assumptions, and charts (causal graph, effect, trend). When the question asks about sample size or test duration, it also returns a spend-cut test design.

All numbers are deterministic statistics. They are never computed by an LLM, and the figures in the report prose are checked against the computed numbers. Optional LLM help (dataset cleaning, causal-graph pruning, estimator choice, report prose) is controlled per step with config; see Engine config.

This repository holds the public listing metadata and connection instructions for the hosted Pulse MCP server. Pulse itself is a hosted service.

Connect

Claude Code:

bash
claude mcp add --transport http syl-pulse https://pulse.sylai.io/mcp \  --header "X-API-Key: <your key>"

Claude Desktop (via mcp-remote):

json
{  "mcpServers": {    "syl-pulse": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://pulse.sylai.io/mcp",               "--header", "X-API-Key:${SYL_API_KEY}"],      "env": { "SYL_API_KEY": "<your key>" }    }  }}

Then ask your agent: "Use pulse_analyze on this data: does ad_spend drive new_customers, adjusting for seasonality? How long would a spend-cut test need to run?"

Every request needs the key, including tool listing. Each successful analysis counts against your Pulse quota or trial.

Tool: pulse_analyze

Estimates a causal effect from a dataset and answers a business question.

ArgumentDescription
questionRequired. The business question, e.g. "Does ad spend drive sales?".
csv or dataDataset as CSV text or a list of row objects (exactly one).
cause, effectOptional. Treatment and outcome columns; inferred from the question if omitted.
confoundersOptional. Columns to adjust for, in addition to those discovered.
outcomesOptional. Several outcome columns, for by-channel effects.
time_colOptional. Time column, used for the test-design cadence.
include_guardian_verdictAlso return a pass / caution / hold verdict, computed locally (uses no Guardian quota).
include_chartsAttach chart images (default true).
include_test_designForce the spend-cut test design on or off; by default it appears only when the question asks about sample size, power or test duration.
estimatorOptional. One of ols_adjusted, aipw, ipw, psm, dml_forest, or rule (the deterministic default). Omit to follow config.estimator.
configOptional object choosing rule or llm per step: cleaning, discovery, estimator, summary. See Engine config.

The result's first content block is the report text, followed by chart images. The structured result has the effect size with its confidence interval, per-channel effects, confidence, caveats, and the optional verdict and test design. It also reports the estimator_used, the resolved config, and engine_steps. An invalid config (unknown key or a value other than rule or llm) comes back as a tool error, and misspelled argument names are rejected rather than ignored.

Engine config

config lets you choose, per step, whether the engine uses fixed rules or an LLM. Each value is "rule" or "llm". Omitted keys use the defaults:

StepDefaultWhat it controls
cleaningllmDataset cleaning: derived columns and null imputation. The LLM only picks a strategy per column; the values are computed deterministically, and your cause and effect columns are never imputed.
discoveryllmPruning and orienting the causal graph, naming cause and effect from your question when you omit them, and reading your question to decide on optional extras such as a subgroup breakdown, a robustness check or a test design.
estimatorruleChoosing the estimator. With llm, the model picks from the supported set based on each method's documentation, and may also choose a matching method. With rule, the deterministic default is used.
summaryllmllm writes the report prose; rule uses a fixed template.

The model key is provided by the service; you never supply one. rule always works. If an llm step cannot run, it falls back to rule, and engine_steps reports {requested, used, fallback_reason} for each step. Setting all four to rule makes no LLM calls.

Example: {"config": {"estimator": "llm", "summary": "rule"}}.

Which settings can change a number: cleaning: llm (imputation strategy, derived-column drops), discovery: llm (the adjustment set) and estimator: llm (the method). summary: llm changes prose only. For results that don't depend on an LLM at all, set cleaning, discovery and estimator to rule.

For a quick pass/caution/hold check on a single claim, see the sibling server Syl Guardian MCP.

Support

Questions or issues: https://sylai.io or [email protected].

License

The files in this repository (metadata and documentation) are MIT licensed; see LICENSE. The Syl Pulse service is proprietary.

来源:README.md,提交 8b5c0b8

工具

1

pulse_analyze

Estimate a causal effect from a dataset and answer a business question. Provide exactly one of ``csv`` (CSV text) or ``data`` (list of row objects). Returns the full long-form Pulse report (the same answer an email reply contains) as the primary text content and as ``report`` in the structured result, followed by chart PNGs as image content blocks (unless ``include_charts`` is false). Structured fields: the adjusted effect size (``ate``/``effect_size``) with its confidence interval (``ci_low``, ``ci_high``, ``ci_range``), per-channel effects (``channels``, keyed by outcome), confidence, and caveats. A ``test_design`` (how long a spend-cut test would take to confirm the effect, and whether the data already suffices) is included only when the question asks about sample size, power, or how long a test would take, or when ``include_test_design`` is true; otherwise it is null. With ``include_guardian_verdict`` it also returns ``guardian_verdict`` ``{verdict: pass|caution|hold, reason}``, computed locally. All numbers are deterministic statistics, never LLM-generated. Args: question: The business question, e.g. "Does ad spend drive sales?". csv: Dataset as CSV text. data: Dataset as a list of row records (alternative to ``csv``). cause: Treatment column (inferred from the question if omitted). effect: Outcome column (inferred if omitted). confounders: Columns to adjust for, in addition to those discovered. outcomes: Several outcome columns, for by-channel effects. time_col: Time column (used for the test-design cadence). include_guardian_verdict: Also return a pass/caution/hold verdict. include_charts: Attach chart images (DAG, effect, trend) as image content. include_test_design: Force the spend-cut test design / sample-size section on (true) or off (false). Omit (null) to include it only when the question asks about sample size, statistical power, or how long a test would take.

输入参数csvdatacauseeffectoutcomesquestion必填time_colconfoundersinclude_chartsinclude_test_designinclude_guardian_verdict

版本历史

1
  1. v0.1.0最新Oct 22, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Sylai 集成