# Zovo Genogram (remote · genogram.zovo.one)

Turns a list of people and relationships into a genogram with the standard symbols.

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

## Components

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

## Channel facts

- Endpoint: `https://genogram.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**: 70/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 1055 tokens (~351/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 Genogram MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

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

### 2026-11-19 (score 78, +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 77, +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 76, +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 75, +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-10 (score 74, +1)

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

### 2026-11-09 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (2)

### `make_genogram` (~577 tokens)

Make genogram

Use this when the user wants a genogram or family diagram with standard symbols drawn from people and their relationships, for example "draw a genogram of my family" or "make a three-generation genogram for my social work class". Takes people (id, name, sex, birth and death years, deceased, index person; no label or notes), relations (couple: married, divorced, separated, cohabiting, engaged; parent_child: biological, adopted, foster; twins: identical, fraternal; emotional: close, distant, conflict, cut_off, hostile), an optional household, a title and a page size. Returns counts, each person's generation number, a geometry check (overlapping symbols or names, family lines through a name), the legend of symbols used, an interactive chart, and PDF, SVG, people CSV and relationships CSV downloads. An emotional relationship is drawn as a line only between two people next to each other in the same row; all others, including any between a parent and a child, are listed in a "Relationships not drawn" table and are not in the legend. Refuses unknown ids, parent cycles, more than 2 biological parents and impossible years, naming the problem. Up to 150 people, 12 generations and 100 emotional relationships. Relationships only: does not take health or medical details. Download links of large charts expire after about 1 hour.

Input parameters:

- `household` (array): Ids of the people who live together; drawn with a dashed outline, e.g. ["p2","p3"].
- `page_size` (string): PDF page: letter (default), a4, tabloid, a3 or a2. One page when the whole chart fits with text of at least 6 pt; else the chart prints in overlapping parts at full size.
- `people` (array, required): The people, up to 150. Example: [{"id":"p1","name":"Jan","sex":"M","birth_year":1950},{"id":"p2","name":"Ewa","sex":"F","birth_year":1952},{"id":"p3","name":"Ola","sex":"F","birth_year":1980,"index":…
- `relations` (array): The relationships, up to 600 (at most 150 couples and 100 emotional). Example: [{"type":"couple","a":"p1","b":"p2","kind":"married","start_year":1975},{"type":"parent_child","a":"p1","b":"p3"},{"type…
- `title` (string): Title printed on the chart and used in file names, up to 80 characters, e.g. "Kowalski family".

Output parameters:

- `checks` (object)
- `counts` (object)
- `downloads` (object)
- `generation_rule` (string)
- `legend` (array)
- `pdf` (object)
- `people` (array)
- `shown` (object)
- `title` (string)
- `warnings` (array)

### `check_genogram` (~361 tokens)

Check genogram data

Use this when the user wants a family list checked before drawing a genogram, for example "check my genogram data for mistakes" or "which generation is each person in". Takes the same people, relations and household as make_genogram. Returns the problems found (unknown or duplicate ids, a person who is their own ancestor with the cycle named, more than 2 biological parents, a parent who is not older than the child, couple years outside a partner's life, twins with different parents, too many generations; above 150 people it checks the first 150 and names the people left out), warnings, and each person's generation number when the data is consistent. Draws nothing and makes no files. Relationships only: it does not take health or medical details.

Input parameters:

- `household` (array): Ids of the people who live together; drawn with a dashed outline, e.g. ["p2","p3"].
- `people` (array, required): The people, up to 150. Example: [{"id":"p1","name":"Jan","sex":"M","birth_year":1950},{"id":"p2","name":"Ewa","sex":"F","birth_year":1952},{"id":"p3","name":"Ola","sex":"F","birth_year":1980,"index":…
- `relations` (array): The relationships, up to 600 (at most 150 couples and 100 emotional). Example: [{"type":"couple","a":"p1","b":"p2","kind":"married","start_year":1975},{"type":"parent_child","a":"p1","b":"p3"},{"type…

Output parameters:

- `counts` (object)
- `generation_rule` (string)
- `issues` (array)
- `limits` (object)
- `people` (array)
- `people_left_out` (array)
- `people_left_out_count` (number)
- `ready` (boolean)
- `shown` (object)

## Diagnostics

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

## Score history

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

## Common questions

### What is the Zovo Genogram MCP server?

Zovo Genogram is an MCP server listed in the public MCP registry as io.github.theluckystrike/genogram. Turns a list of people and relationships into a genogram with the standard symbols. This page covers its hosted endpoint (https://genogram.zovo.one/mcp).

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

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

Zovo Genogram exposes 2 tools: make_genogram, check_genogram. Their descriptions and schemas cost roughly 938 tokens of context every time the server is loaded.

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

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

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

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

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