# Syl Pulse (remote · pulse.sylai.io)

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

- Trust score: 64/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `pulse.sylai.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/io-sylai-pulse/pulse.md), [page](https://verifymcp.io/servers/io-sylai-pulse/pulse)

## Channel facts

- Endpoint: `https://pulse.sylai.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 53/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 822 tokens (~822/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Syl Pulse MCP server?

Syl Pulse is a hosted endpoint at https://pulse.sylai.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-sylai-pulse 'https://pulse.sylai.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-sylai-pulse": {
      "url": "https://pulse.sylai.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-sylai-pulse": {
      "type": "http",
      "url": "https://pulse.sylai.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-sylai-pulse]
url = "https://pulse.sylai.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-sylai-pulse": {
      "type": "remote",
      "url": "https://pulse.sylai.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-sylai-pulse --url 'https://pulse.sylai.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-sylai-pulse:
    url: "https://pulse.sylai.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-sylai-pulse": {
      "Transport": "http",
      "Url": "https://pulse.sylai.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-sylai-pulse -t streamable-http -u 'https://pulse.sylai.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-sylai-pulse": {
      "type": "http",
      "url": "https://pulse.sylai.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 61, 0)

- [security] Tool “pulse_analyze” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 613 → 822
- [cosmetic] “pulse_analyze” added an optional parameter “config”
- [cosmetic] “pulse_analyze” added an optional parameter “estimator”

### 2026-10-28 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 58, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (1)

### `pulse_analyze` (~751 tokens)

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.
    estimator: Optional estima…

Input parameters:

- `cause`
- `config`
- `confounders`
- `csv`
- `data`
- `effect`
- `estimator`
- `include_charts` (boolean)
- `include_guardian_verdict` (boolean)
- `include_test_design`
- `outcomes`
- `question` (string, required)
- `time_col`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-sylai-pulse/pulse#diagnostics

## Score history

- 2026-11-05: 64
- 2026-11-04: 64
- 2026-11-03: 63
- 2026-11-02: 63
- 2026-11-01: 62
- 2026-10-31: 62
- 2026-10-30: 61
- 2026-10-29: 61
- 2026-10-28: 61
- 2026-10-27: 60
- 2026-10-26: 60
- 2026-10-25: 59
- 2026-10-24: 59
- 2026-10-23: 58
- 2026-10-22: 58

## Common questions

### What is the Syl Pulse MCP server?

Syl Pulse is an MCP server listed in the public MCP registry as io.sylai/pulse. Causal analytics: ask a business question, get a deterministic causal answer and charts. This page covers its hosted endpoint (https://pulse.sylai.io/mcp).

### Is the Syl Pulse MCP server safe to use?

Syl Pulse scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Syl Pulse MCP server expose?

Syl Pulse exposes 1 tool: pulse_analyze. Their descriptions and schemas cost roughly 751 tokens of context every time the server is loaded.

### Does the Syl Pulse MCP server require authentication?

No. We connected to Syl Pulse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Syl Pulse MCP server still maintained?

Syl Pulse is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://pulse.sylai.io/mcp
- Authorisation metadata: https://pulse.sylai.io/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/connor274/syl-pulse-mcp
- Website: https://sylai.io/pulse
- Changelog RSS feed: https://verifymcp.io/servers/io-sylai-pulse/pulse.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-sylai-pulse/pulse.json
- HTML version of this page: https://verifymcp.io/servers/io-sylai-pulse/pulse