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 整合