# Zovo State Diagram (remote · state-diagram.zovo.one)

Turn a few lines of text into a UML state machine diagram document, and check the machine.

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

## Components

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

## Channel facts

- Endpoint: `https://state-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**: 72/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 1049 tokens (~349/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 State Diagram MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "theluckystrike-state-diagram": {
      "type": "http",
      "url": "https://state-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-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-14 (score 76, +1)

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

### 2026-11-12 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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
- [cosmetic] “check_state_diagram” reworded the description of “diagram”
- [cosmetic] “make_state_diagram” reworded the description of “diagram”

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

First indexed and scored.

## MCP tools (2)

### `make_state_diagram` (~483 tokens)

Make state diagram

Use this when the user wants a UML state diagram or state machine drawn, for example "draw the states of an order" or "make a PDF of this state machine". Takes the diagram text in a line grammar: state Name / state "Long label" as Name / state Name <<choice>> / state Name { ... } (composite, nest up to 3); [*] -> A (start), A -> [*] (end); A -> B: event [guard] / action; A -> A: event (self); note A: text; # comments. When the user describes the machine in words, write it in this grammar first. Returns counts, states, transitions in input order, the machine check (unreachable states, states with no path to the end, non-deterministic transitions), a check on the drawing, the PDF page count, an interactive diagram, and PDF, SVG and CSV downloads. Refuses a line outside the grammar with its line number and token. Up to 80 states and 300 transitions. Does not read fork, join, history or concurrent regions. Download links of large diagrams expire after about 1 hour.

Input parameters:

- `diagram` (string, required): The state machine in this line grammar, one statement per line, up to 40,000 characters: state Name | state "Long label" as Name | state Name <<choice>> | state Name { ... } (composite, nest up to 3)…
- `page_size` (string): PDF paper, portrait: letter (default) or a4. Example: a4.
- `title` (string): Title printed on the diagram and used in file names, up to 80 characters, e.g. "Order lifecycle".

Output parameters:

- `analysis` (object)
- `counts` (object)
- `downloads` (object)
- `layout_check` (object)
- `pdf` (object)
- `shown` (object)
- `states` (array)
- `title` (string)
- `transitions` (array)
- `warnings` (array)

### `check_state_diagram` (~333 tokens)

Check state diagram text

Use this when the user wants state machine text checked without a drawing, for example "which states are unreachable?" or "check my state diagram for dead ends". Takes the same diagram text as make_state_diagram. Returns ready true or false; when a line breaks the grammar, the line number, the token and the reason; otherwise the states with incoming and outgoing transition counts, states not reachable from the start, states with no path to the end (both by breadth-first search; a composite state is entered through its own start), and transitions that leave the same state on the same event and guard. Does not draw the diagram or make files, and does not read fork, join, history or concurrent regions.

Input parameters:

- `diagram` (string, required): The state machine in this line grammar, one statement per line, up to 40,000 characters: state Name | state "Long label" as Name | state Name <<choice>> | state Name { ... } (composite, nest up to 3)…

Output parameters:

- `analysis` (object)
- `counts` (object)
- `error`
- `grammar` (array)
- `limits` (object)
- `notes` (array)
- `ready` (boolean)
- `shown` (object)
- `states` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-state-diagram/state-diagram#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: 75
- 2026-11-12: 75
- 2026-11-11: 74
- 2026-11-10: 74
- 2026-11-09: 73
- 2026-11-08: 73

## Common questions

### What is the Zovo State Diagram MCP server?

Zovo State Diagram is an MCP server listed in the public MCP registry as io.github.theluckystrike/state-diagram. Turn a few lines of text into a UML state machine diagram document, and check the machine. This page covers its hosted endpoint (https://state-diagram.zovo.one/mcp).

### Is the Zovo State Diagram MCP server safe to use?

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

Zovo State Diagram exposes 2 tools: make_state_diagram, check_state_diagram. Their descriptions and schemas cost roughly 816 tokens of context every time the server is loaded.

### Does the Zovo State Diagram MCP server require authentication?

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

### Is the Zovo State Diagram MCP server still maintained?

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

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