io.github.MUSE-CODE-SPACE/vibe-coding
NPM · VIBE-CODING-MCP
Auto-document vibe coding sessions - collect, summarize, and publish
Available components
Last scanned (1 hour ago)
Scores higher than 51% of npm servers
Category Developer Tools
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 45 of 140 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 121 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3193 tokens (~212/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "muse_publish_document" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 15 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 0
- Stability: 0.97 → pass security
- 4 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.
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 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/vibe-coding-mcp@2.12.1
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 140 packages
| Packages resolved | 140 |
|---|---|
| Stale | 45 |
| 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 →
muse_analyze_code ~149
Performs deep code analysis using AST parsing. Extracts functions, classes, imports, and generates Mermaid diagrams. Supports AI-powered analysis for quality insights, security issues, and improvement suggestions.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The source code to analyze |
| diagramTypes | array | – | Types of diagrams to generate (default: all) |
| filename | string | – | Optional filename for context |
| generateDiagrams | boolean | – | Generate Mermaid diagrams (default: true) |
| language | string | – | Programming language (auto-detected if not provided) |
| useAI | boolean | – | Enable AI-powered analysis for quality, security, and suggestions (default: false, requires ANTHROPIC_API_KEY) |
No output schema declared.
No examples provided.
muse_auto_tag ~244
Automatically suggests and applies tags to sessions. Actions: suggest (recommend tags), apply (add tags to session), train (learn from examples), config (configure tagging behavior).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| categories | array | – | Filter suggestions by category |
| codeBlocks | array | – | Code blocks to analyze |
| content | string | – | Text content to analyze for tags |
| customPatterns | array | – | Custom patterns for tag detection (for config) |
| defaultCategories | array | – | Default categories to use (for config) |
| enableAutoTag | boolean | – | Enable/disable auto-tagging (for config) |
| examples | array | – | Training examples for train action |
| includeExisting | boolean | – | Include existing tags when applying (default: true) |
| maxTags | number | – | Maximum number of tags to suggest (default: 5) |
| minConfidence | number | – | Minimum confidence threshold 0-1 (default: 0.7) |
| sessionId | string | – | Session ID to analyze or update (for suggest/apply) |
| useAI | boolean | – | Use AI for tag suggestions (default: false) |
No output schema declared.
No examples provided.
muse_batch ~202
Executes multiple tool operations in batch. Actions: execute (run batch), preview (plan without executing), status (check job status), cancel (stop running job), history (list past jobs). Supports sequential and parallel execution with dependency management.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| includeErrors | boolean | – | Include error details in response (default: true) |
| includeResults | boolean | – | Include operation results in response (default: true) |
| jobId | string | – | Job ID for status/cancel actions |
| limit | number | – | Limit for history action (default: 20) |
| mode | string | – | Execution mode (default: sequential) |
| operations | array | – | Array of operations to execute |
| status | string | – | Filter history by status |
| stopOnError | boolean | – | Stop batch on first error (default: true) |
| timeout | number | – | Timeout per operation in ms (default: 60000) |
No output schema declared.
No examples provided.
muse_collect_code_context ~153
Collects code blocks and conversation summaries into a structured context for documentation. Supports automatic language detection, duplicate removal, and statistics.
| Name | Type | Req | Description |
|---|---|---|---|
| autoDetectLanguage | boolean | – | Automatically detect programming language (default: true) |
| codeBlocks | array | – | Array of code blocks with language and code content |
| conversationSummary | string | yes | Summary of the conversation or context |
| includeStats | boolean | – | Include code statistics in output (default: true) |
| rawText | string | – | Raw text containing code blocks to extract (alternative to codeBlocks) |
| removeDuplicates | boolean | – | Remove duplicate code blocks (default: true) |
| tags | array | – | Optional tags for categorization (language tags auto-added) |
No output schema declared.
No examples provided.
muse_create_session_log ~101
Creates daily or session-based vibe coding session logs.
| Name | Type | Req | Description |
|---|---|---|---|
| codeContexts | array | – | Array of code contexts from the session |
| designDecisions | array | – | Array of design decisions made |
| duration | number | – | Session duration in seconds |
| options | object | – | – |
| summary | string | yes | Summary of what was accomplished |
| tags | array | – | Tags for the session |
| title | string | yes | Title of the session |
No output schema declared.
No examples provided.
muse_export_session ~224
Exports vibe coding sessions to various formats (Markdown, JSON, HTML). Use for creating shareable documentation, backups, or reports from session history.
| Name | Type | Req | Description |
|---|---|---|---|
| bundleMultiple | boolean | – | Combine multiple sessions into one document. Default: true |
| format | string | yes | Output format: markdown (readable docs), json (structured data), html (web page) |
| includeCodeBlocks | boolean | – | Include code blocks from code contexts. Default: true |
| includeDesignDecisions | boolean | – | Include design decisions. Default: true |
| includeMetadata | boolean | – | Include session metadata (ID, timestamps, tags). Default: true |
| outputPath | string | – | File path to save the export. If omitted, returns content directly. |
| sessionIds | array | – | Specific session IDs to export. If omitted, exports all sessions. |
| template | string | – | Template style: minimal (brief), default (balanced), detailed (comprehensive), report (formal) |
| title | string | – | Document title. Default: "Vibe Coding Session Export" |
No output schema declared.
No examples provided.
muse_generate_dev_document ~294
Generates README, DESIGN, TUTORIAL, or CHANGELOG documents in Markdown format. Supports multiple languages, badges, API reference, FAQ, and more.
| Name | Type | Req | Description |
|---|---|---|---|
| apiReference | array | – | API documentation |
| author | string | – | Author name |
| badges | array | – | Shield.io badges |
| codeContexts | array | – | Array of code contexts to include |
| contributors | array | – | List of contributors |
| customSections | object | – | Custom sections to add (key: section title, value: content) |
| description | string | – | Project or document description |
| designDecisions | array | – | Array of design decisions to include |
| documentType | string | yes | Type of document to generate (README, DESIGN, TUTORIAL, CHANGELOG, API, ARCHITECTURE) |
| faq | array | – | Frequently asked questions |
| features | array | – | List of features |
| includeTableOfContents | boolean | – | Whether to include a table of contents |
| installation | object | – | Installation instructions |
| language | string | – | Language for section headers (default: en) |
| license | string | – | License type (e.g., MIT, Apache-2.0) |
| projectName | string | – | Name of the project |
| repository | string | – | Repository URL |
| title | string | – | Title of the document |
| version | string | – | Version number |
No output schema declared.
No examples provided.
muse_git ~503
Git integration for vibe coding sessions. Get repository status, commit history, diffs, branch info. Capture git snapshots for sessions and extract design decisions from commit messages.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action: status (repo state), log (commit history), diff (changes), branch (branch info), snapshot (full context), extractDecisions (from commits), linkToSession (attach to session) |
| author | string | – | Filter commits by author name or email |
| contextLines | number | – | Lines of context around changes (default: 3) |
| diffType | string | – | Diff type: staged, unstaged, or all changes (default: all) |
| fromRef | string | – | Source commit/branch/tag for diff |
| grep | string | – | Search commit messages for keyword |
| includeDiff | boolean | – | Include current diff in snapshot (default: true) |
| includeLog | boolean | – | Include recent commits in snapshot (default: true) |
| includeRemote | boolean | – | Include remote branches (default: true) |
| includeStash | boolean | – | Include stash list in snapshot (default: false) |
| includeUntracked | boolean | – | Include untracked files in status (default: true) |
| language | string | – | Language for analysis (default: auto-detect) |
| limit | number | – | Max commits to return for log/extractDecisions (default: 20, max: 500) |
| logLimit | number | – | Commits to include in snapshot (default: 10) |
| oneline | boolean | – | Compact log format (default: false) |
| path | string | – | Filter by file or directory path |
| patterns | array | – | Custom regex patterns for detecting design decisions |
| repoPath | string | – | Path to git repository. Defaults to current working directory. |
| sessionId | string | – | Session ID to link git context to (required for linkToSession) |
| since | string | – | Filter commits after date (e.g., "2024-01-01", "1 week ago") |
| snapshotType | string | – | Detail level when linking to session (default: minimal) |
| stat | boolean | – | Include stat summary in diff (default: true) |
| toRef | string | – | Target commit/branch/tag for diff |
| until | string | – | Filter commits before date |
| verbose | boolean | – | Include last commit info per branch (default: false) |
No output schema declared.
No examples provided.
muse_normalize_for_platform ~77
Converts Markdown documents for Notion, GitHub Wiki, or Obsidian platforms. Handles links, images, code blocks, tables, frontmatter, and platform-specific syntax.
| Name | Type | Req | Description |
|---|---|---|---|
| document | string | yes | The Markdown document to normalize |
| options | object | – | – |
| platform | string | yes | Target platform for the document |
No output schema declared.
No examples provided.
muse_project_profile ~322
Manages project profiles for vibe coding sessions. Save project-specific settings for documentation, code analysis, and publishing.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action: create, get, update, delete, list, setActive, getActive, clone |
| codeAnalysis | object | – | Code analysis settings (defaultLanguage, defaultDiagramTypes, excludePatterns, useAI) |
| defaultTags | array | – | Default tags applied to all sessions |
| description | string | – | Profile description |
| documentation | object | – | Documentation settings (defaultDocType, language, author, license, includeTableOfContents) |
| limit | number | – | Max results for list (default: 50) |
| metadata | object | – | Custom metadata |
| name | string | – | Profile name (required for create, optional for get by name) |
| newName | string | – | New name for cloned profile (required for clone) |
| offset | number | – | Skip results for list (default: 0) |
| profileId | string | – | Profile ID (for get, update, delete, setActive, clone) |
| projectPath | string | – | Path to the project directory |
| publishing | object | – | Publishing settings (defaultPlatform, platformSettings, autoPublish) |
| repository | string | – | Git repository URL |
| sortBy | string | – | Sort field for list |
| sortOrder | string | – | Sort order for list |
| tagCategories | array | – | Tag categories for organization |
| team | object | – | Team information |
| version | string | – | Project version |
No output schema declared.
No examples provided.
muse_publish_document ~77
Publishes generated documents to external platforms (Notion, GitHub Wiki, Obsidian, Confluence, Slack, or Discord).
| Name | Type | Req | Description |
|---|---|---|---|
| document | string | yes | The document content to publish |
| options | object | – | – |
| platform | string | yes | Target platform for publishing |
| title | string | yes | Title of the document |
No output schema declared.
No examples provided.
muse_session_history ~303
Manages vibe coding session history. Save, retrieve, search, and manage past coding sessions with their code contexts and design decisions.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform: save (create new), get (retrieve by ID), update (modify existing), delete (remove), list (get all), search (find by keyword), stats (storage statistics) |
| codeContexts | array | – | Array of code context objects |
| designDecisions | array | – | Array of design decision objects |
| filterTags | array | – | Filter by tags (for list) |
| keyword | string | – | Search keyword (required for search action) |
| limit | number | – | Maximum results to return (for list/search, default: 50) |
| metadata | object | – | Additional metadata |
| offset | number | – | Number of results to skip (for list, default: 0) |
| searchIn | array | – | Fields to search in (for search, default: all) |
| sessionId | string | – | Session ID (required for get, update, delete actions) |
| sortBy | string | – | Sort field (for list, default: updatedAt) |
| sortOrder | string | – | Sort order (for list, default: desc) |
| summary | string | – | Session summary (required for save, optional for update) |
| tags | array | – | Tags for categorization |
| title | string | – | Session title (required for save, optional for update) |
No output schema declared.
No examples provided.
muse_session_stats ~174
Provides analytics and insights about coding sessions. Actions: overview (summary stats), languages (language breakdown), timeline (activity over time), tags (tag analysis), productivity (work patterns), trends (compare periods).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Type of statistics to retrieve |
| compareWith | string | – | Compare with previous period or average |
| format | string | – | Output format (default: summary) |
| includeInsights | boolean | – | Include AI-generated insights (default: true) |
| languages | array | – | Filter by specific languages |
| period | string | – | Time period for grouping (default: all) |
| since | string | – | Start date for filtering (ISO date or relative like "1 week ago") |
| tags | array | – | Filter by specific tags |
| until | string | – | End date for filtering |
No output schema declared.
No examples provided.
muse_summarize_design_decisions ~183
Extracts and analyzes key architectural and design decisions from conversation logs. Supports both English and Korean, with importance scoring and keyword extraction. Set useAI=true for Claude-powered enhanced analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| conversationLog | string | yes | The full conversation log text to analyze |
| extractRelatedCode | boolean | – | Extract related code blocks (default: true) |
| includeImportanceScore | boolean | – | Include importance scoring for each decision (default: true) |
| language | string | – | Language of the conversation (default: auto-detect) |
| maxDecisions | number | – | Maximum number of decisions to extract (default: 20) |
| projectContext | string | – | Optional context about the project for better categorization |
| useAI | boolean | – | Use Claude AI for enhanced analysis. Requires ANTHROPIC_API_KEY environment variable. (default: false) |
No output schema declared.
No examples provided.
muse_template ~187
Manages custom document templates with variable substitution. Actions: create, get, update, delete, list, apply (render with data), preview (render preview), import, export.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| content | string | – | Template content with {{variables}} |
| data | object | – | Variable values for apply/preview |
| description | string | – | Template description |
| filePath | string | – | File path for import/export |
| filterType | string | – | Filter list by type |
| format | string | – | Import/export format (default: json) |
| limit | number | – | Limit results for list |
| name | string | – | Template name |
| offset | number | – | Offset for list pagination |
| templateId | string | – | Template ID |
| type | string | – | Template type |
| variables | array | – | Template variables definition |
No output schema declared.
No examples provided.
How do I install the io.github.MUSE-CODE-SPACE/vibe-coding MCP server?
io.github.MUSE-CODE-SPACE/vibe-coding runs locally as an npm package, launched with npx -y vibe-coding-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 · vibe-coding-mcp
claude mcp add muse-code-space-vibe-coding -- npx -y vibe-coding-mcp
What is the io.github.MUSE-CODE-SPACE/vibe-coding MCP server?
io.github.MUSE-CODE-SPACE/vibe-coding is an MCP server listed in the public MCP registry as io.github.MUSE-CODE-SPACE/vibe-coding. Auto-document vibe coding sessions - collect, summarize, and publish. This page covers its npm package (vibe-coding-mcp).
Is the io.github.MUSE-CODE-SPACE/vibe-coding MCP server safe to use?
io.github.MUSE-CODE-SPACE/vibe-coding scores 75 out of 100 on VerifyMCP. We recorded 1 known advisory against 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 io.github.MUSE-CODE-SPACE/vibe-coding MCP server expose?
io.github.MUSE-CODE-SPACE/vibe-coding exposes 15 tools: muse_collect_code_context, muse_summarize_design_decisions, muse_generate_dev_document, muse_normalize_for_platform, muse_publish_document, and 10 more. Their descriptions and schemas cost roughly 3,193 tokens of context every time the server is loaded.
Is the io.github.MUSE-CODE-SPACE/vibe-coding MCP server still maintained?
io.github.MUSE-CODE-SPACE/vibe-coding 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 io.github.MUSE-CODE-SPACE/vibe-coding MCP server under?
io.github.MUSE-CODE-SPACE/vibe-coding declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.