Developer · Remote MCP server
Pulse
Ask about revenue, MRR, ad spend, LTV and CAC; install the Pulse SDK. Read-only.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
studio.pulsecircle/pulse- Version
- 0.1.2
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-02
- Updated
- 2026-09-02
- Publisher
- studio.pulsecircle
- Namespace
- Namespace verified by the MCP Registry via the domain pulsecircle.studio · how
- Website
- pulse.pulsecircle.studio/docs/mcp/
- Repository
- github.com/Pulse-Circle-Studio/pulse-sdk
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.pulse.pulsecircle.studio/mcp | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @pulse-circle/mcp | 0.1.2 | stdio |
How to connect Pulse
Pulse is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.pulse.pulsecircle.studio/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
It can also run locally from a Node.js package published to the npm registry: @pulse-circle/mcp version 0.1.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @pulse-circle/mcp@0.1.2.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"pulse": {
"command": "npx",
"args": [
"-y",
"@pulse-circle/mcp@0.1.2"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| pty-mcpInteractive PTY sessions over MCP: local shells, SSH, serial ports, and persistent remote sessions. | Local · stdio |
| PubchemPubChem MCP - NIH chemistry compound database (no auth) | Remote · HTTPLive check: ✓ handshake |
| Publicdata KrKorean public data API gateway for discovering and calling data.go.kr APIs from MCP clients. | Local · stdio |
| Pudge UiQuery pudge-ui - 93 skeuomorphic 2000s-era UI component specs - for coding-agent context. | Local · stdio |
| Pulse8 Ai Cortex Knowledge VaultAgent-native knowledge OS on Markdown: typed graph, hybrid search, and compiler over MCP. | Local · stdio |
| PulseWatch public knowledgePublic PulseWatch offers and monitoring guides. No private customer data or monitor controls. | Remote · HTTPLive check: ✓ handshake |
| Pump SDK MCP ServerBuild extend and maintain pump - Token creation buying selling migration fee collection. | Local · stdio |
| PumpcheckDetect npm download-pumping before adding a dependency: real usage vs inflated counter. | Remote · HTTPLive check: ✗ no handshake |