Samuraizer
NPM · @SAMURAIZER/MCP-SERVER
Local MCP server for meeting transcripts, summaries, action items & decisions — no cloud.
Available components
Last scanned (6 hours ago)
Scores higher than 87% of npm servers
Category Productivity and Notes
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
- 40 of 113 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 58 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 529 tokens (~58/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
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.
- 5 Nov 26 +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.
- 4 Nov 26 −1
- Stability: pass → 0.93 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 21 Oct 26 +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.
- 20 Oct 26 −1
- Stability: pass → 0.93 functional
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 5 Nov 2026 · Analysed npm/@samuraizer/mcp-server@0.1.7
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 113 packages
| Packages resolved | 113 |
|---|---|
| Stale | 40 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
extract_action_items Extract Action Items ~54
Extract action items from a meeting transcript. Returns a JSON list of tasks with owner and due date.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | Ollama model to use (optional) |
| transcriptText | string | yes | Full transcript text |
No output schema declared.
No examples provided.
extract_decisions Extract Decisions ~49
Extract confirmed decisions from a meeting transcript. Returns a JSON list of decisions.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | Ollama model to use (optional) |
| transcriptText | string | yes | Full transcript text |
No output schema declared.
No examples provided.
get_meeting ~34
Retrieve the full processed output for a specific meeting by id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The meeting id (ULID). |
No output schema declared.
No examples provided.
list_meetings ~37
List all processed meetings, sorted newest first. Optionally limit results.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of meetings to return. |
No output schema declared.
No examples provided.
normalize_audio Normalize Audio ~55
Normalize an audio file to 16kHz mono PCM WAV format required by Whisper.
| Name | Type | Req | Description |
|---|---|---|---|
| inputPath | string | yes | Absolute path to the source audio file |
| outputPath | string | yes | Absolute path for the output WAV file |
No output schema declared.
No examples provided.
process_recording Process Recording ~62
Run the full Samuraizer pipeline on an audio file. Returns summary, action items, decisions, and output file paths.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Absolute path to the audio file |
| model | string | – | Ollama model to use (optional) |
No output schema declared.
No examples provided.
search_meetings ~115
Search meetings by summary text, name, action items, and decisions. Transcripts are not searched — use get_meeting for those. Returns ranked results with snippets.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum results to return (default 10). |
| query | string | yes | 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… |
No output schema declared.
No examples provided.
summarize_transcript Summarize Transcript ~45
Generate a concise meeting summary from transcript text.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | Ollama model to use (optional) |
| transcriptText | string | yes | Full transcript text to summarize |
No output schema declared.
No examples provided.
transcribe_audio Transcribe Audio ~37
Transcribe an audio file using whisper.cpp. Returns the transcript text.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Absolute path to the audio file |
No output schema declared.
No examples provided.
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.
npm · @samuraizer/mcp-server
claude mcp add uladzkha-samuraizer -- npx -y @samuraizer/mcp-server
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 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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.
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 5 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 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.