# Zovo Venn (remote · venn-diagram.zovo.one)

Compares 2 or 3 lists and draws a Venn diagram, with a CSV table of the region of each item.

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

## Components

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

## Channel facts

- Endpoint: `https://venn-diagram.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**: 74/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 817 tokens (~272/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 Venn MCP server?

Zovo Venn is a hosted endpoint at https://venn-diagram.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-venn-diagram 'https://venn-diagram.zovo.one/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  theluckystrike-venn-diagram:
    url: "https://venn-diagram.zovo.one/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "theluckystrike-venn-diagram": {
      "type": "http",
      "url": "https://venn-diagram.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-19 (score 79, +1)

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

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

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

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

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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)

### `make_venn` (~467 tokens)

Make Venn diagram

Use this when the user wants a Venn diagram of 2 or 3 lists or groups, for example "Venn diagram of these two customer lists" or "draw the overlap of skills for 3 candidates". Takes 2 or 3 named sets of items (up to 500 per set, 80 characters per item) or only region counts, a layout (symmetric, or proportional for 2 sets) and a case option. Returns the count of each region, which items are drawn, a check that each drawn label sits inside its region, an interactive diagram, and SVG, PDF and CSV downloads. Does not read files or images, and does not draw 4 or more sets. Lists are not kept after the call; download files of large diagrams are stored for 1 hour.

Input parameters:

- `case_sensitive` (boolean): false (default): "Apple" and "apple" are the same item. true: case matters.
- `layout` (string): symmetric (default): circles of equal size, areas not to scale. proportional: 2 sets only, both with at least one item, circle and overlap areas to scale with the counts.
- `region_counts` (object): Use when only the counts are known, not the items. Keys name one region each: 2 sets a, b, ab; 3 sets a, b, c, ab, ac, bc, abc (a = only the first set; ab = in the first and second set but not the th…
- `set_names` (array): Only with region_counts: the 2 or 3 set names in order a, b, c, e.g. ["Email","SMS"].
- `sets` (array): 2 or 3 named lists to compare. Each set: {"name":"Team A","items":["Ann","Bo","Cy"]}. Names up to 40 characters; up to 500 items per set, each up to 80 characters. Give this or set_names with region_…
- `title` (string): Diagram title, e.g. "Skills of two candidates". Up to 80 characters. Default: the set names joined with "vs".

Output parameters:

- `downloads` (object)
- `layout` (string)
- `mode` (string)
- `normalization` (string)
- `pdf` (object)
- `placement_check` (object)
- `preview_count` (object)
- `proportional` (object)
- `regions` (array)
- `set_count` (number)
- `sets` (array)
- `title` (string)
- `union_count` (number)
- `warnings` (array)

### `compare_lists` (~218 tokens)

Compare lists

Use this when the user wants to know which items 2 or 3 lists share and which are unique, without a diagram, for example "which names are on both lists" or "compare these three guest lists". Takes 2 or 3 named lists (up to 500 items each, 80 characters per item) and a case option. Returns each region (only A, only B, A and B, ...) with its count and items, the overlap percentage for each pair, and a CSV with each item's region. Does not read files, does not fuzzy-match spellings, and does not draw a diagram.

Input parameters:

- `case_sensitive` (boolean): false (default): "Apple" and "apple" are the same item. true: case matters.
- `sets` (array, required): 2 or 3 named lists to compare. Each set: {"name":"Team A","items":["Ann","Bo","Cy"]}. Names up to 40 characters; up to 500 items per set, each up to 80 characters.

Output parameters:

- `downloads` (object)
- `items_complete` (boolean)
- `normalization` (string)
- `pairs` (array)
- `regions` (array)
- `set_count` (number)
- `sets` (array)
- `union_count` (number)
- `warnings` (array)

## Diagnostics

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

## Score history

- 2026-11-21: 79
- 2026-11-20: 79
- 2026-11-19: 79
- 2026-11-18: 78
- 2026-11-17: 78
- 2026-11-16: 77
- 2026-11-15: 77
- 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 Venn MCP server?

Zovo Venn is an MCP server listed in the public MCP registry as io.github.theluckystrike/venn-diagram. Compares 2 or 3 lists and draws a Venn diagram, with a CSV table of the region of each item. This page covers its hosted endpoint (https://venn-diagram.zovo.one/mcp).

### Is the Zovo Venn MCP server safe to use?

Zovo Venn 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 Venn MCP server expose?

Zovo Venn exposes 2 tools: make_venn, compare_lists. Their descriptions and schemas cost roughly 685 tokens of context every time the server is loaded.

### Does the Zovo Venn MCP server require authentication?

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

### Is the Zovo Venn MCP server still maintained?

Zovo Venn 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 Venn MCP server?

VerifyMCP ran 14 checks on Zovo Venn, 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://venn-diagram.zovo.one/mcp
- Website: https://venn-diagram.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-venn-diagram/venn-diagram.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-venn-diagram/venn-diagram/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-venn-diagram/venn-diagram.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-venn-diagram/venn-diagram
