# io.github.GuangminJu/mellos-mapping (npm · mellos-mapping)

Live layered dependency map for bottom-up development, drawn by the agent in a terminal pane.

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-18

## Components

- npm · `mellos-mapping`: 68/100 (this document), [markdown](https://verifymcp.io/servers/guangminju-mellos-mapping/mellos-mapping.md), [page](https://verifymcp.io/servers/guangminju-mellos-mapping/mellos-mapping)

## Channel facts

- Registry: `npm`
- Package: `mellos-mapping`
- Version: `0.19.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-08-18.

- **Supply Chain Security**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **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 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 997 tokens (~199/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 63% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add guangminju-mellos-mapping -- npx -y mellos-mapping
```

### Codex

```bash
codex mcp add guangminju-mellos-mapping -- npx -y mellos-mapping
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add guangminju-mellos-mapping --command npx --arg -y --arg mellos-mapping
```

### Hermes

```yaml
mcp_servers:
  guangminju-mellos-mapping:
    command: "npx"
    args: ["-y", "mellos-mapping"]
```

### Other

```json
{
  "mcpServers": {
    "guangminju-mellos-mapping": {
      "command": "npx",
      "args": [
        "-y",
        "mellos-mapping"
      ]
    }
  }
}
```

## 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-08-18 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-16 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-15 (score 66, +12)

- [security regression] Stability: 0.03 → unverified
- [security improvement] Known CVEs: unverified → pass
- [functional regression] Schema quality: 846 → 997
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Dependency health: unverified → pass
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.18.0 → 0.19.0

### 2026-08-14 (score 54, 0)

- [security regression] Malware scan: pass → unverified
- [security improvement] Known CVEs: unverified → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Dependency health: unverified → pass
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.14.0 → 0.18.0
- [functional] Package version: 0.14.0 → 0.17.0
- [functional] Package version: 0.14.0 → 0.16.0
- [functional] Package version: 0.14.0 → 0.15.0

### 2026-08-13 (score 54)

First indexed and scored.

## MCP tools (5)

### `mmap_declare` (~390 tokens)

Declare map structure

Grow the Mellos map: set the title and diagram kind, add layer bands, lanes and groups (labeled subsystems within ONE band — declare them when a single band grows crowded, roughly five or more nodes in that band; a group must be a strict subset of its band, and a map spread thin across many bands needs none), add nodes, add dependency edges. Declare the whole ghost design up front, then grow it as understanding deepens. Edges must point strictly downward (a node may only use nodes on lower layers); the batch is all-or-nothing.

Input parameters:

- `edges` (array)
- `groups` (array)
- `kind` (string): diagram kind. dev (default) = the live progress ledger with status skins. The rest are documentation diagrams rendered neutrally: architecture (layered components; also fits call graphs and module de…
- `lanes` (array): vertical columns crossing all bands; declaration order = left-to-right
- `layers` (array)
- `nodes` (array)
- `page` (string): page (parallel map) this call targets; omit for the default page. One effort = one page: start a NEW effort on its own page named after the effort, so concurrent sessions never write over each other…
- `title` (string): map title, e.g. the feature being built

### `mmap_update` (~123 tokens)

Record progress on nodes

Update node status/label/evidence. Set in-progress when starting a node (the pane spins), done with evidence when its verification passes, regressed with evidence when a done node breaks. The map is a ledger: report honestly, it never blocks you.

Input parameters:

- `page` (string): page (parallel map) this call targets; omit for the default page. One effort = one page: start a NEW effort on its own page named after the effort, so concurrent sessions never write over each other…
- `updates` (array, required)

### `mmap_remove` (~193 tokens)

Revise the map

Remove edges, nodes, groups and empty layer bands (in that order, all-or-nothing). Removing a node also removes every edge touching it; removing a group merely ungroups its members. Use when the ghost design turns out wrong — the map is a hypothesis, revising it is honest work.

Input parameters:

- `edges` (array)
- `groups` (array): groups to remove; members stay, merely ungrouped
- `lanes` (array): lanes to remove; members stay, merely off-lane
- `layers` (array): bands to remove; must be empty of nodes and groups
- `nodes` (array)
- `page` (string): page (parallel map) this call targets; omit for the default page. One effort = one page: start a NEW effort on its own page named after the effort, so concurrent sessions never write over each other…

### `mmap_setup` (~151 tokens)

Configure when maps open

Get or set this project's mapping policy — WHEN the assistant opens a Mellos map. Call with no arguments to read it. If it reports "not set", ask the USER to choose (never pick for them): always = map every structured task — workflows, designs, architecture, technical dependencies; complex = map only medium or complex tasks — several modules, a new subsystem, roughly an hour or more; on-request = map only when the user explicitly asks. Then call again with their choice to persist it. The policy guides you; it never blocks the tools, and an explicit user request for a map always wins.

Input parameters:

- `policy` (string): the user's choice to persist; omit to read the current policy

### `mmap_view` (~140 tokens)

View the current map

Render the current Mellos map as monochrome text — the same picture the split-pane watcher shows live. Use it to check the map state or to show it inline in conversation.

Input parameters:

- `page` (string): page (parallel map) this call targets; omit for the default page. One effort = one page: start a NEW effort on its own page named after the effort, so concurrent sessions never write over each other…
- `zoom` (integer): zoom ladder: 1 = detail (notes unfold), 0 = standard (default), -1..-3 = scaled down, -4 = overview glyphs

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/guangminju-mellos-mapping/mellos-mapping#diagnostics

## Score history

- 2026-08-18: 68
- 2026-08-17: 67
- 2026-08-16: 67
- 2026-08-15: 66
- 2026-08-14: 54
- 2026-08-13: 54

## Links

- npm package: https://www.npmjs.com/package/mellos-mapping
- Socket report: https://socket.dev/npm/package/mellos-mapping
- Repository: https://github.com/GuangminJu/mellos-mapping
- Changelog RSS feed: https://verifymcp.io/servers/guangminju-mellos-mapping/mellos-mapping.xml
- Changelog JSON feed: https://verifymcp.io/servers/guangminju-mellos-mapping/mellos-mapping.json
- HTML version of this page: https://verifymcp.io/servers/guangminju-mellos-mapping/mellos-mapping