io.github.GuangminJu/mellos-mapping
io-github-guangminju-mellos-mapping declares 8 capabilities across 8 tools, with 2 critical issues.
Issues
8 of 8 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
1 tool is classified as irreversible and declares no limit.
8 of 8 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
8 of 8 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
4 tools can modify data and declare no limit.
3 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
mmap_declare | write |
assumed |
mmap_update | write |
inferred |
mmap_read | read |
inferred |
mmap_batch | write |
assumed |
mmap_remove | delete |
inferred |
mmap_setup | read |
inferred |
mmap_view | read |
inferred |
mmap_open | write |
assumed |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-12 | 39 | tools/list answered by the npm package mellos-mapping@0.27.1 (published to npm as mellos-mapping, listed in the official MCP registry as io.github.GuangminJu/mellos-mapping 0.27.1), run in an isolated container with no network access and no credentials |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.