# Murmur (npm · murmur-mcp)

Deterministic crowd simulation: personas, feeds and analyst reports for pricing and launch.

- Trust score: 33/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- npm · `murmur-mcp`: 33/100 (this document), [markdown](https://verifymcp.io/servers/ratz00007-murmur-mcp/murmur-mcp.md), [page](https://verifymcp.io/servers/ratz00007-murmur-mcp/murmur-mcp)

## Channel facts

- Registry: `npm`
- Package: `murmur-mcp`
- Version: `1.0.0`
- 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-11-04.

- **Supply Chain Security**: 80/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 51 of 128 dependencies flagged as unhealthy (1 deprecated).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it.

## Install

### How do I install the Murmur MCP server?

Murmur runs locally as an npm package, launched with npx -y murmur-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 ratz00007-murmur-mcp -- npx -y murmur-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "ratz00007-murmur-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "murmur-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ratz00007-murmur-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "murmur-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ratz00007-murmur-mcp -- npx -y murmur-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ratz00007-murmur-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "murmur-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ratz00007-murmur-mcp --command npx --arg -y --arg murmur-mcp
```

### Hermes

```yaml
mcp_servers:
  ratz00007-murmur-mcp:
    command: "npx"
    args: ["-y", "murmur-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "ratz00007-murmur-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "murmur-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ratz00007-murmur-mcp -t stdio -c npx -a -y murmur-mcp
```

### Other

```json
{
  "mcpServers": {
    "ratz00007-murmur-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "murmur-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-11-01 (score 33)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/ratz00007-murmur-mcp/murmur-mcp#diagnostics

## Score history

- 2026-11-04: 33
- 2026-11-03: 33
- 2026-11-02: 33
- 2026-11-01: 33

## Common questions

### What is the Murmur MCP server?

Murmur is an MCP server listed in the public MCP registry as io.github.Ratz00007/murmur-mcp. Deterministic crowd simulation: personas, feeds and analyst reports for pricing and launch. This page covers its npm package (murmur-mcp).

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

Murmur scores 33 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. 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.

### Is the Murmur MCP server still maintained?

Murmur is still listed as active in the MCP registry. We last reached this channel on 4 November 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 Murmur MCP server under?

Murmur declares the Apache-2.0 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/murmur-mcp
- Socket report: https://socket.dev/npm/package/murmur-mcp
- Repository: https://github.com/Ratz00007/murmur-mcp
- Changelog RSS feed: https://verifymcp.io/servers/ratz00007-murmur-mcp/murmur-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ratz00007-murmur-mcp/murmur-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ratz00007-murmur-mcp/murmur-mcp