# Zovo Mind Map (remote · mind-map.zovo.one)

Turns an outline or a plan into a clean mind map you can print or download.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mind-map.zovo.one`: 79/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-mind-map/mind-map.md), [page](https://verifymcp.io/servers/theluckystrike-mind-map/mind-map)

## Channel facts

- Endpoint: `https://mind-map.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 766 tokens (~255/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo Mind Map MCP server?

Zovo Mind Map is a hosted endpoint at https://mind-map.zovo.one/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http theluckystrike-mind-map 'https://mind-map.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-mind-map": {
      "url": "https://mind-map.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-mind-map": {
      "type": "http",
      "url": "https://mind-map.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-mind-map]
url = "https://mind-map.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-mind-map": {
      "type": "remote",
      "url": "https://mind-map.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-mind-map --url 'https://mind-map.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-mind-map:
    url: "https://mind-map.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-mind-map": {
      "Transport": "http",
      "Url": "https://mind-map.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-mind-map -t streamable-http -u 'https://mind-map.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-mind-map": {
      "type": "http",
      "url": "https://mind-map.zovo.one/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-20 (score 79, +1)

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

### 2026-11-18 (score 78, +1)

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

### 2026-11-16 (score 77, +1)

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

### 2026-11-13 (score 76, +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-11-11 (score 75, +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-11-09 (score 74, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 73)

First indexed and scored.

## MCP tools (2)

### `generate_mind_map` (~457 tokens)

Generate mind map

Use this when the user wants a mind map, concept map, brainstorm map or topic tree drawn from an outline or a list of topics and subtopics, for example "turn these notes into a mind map" or "mind map of our launch plan". Takes an indented outline (2 spaces or 1 tab per level) or nested nodes, up to 300 topics and 6 levels, plus a layout (balanced, right-tree or org-down), a colour theme and a PDF page size. Returns the topic count, depth, main branches, an interactive map, and SVG, PDF and OPML downloads. Refuses mixed indentation and skipped levels with the line number. Does not draw flowcharts with decisions, timelines, images or links between branches, and does not save maps.

Input parameters:

- `layout` (string): balanced (default): main branches split to the left and right of the centre topic; right-tree: everything grows to the right; org-down: a top-down hierarchy like an org chart.
- `nodes` (array): Alternative to outline_text. Nested topics: [{"text":"Goals","children":[{"text":"Revenue"},{"text":"Hiring"}]}]. Each node has text (up to 120 characters) and optional children. Up to 300 nodes and…
- `outline_text` (string): Indented outline, one topic per line, 2 spaces (or 1 tab) per level, optional "-" bullets, e.g. "Marketing\n  - Social\n  - Email\nSales\n  - Partners". Up to 300 lines and 6 levels. Give this or nod…
- `page_size` (string): PDF page: auto (default, the page fits the map at full size), letter or a4 (the map is scaled to fit one page, landscape or portrait).
- `theme` (string): Colour theme, e.g. classic (default, a colour per branch), ocean (blues), forest (greens and browns) or mono (grey, prints well in black and white).
- `title` (string): Centre topic of the map, e.g. "Product launch". If omitted and the outline has one top line, that line becomes the centre.

Output parameters:

- `branches` (array)
- `downloads` (object)
- `layout` (string)
- `layout_check` (object)
- `leaf_count` (number)
- `max_depth` (number)
- `node_count` (number)
- `outline` (string)
- `page_size` (string)
- `pdf` (object)
- `preview_count` (object)
- `size_pt` (object)
- `theme` (string)
- `title` (string)
- `warnings` (array)

### `outline_from_mind_map` (~215 tokens)

Outline from mind map

Use this when the user wants a mind map turned back into a text outline, for example "give me this mind map as an outline" or "export the map as Markdown bullets". Takes the centre topic and nested nodes ({text, children}), up to 300 topics and 6 levels. Returns an indented or Markdown outline that generate_mind_map accepts again, the topic count and depth, and outline and OPML downloads. Does not read images of mind maps or files from other apps.

Input parameters:

- `format` (string): indented (default): 2 spaces per level; markdown: "- " bullets with 2 spaces per level.
- `nodes` (array, required): The map's topics below the centre. Nested topics: [{"text":"Goals","children":[{"text":"Revenue"},{"text":"Hiring"}]}]. Each node has text (up to 120 characters) and optional children.
- `title` (string): Centre topic, e.g. "Product launch". Written as the first line of the outline.

Output parameters:

- `downloads` (object)
- `format` (string)
- `line_count` (number)
- `max_depth` (number)
- `node_count` (number)
- `outline` (string)
- `outline_complete` (boolean)
- `title` (string)
- `warnings` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-mind-map/mind-map#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 79
- 2026-11-19: 78
- 2026-11-18: 78
- 2026-11-17: 77
- 2026-11-16: 77
- 2026-11-15: 76
- 2026-11-14: 76
- 2026-11-13: 76
- 2026-11-12: 75
- 2026-11-11: 75
- 2026-11-10: 74
- 2026-11-09: 74
- 2026-11-08: 73

## Common questions

### What is the Zovo Mind Map MCP server?

Zovo Mind Map is an MCP server listed in the public MCP registry as io.github.theluckystrike/mind-map. Turns an outline or a plan into a clean mind map you can print or download. This page covers its hosted endpoint (https://mind-map.zovo.one/mcp).

### Is the Zovo Mind Map MCP server safe to use?

Zovo Mind Map scores 79 out of 100 on VerifyMCP. 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 Zovo Mind Map MCP server expose?

Zovo Mind Map exposes 2 tools: generate_mind_map, outline_from_mind_map. Their descriptions and schemas cost roughly 672 tokens of context every time the server is loaded.

### Does the Zovo Mind Map MCP server require authentication?

No. We connected to Zovo Mind Map without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zovo Mind Map MCP server still maintained?

Zovo Mind Map 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 did VerifyMCP test on the Zovo Mind Map MCP server?

VerifyMCP ran 14 checks on Zovo Mind Map, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mind-map.zovo.one/mcp
- Website: https://mind-map.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-mind-map/mind-map.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-mind-map/mind-map/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-mind-map/mind-map.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-mind-map/mind-map
