# Pulse (npm · @pulse-circle/mcp)

Ask about revenue, MRR, ad spend, LTV and CAC; install the Pulse SDK. Read-only.

- Trust score: 86/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.pulse.pulsecircle.studio`: 38/100, [markdown](https://verifymcp.io/servers/studio-pulsecircle-pulse/mcp.md), [page](https://verifymcp.io/servers/studio-pulsecircle-pulse/mcp)
- npm · `@pulse-circle/mcp`: 86/100 (this document), [markdown](https://verifymcp.io/servers/studio-pulsecircle-pulse/pulse-circle-mcp.md), [page](https://verifymcp.io/servers/studio-pulsecircle-pulse/pulse-circle-mcp)

## Channel facts

- Registry: `npm`
- Package: `@pulse-circle/mcp`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-09-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Pulse-Circle-Studio/pulse-sdk).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 18 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 165 tokens (~82/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 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 2 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 Pulse MCP server?

Pulse runs locally as an npm package, launched with npx -y @pulse-circle/mcp. 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 studio-pulsecircle-pulse -- npx -y @pulse-circle/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "studio-pulsecircle-pulse": {
      "command": "npx",
      "args": [
        "-y",
        "@pulse-circle/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "studio-pulsecircle-pulse": {
      "command": "npx",
      "args": [
        "-y",
        "@pulse-circle/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add studio-pulsecircle-pulse -- npx -y @pulse-circle/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "studio-pulsecircle-pulse": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pulse-circle/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add studio-pulsecircle-pulse --command npx --arg -y --arg @pulse-circle/mcp
```

### Hermes

```yaml
mcp_servers:
  studio-pulsecircle-pulse:
    command: "npx"
    args: ["-y", "@pulse-circle/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "studio-pulsecircle-pulse": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pulse-circle/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add studio-pulsecircle-pulse -t stdio -c npx -a -y @pulse-circle/mcp
```

### Other

```json
{
  "mcpServers": {
    "studio-pulsecircle-pulse": {
      "command": "npx",
      "args": [
        "-y",
        "@pulse-circle/mcp"
      ]
    }
  }
}
```

## 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-09-21 (score 86, +1)

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

### 2026-09-18 (score 85, +1)

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

### 2026-09-16 (score 84, +1)

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

### 2026-09-14 (score 83, +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-09-12 (score 82, +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-09-10 (score 81, +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-09-08 (score 80, +1)

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

### 2026-09-06 (score 79, +1)

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

## MCP tools (2)

### `pulse_setup_guide` (~86 tokens)

Use when the user wants to add Pulse product analytics or event tracking to an app, or asks how to install the Pulse SDK. Returns the install command and code snippet for web, react-native, swift (iOS) or kotlin (Android) — apply it to the codebase yourself. Read-only: returns documentation, reads no account data.

Input parameters:

- `platform` (string, required)

### `pulse_connect` (~79 tokens)

Use when the user wants subscription revenue, MRR, LTV, trials or refunds in Pulse, or asks how to connect RevenueCat, the Apple App Store or Google Play. Returns the setup steps for that source: which keys to create and where to paste them. Read-only: returns documentation, connects nothing itself.

Input parameters:

- `source` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/studio-pulsecircle-pulse/pulse-circle-mcp#diagnostics

## Score history

- 2026-09-21: 86
- 2026-09-20: 85
- 2026-09-19: 85
- 2026-09-18: 85
- 2026-09-17: 84
- 2026-09-16: 84
- 2026-09-15: 83
- 2026-09-14: 83
- 2026-09-13: 82
- 2026-09-12: 82
- 2026-09-11: 81
- 2026-09-10: 81
- 2026-09-09: 80
- 2026-09-08: 80
- 2026-09-07: 79
- 2026-09-06: 79
- 2026-09-05: 78
- 2026-09-04: 78
- 2026-09-03: 78
- 2026-09-02: 62
- 2026-09-01: 73

## Common questions

### What is the Pulse MCP server?

Pulse is an MCP server listed in the public MCP registry as studio.pulsecircle/pulse. Ask about revenue, MRR, ad spend, LTV and CAC; install the Pulse SDK. Read-only. This page covers its npm package (@pulse-circle/mcp).

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

Pulse scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Pulse MCP server expose?

Pulse exposes 2 tools: pulse_setup_guide, pulse_connect. Their descriptions and schemas cost roughly 165 tokens of context every time the server is loaded.

### Is the Pulse MCP server still maintained?

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

### What licence is the Pulse MCP server under?

Pulse declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pulse-circle/mcp
- Socket report: https://socket.dev/npm/package/@pulse-circle/mcp
- Repository: https://github.com/Pulse-Circle-Studio/pulse-sdk
- Website: https://pulse.pulsecircle.studio/docs/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/studio-pulsecircle-pulse/pulse-circle-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/studio-pulsecircle-pulse/pulse-circle-mcp.json
- HTML version of this page: https://verifymcp.io/servers/studio-pulsecircle-pulse/pulse-circle-mcp