2 findingsStatic scanned
Adds Storybook component and story documentation tools to an MCP server you run yourself.
9.4M installs/moMIT
Mellos Mapping
me1los · MCP server
Mellos Mapping gives your coding agent a persistent dependency map of the project it is building, with layers that grow from the bottom up. The agent first declares the whole intended structure as dashed ghost nodes, which you can veto while it is still only a picture, then updates each node as work proceeds. A node turns solid green only with evidence such as a passing test run, and turns red if later work cracks it. An MCP server lets the agent declare, update and read the map, and a terminal pane shows it live.
Written by ooruby from the README of mellos-mapping 0.27.1.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
A task list hides what depends on what; the map shows what stands on what, and which parts have been verified.
What you could do with it
- Have your agent ghost out the full design of a feature first, then veto parts you do not want before any code exists.
- Open the map pane in a terminal to see which node your agent is working on right now.
- Review which nodes are verified with evidence and which have regressed after later changes.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- node child_process (scripts/codex-cli.mjs:2)
- synchronous shell execution (scripts/codex-cli.mjs:33)
- node child_process (scripts/install-mmap-command.mjs:39)
- synchronous shell execution (scripts/install-mmap-command.mjs:167)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
A live layered dependency map for bottom-up development — MCP server + terminal pane. Ghost the design first, then light nodes up from the bottom as they are built and verified.
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.27.1, the file with digest sha512-cuAF61TE/AMG+VLkXtzvtKItDszTGOhEHZ36Fvg5RqOYMo+VEpbdId0i3q8axTfubLfGWzWG9byXKY7kMhoyog==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Paste this into your client's MCP configuration.
{
"mcpServers": {
"mmap": {
"command": "npx",
"args": [
"-y",
"-p",
"mellos-mapping@0.27.1",
"mmap"
]
}
}
}Or run it directly.
npx -y -p mellos-mapping@0.27.1 mmapPinned to 0.27.1, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- mellos-mapping
- Version read
- 0.27.1
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/guangminju/mellos-mapping
- Commit
- 1fe8b5ce42f3
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/mellos-mapping)About this listing
- Kind
- MCP server
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-06
Similar MCP servers
All MCP serversVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.