mmm-mcp-server

MCPcommunity
v0.1.2UnknownMITUpdated 3d agonpmGitHub

Matryoshka Mind Map の自分のデータをClaudeから直接読み書きするMCPサーバー

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
500Downloads/wk
3d agoLast update
Package
AuthorUnknown
LicenseMIT
Version0.1.2
Sourcenpm+mcp-registry
npmmmm-mcp-server
GitHubnhorie-canal/mmm_mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface9 tools · 3 privileged
Security scan✓ Cleanv0.1.2 · todayHow well does this scan work?
EvalsNone
IndexedOct 3, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

9 tools · 3 privileged
Statically extracted from the published packagev0.1.2 · 14h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

auto_structure_thought会話中にClaudeが考えた階層構造を、既存のマップに追加する。深さは3階層固定ではなく任意。

会話中にClaudeが考えた階層構造を、既存のマップに追加する。深さは3階層固定ではなく任意。

No input schema was published for this tool.

create_map新しいマインドマップ(マップ)を1つ作成する。

新しいマインドマップ(マップ)を1つ作成する。

No input schema was published for this tool.

delete_elementsprivileged既存マップから要素を削除する。指定した要素とその配下(子孫)を丸ごと削除する。

既存マップから要素を削除する。指定した要素とその配下(子孫)を丸ごと削除する。

No input schema was published for this tool.

edit_elementprivileged既存マップの要素1件の本文(detail)を書き換える。要素の追加はauto_structure_thought・

既存マップの要素1件の本文(detail)を書き換える。要素の追加はauto_structure_thought・

No input schema was published for this tool.

import_markdown_context任意の深さのMarkdown(インデントで階層を表現したリスト、見出しは`#`)を組み立てて、

任意の深さのMarkdown(インデントで階層を表現したリスト、見出しは`#`)を組み立てて、

No input schema was published for this tool.

list_elements指定したマップ内の全要素と親子関係、チェック状態(checked)を返す。

指定したマップ内の全要素と親子関係、チェック状態(checked)を返す。

No input schema was published for this tool.

list_maps自分のMatryoshka Mind Mapの全マップ(タイトル・ID・TODOかどうか)を返す。

自分のMatryoshka Mind Mapの全マップ(タイトル・ID・TODOかどうか)を返す。

No input schema was published for this tool.

move_elementprivileged既存マップの要素1件(配下ごと)を、同じマップ内の別の場所へ移動する。

既存マップの要素1件(配下ごと)を、同じマップ内の別の場所へ移動する。

No input schema was published for this tool.

update_task_statusTODOマップの要素のチェック状態を書き換える。1件でも複数件でもよい。

TODOマップの要素のチェック状態を書き換える。1件でも複数件でもよい。

No input schema was published for this tool.

9 of 9 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Matryoshka Mind Map の自分のデータをClaudeから直接読み書きするMCPサーバー

Keywords
mcpmodel-context-protocolmindmaptodoclaudematryoshka
Alternatives
Comparing tool surfaces…

Tools exposed

9 tools · 3 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-03 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

66 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+54 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in notes & productivity