# VibeDNA Journal (mcpb · vibedna-journal-mcp-1.0.3.mcpb)

One journal file per project that your AI reads at session start and updates as it works.

- Trust score: 14/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `vibedna-journal-mcp-1.0.3.mcpb`: 14/100 (this document), [markdown](https://verifymcp.io/servers/marstudio360-vibedna-journal-mcp/vibedna-journal-mcp.md), [page](https://verifymcp.io/servers/marstudio360-vibedna-journal-mcp/vibedna-journal-mcp)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/marstudio360/vibedna-journal-mcp/releases/download/v1.0.3/vibedna-journal-mcp-1.0.3.mcpb`
- Version: `1.0.3`
- Transport: `stdio`
- SHA-256: `d2a3785fa1706891c97143b0d33bd43ac71f466bfe49ba75fe916087084d8829`

## 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-05.

- **Supply Chain Security**: 13/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs were checked across the 28 of 28 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - Install-script risk not yet assessed.
  - 0 of 28 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/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 29 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox has not given us the schema these checks need 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 the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### How do I install the VibeDNA Journal MCP server?

VibeDNA Journal ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, d2a3785fa1706891c97143b0d33bd43ac71f466bfe49ba75fe916087084d8829; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/marstudio360/vibedna-journal-mcp/releases/download/v1.0.3/vibedna-journal-mcp-1.0.3.mcpb`
- SHA-256: `d2a3785fa1706891c97143b0d33bd43ac71f466bfe49ba75fe916087084d8829`

### Verify on macOS / Linux

```bash
echo "d2a3785fa1706891c97143b0d33bd43ac71f466bfe49ba75fe916087084d8829  vibedna-journal-mcp-1.0.3.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\vibedna-journal-mcp-1.0.3.mcpb).Hash -eq "d2a3785fa1706891c97143b0d33bd43ac71f466bfe49ba75fe916087084d8829"
```

## 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 14, +2)

- [functional improvement] Maintenance: unverified → pass

### 2026-10-30 (score 12, −2)

- [functional regression] Maintenance: pass → unverified

### 2026-10-13 (score 14, 0)

- [security] Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- [security] Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- [functional] Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- [functional] Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.
- [functional] Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.

### 2026-10-08 (score 14)

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, Dependencies. The full working is on the page: https://verifymcp.io/servers/marstudio360-vibedna-journal-mcp/vibedna-journal-mcp#diagnostics

## Score history

- 2026-11-05: 14
- 2026-11-04: 14
- 2026-11-03: 14
- 2026-11-02: 14
- 2026-11-01: 14
- 2026-10-31: 12
- 2026-10-30: 12
- 2026-10-29: 14
- 2026-10-28: 14
- 2026-10-27: 14
- 2026-10-26: 14
- 2026-10-25: 14
- 2026-10-24: 14
- 2026-10-23: 14
- 2026-10-22: 14
- 2026-10-21: 14
- 2026-10-20: 14
- 2026-10-19: 14
- 2026-10-18: 14
- 2026-10-17: 14
- 2026-10-16: 14
- 2026-10-15: 14
- 2026-10-14: 14
- 2026-10-13: 14
- 2026-10-12: 14
- 2026-10-10: 14
- 2026-10-08: 14

## Common questions

### What is the VibeDNA Journal MCP server?

VibeDNA Journal is an MCP server listed in the public MCP registry as io.github.marstudio360/vibedna-journal-mcp. One journal file per project that your AI reads at session start and updates as it works. This page covers its MCPB bundle (https://github.com/marstudio360/vibedna-journal-mcp/releases/download/v1.0.3/vibedna-journal-mcp-1.0.3.mcpb).

### Is the VibeDNA Journal MCP server safe to use?

VibeDNA Journal scores 14 out of 100 on VerifyMCP. 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 licence is the VibeDNA Journal MCP server under?

VibeDNA Journal declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the VibeDNA Journal MCP server?

VerifyMCP ran 7 checks on VibeDNA Journal, covering Known CVEs, Dependency health, Source repository, Provenance and 3 more. 7 items could not be completed, a gap on our side rather than a finding about VibeDNA Journal: Malware scan, Install scripts, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/marstudio360/vibedna-journal-mcp
- Website: https://vibedna.ai/store/journal
- Changelog RSS feed: https://verifymcp.io/servers/marstudio360-vibedna-journal-mcp/vibedna-journal-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/marstudio360-vibedna-journal-mcp/vibedna-journal-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/marstudio360-vibedna-journal-mcp/vibedna-journal-mcp.json
- HTML version of this page: https://verifymcp.io/servers/marstudio360-vibedna-journal-mcp/vibedna-journal-mcp