app.cloudmindmaps/mindmaps
NPM · CLOUDMINDMAPS-MCP
Create and read mind maps on CloudMindMaps from Claude and other AI assistants.
Available components
Last scanned (19 hours ago)
Scores higher than 51% of npm servers
Category Productivity and Notes
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. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 136 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 593 tokens (~148/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 0
- Stability: 0.97 → pass security
- 20 Nov 26 0
- Stability: pass → 0.97 functional
- 14 Nov 26 0
- Stability: 0.97 → pass security
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 −1
- Stability: pass → 0.93 functional
- 6 Nov 26 0
- Stability: 0.97 → pass security
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 −1
- Stability: pass → 0.93 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/cloudmindmaps-mcp@1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_mindmap Create mind map from raw .mm XML ~279
Create a mind map on CloudMindMaps from raw CloudMindMaps XML (.mm format). Prefer create_mindmap_from_outline unless you specifically need XML features not exposed by the outline (clouds, edge styling, arrowlink connectors, richcontent HTML nodes). Minimal XML shape: <map version="1.0.0"> <node ID="ID_0" TEXT="Root Topic"> <node ID="ID_1" TEXT="Branch A" POSITION="right"> <node ID="ID_2" TEXT="Detail"/> </node> <node ID="ID_3" TEXT="Branch B" POSITION="left"/> </node> </map> Rules: - Exactly one root <node> inside <map>. Root has no POSITION. - Only the root's direct children take POSITION="left" or "right". - Every node needs a unique ID (ID_0, ID_1, ...). - Escape XML entities in TEXT (& < > " '). - Optional sub-elements: <font>, <edge>, <icon BUILTIN="...">, <cloud>, <richcontent>, <arrowlink>.
| Name | Type | Req | Description |
|---|---|---|---|
| title | string | yes | Title of the mind map. |
| xml | string | yes | Valid CloudMindMaps .mm XML content. |
No output schema declared.
No examples provided.
create_mindmap_from_outline Create mind map from an outline ~246
Create a mind map on CloudMindMaps from a simple nested outline. THIS IS THE RECOMMENDED WAY to create maps — you provide the structure as nested objects and the server generates valid .mm XML for you (correct IDs, balanced left/right branches, XML escaping). Use this whenever you're turning notes, documents, ideas, or a plan into a mind map. Provide 'root' as the central topic with nested 'children'. Guidelines for a readable map: - Give the root a short, punchy central topic. - Aim for 2-6 top-level branches; the server auto-balances them left and right. - Keep it 3-4 levels deep. Split further rather than writing long node text. - Use 'icon' sparingly for emphasis (e.g. "idea", "warning", "yes"), and 'note' for detail that shouldn't clutter the node label. Returns the map's shareable URL on cloudmindmaps.app.
| Name | Type | Req | Description |
|---|---|---|---|
| root | object | yes | The central topic node, with nested children forming the map. |
| title | string | yes | Title of the mind map (used for the file/name, not shown as a node). |
No output schema declared.
No examples provided.
get_mindmap Get a mind map's content ~42
Fetch the full details and .mm XML content of a mind map by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The mind map ID (16-character string). |
No output schema declared.
No examples provided.
list_mindmaps List my mind maps ~26
List all mind maps owned by or shared with the authenticated CloudMindMaps user.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the app.cloudmindmaps/mindmaps MCP server?
app.cloudmindmaps/mindmaps runs locally as an npm package, launched with npx -y cloudmindmaps-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · cloudmindmaps-mcp
claude mcp add app-cloudmindmaps-mindmaps -- npx -y cloudmindmaps-mcp
What is the app.cloudmindmaps/mindmaps MCP server?
app.cloudmindmaps/mindmaps is an MCP server listed in the public MCP registry as app.cloudmindmaps/mindmaps. Create and read mind maps on CloudMindMaps from Claude and other AI assistants. This page covers its npm package (cloudmindmaps-mcp).
Is the app.cloudmindmaps/mindmaps MCP server safe to use?
app.cloudmindmaps/mindmaps scores 75 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 tools does the app.cloudmindmaps/mindmaps MCP server expose?
app.cloudmindmaps/mindmaps exposes 4 tools: create_mindmap_from_outline, create_mindmap, list_mindmaps, get_mindmap. Their descriptions and schemas cost roughly 593 tokens of context every time the server is loaded.
Is the app.cloudmindmaps/mindmaps MCP server still maintained?
app.cloudmindmaps/mindmaps is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the app.cloudmindmaps/mindmaps MCP server under?
app.cloudmindmaps/mindmaps 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 app.cloudmindmaps/mindmaps MCP server?
VerifyMCP ran 15 checks on app.cloudmindmaps/mindmaps, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about app.cloudmindmaps/mindmaps: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.