Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Pulse

NPM · @PULSE-CIRCLE/MCP · 2 COMPONENTS · SCANNED SEP 21

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

+3 this week 86 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Pulse-Circle-Studio/pulse-sdk). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 18 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 165 tokens (~82/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

npm · @pulse-circle/mcp

# add to Claude Code
claude mcp add studio-pulsecircle-pulse -- npx -y @pulse-circle/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "studio-pulsecircle-pulse": {
      "command": "npx",
      "args": [
        "-y",
        "@pulse-circle/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "studio-pulsecircle-pulse": {
      "command": "npx",
      "args": [
        "-y",
        "@pulse-circle/mcp"
      ]
    }
  }
}
# add to Codex CLI
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
    }
  }
}
# add to OpenClaw
openclaw mcp add studio-pulsecircle-pulse --command npx --arg -y --arg @pulse-circle/mcp
# ~/.hermes/config.yaml
mcp_servers:
  studio-pulsecircle-pulse:
    command: "npx"
    args: ["-y", "@pulse-circle/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "studio-pulsecircle-pulse": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pulse-circle/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add studio-pulsecircle-pulse -t stdio -c npx -a -y @pulse-circle/mcp
// mcp.json
{
  "mcpServers": {
    "studio-pulsecircle-pulse": {
      "command": "npx",
      "args": [
        "-y",
        "@pulse-circle/mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Sept 26 +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.

  • 18 Sept 26 +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.

  • 16 Sept 26 +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.

  • 14 Sept 26 +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.

  • 12 Sept 26 +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.

  • 10 Sept 26 +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.

  • 8 Sept 26 +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.

  • 6 Sept 26 +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.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Analysed npm/@pulse-circle/mcp@0.1.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Pulse-Circle-Studio/pulse-sdk
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Pulse-Circle-Studio/pulse-sdk/.github/workflows/publish.yml@refs/tags/mcp-v0.1.2
Rekor log index 2684513077
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:b8109a0f4becf314d0ef540d5254122d474eb25a5eaadc88f9c2750b81cf5faf2d1c85775450e0448ec693749b36090f373e0fe5a159b626a022ffdf6

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~165 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
pulse_connect ~79

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.

NameTypeReqDescription
sourcestringyes

No output schema declared.

No examples provided.

pulse_setup_guide ~86

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.

NameTypeReqDescription
platformstringyes

No output schema declared.

No examples provided.

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.