# Samuraizer (npm · @samuraizer/mcp-server)

Local MCP server for meeting transcripts, summaries, action items & decisions — no cloud.

- Trust score: 82/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `@samuraizer/mcp-server`: 82/100 (this document), [markdown](https://verifymcp.io/servers/uladzkha-samuraizer/samuraizer-mcp-server.md), [page](https://verifymcp.io/servers/uladzkha-samuraizer/samuraizer-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@samuraizer/mcp-server`
- Version: `0.1.7`
- 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-20.

- **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.
  - 42 of 116 dependencies flagged as unhealthy.
- **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 (MIT).
  - Actively maintained (last published 12 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 529 tokens (~58/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 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 Samuraizer MCP server?

Samuraizer runs locally as an npm package, launched with npx -y @samuraizer/mcp-server. 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 uladzkha-samuraizer -- npx -y @samuraizer/mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "uladzkha-samuraizer": {
      "command": "npx",
      "args": [
        "-y",
        "@samuraizer/mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "uladzkha-samuraizer": {
      "command": "npx",
      "args": [
        "-y",
        "@samuraizer/mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add uladzkha-samuraizer -- npx -y @samuraizer/mcp-server
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add uladzkha-samuraizer --command npx --arg -y --arg @samuraizer/mcp-server
```

### Hermes

```yaml
mcp_servers:
  uladzkha-samuraizer:
    command: "npx"
    args: ["-y", "@samuraizer/mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "uladzkha-samuraizer": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@samuraizer/mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add uladzkha-samuraizer -t stdio -c npx -a -y @samuraizer/mcp-server
```

### Other

```json
{
  "mcpServers": {
    "uladzkha-samuraizer": {
      "command": "npx",
      "args": [
        "-y",
        "@samuraizer/mcp-server"
      ]
    }
  }
}
```

## 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-20 (score 82, −3)

- [functional] Stability: pass → 0.77

### 2026-09-19 (score 85, 0)

- [security] Stability: 0.97 → pass

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

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 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 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 80, +16)

- [security improvement] Malware scan: unverified → pass

## MCP tools (9)

### `normalize_audio` (~55 tokens)

Normalize Audio

Normalize an audio file to 16kHz mono PCM WAV format required by Whisper.

Input parameters:

- `inputPath` (string, required): Absolute path to the source audio file
- `outputPath` (string, required): Absolute path for the output WAV file

### `transcribe_audio` (~37 tokens)

Transcribe Audio

Transcribe an audio file using whisper.cpp. Returns the transcript text.

Input parameters:

- `filePath` (string, required): Absolute path to the audio file

### `summarize_transcript` (~45 tokens)

Summarize Transcript

Generate a concise meeting summary from transcript text.

Input parameters:

- `model` (string): Ollama model to use (optional)
- `transcriptText` (string, required): Full transcript text to summarize

### `extract_action_items` (~54 tokens)

Extract Action Items

Extract action items from a meeting transcript. Returns a JSON list of tasks with owner and due date.

Input parameters:

- `model` (string): Ollama model to use (optional)
- `transcriptText` (string, required): Full transcript text

### `extract_decisions` (~49 tokens)

Extract Decisions

Extract confirmed decisions from a meeting transcript. Returns a JSON list of decisions.

Input parameters:

- `model` (string): Ollama model to use (optional)
- `transcriptText` (string, required): Full transcript text

### `process_recording` (~62 tokens)

Process Recording

Run the full Samuraizer pipeline on an audio file. Returns summary, action items, decisions, and output file paths.

Input parameters:

- `filePath` (string, required): Absolute path to the audio file
- `model` (string): Ollama model to use (optional)

### `search_meetings` (~115 tokens)

Search meetings by summary text, name, action items, and decisions. Transcripts are not searched — use get_meeting for those. Returns ranked results with snippets.

Input parameters:

- `limit` (integer): Maximum results to return (default 10).
- `query` (string, required): Search query. Case-insensitive. Every word must appear somewhere in the searched fields, but they need not share a field. Words match as substrings ("export" finds "exporter"). Wrap words in double q…

### `list_meetings` (~37 tokens)

List all processed meetings, sorted newest first. Optionally limit results.

Input parameters:

- `limit` (integer): Maximum number of meetings to return.

### `get_meeting` (~34 tokens)

Retrieve the full processed output for a specific meeting by id.

Input parameters:

- `id` (string, required): The meeting id (ULID).

## Diagnostics

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

## Score history

- 2026-09-20: 82
- 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: 64
- 2026-09-06: 79
- 2026-09-05: 78
- 2026-09-04: 78
- 2026-09-03: 78
- 2026-09-02: 77
- 2026-09-01: 77
- 2026-08-31: 76
- 2026-08-30: 76
- 2026-08-29: 75
- 2026-08-28: 71
- 2026-08-27: 71
- 2026-08-26: 71
- 2026-08-25: 70
- 2026-08-24: 70
- 2026-08-23: 70
- 2026-08-22: 70

## Common questions

### What is the Samuraizer MCP server?

Samuraizer is an MCP server listed in the public MCP registry as io.github.UladzKha/samuraizer. Local MCP server for meeting transcripts, summaries, action items & decisions, no cloud. This page covers its npm package (@samuraizer/mcp-server).

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

Samuraizer scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.

### What tools does the Samuraizer MCP server expose?

Samuraizer exposes 9 tools: normalize_audio, transcribe_audio, summarize_transcript, extract_action_items, extract_decisions, and 4 more. Their descriptions and schemas cost roughly 488 tokens of context every time the server is loaded.

### Is the Samuraizer MCP server still maintained?

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

Samuraizer 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/@samuraizer/mcp-server
- Socket report: https://socket.dev/npm/package/@samuraizer/mcp-server
- Repository: https://github.com/UladzKha/samuraizer-cli
- Changelog RSS feed: https://verifymcp.io/servers/uladzkha-samuraizer/samuraizer-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/uladzkha-samuraizer/samuraizer-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/uladzkha-samuraizer/samuraizer-mcp-server