Skip to content

Syl Pulse MCP server

io.sylai/pulsesylai.iostreamable-httpv0.1.0Scanned

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

1 tool: 1 only read.

Tools: 0 delete, 0 irreversible, 0 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Syl Pulse MCP server can do

The Syl Pulse MCP server is published by sylai.io, a domain the MCP Registry verified. It has 1 tool. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 8, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

1 tool

Only reads 1Show 1 read-only tool
  • pulse_analyzeEstimate a causal effect from a dataset and answer a business question.1 finding

    Why it is in this group

    • The name "pulse_analyze" says "analyze": a word for reading.

    Findings

    • Info

      The description is 2,731 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ll "rule" makes zero LLM calls. Numbers are deterministic in every mode."

      What this check looks for
    Description, as the server wrote it
    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 estimation method: ols_adjusted, aipw, ipw, psm or dml_forest (or "rule" for the deterministic default). Omit to follow ``config.estimator`` (default "rule"; "llm" lets the model choose from that list, falling back to the rule choice when no LLM key). config: Optional per-step engine config, e.g. {"summary": "rule"}. Keys: cleaning, discovery, estimator, summary; each "rule" (deterministic, no LLM call) or "llm" (LLM-assisted; falls back to rule and says so in ``engine_steps`` when no key is configured or the call fails). Defaults: cleaning=llm, discovery=llm, estimator=rule, summary=llm. All "rule" makes zero LLM calls. Numbers are deterministic in every mode.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:24 UTC, unchanged since Oct 23, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description is 2,731 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ll "rule" makes zero LLM calls. Numbers are deterministic in every mode."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http pulse https://pulse.sylai.io/mcp --header 'X-API-Key: <your-x-api-key>'
claude mcp add --transport http pulse https://pulse.sylai.io/mcp --header 'X-API-Key: <your-x-api-key>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__pulse__pulse_analyze"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pulse. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.sylai/pulse/verify?hash=8c807b5267e600f86699a9d5d0a40a5b6247c66e3f9b662092adea210be0faaa" | jq -e '.changed == false'

Pinned hash 8c807b5267e6, from Nov 8, 2026, 17:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.sylai/pulse/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.sylai/pulse
[![Anlyon Radar](https://radar.anlyon.com/badge/io.sylai/pulse.svg)](https://radar.anlyon.com/servers/io.sylai/pulse)

Source: MCP Registry · repository. Synced Oct 22, 2026, 20:17 UTC.

Syl Pulse MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Syl Pulse MCP server safe?

No scan can promise that. What its definitions show: 1 tool, all of which only read, and 1 finding from fixed checks. Read-only tools can still pass private data to a model.

Can the Syl Pulse MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Syl Pulse MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Syl Pulse MCP server have?

1 tool: 1 read. pulse_analyze.

Does the Syl Pulse MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Syl Pulse MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Syl Pulse MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.