Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Zovo Activity Diagram

REMOTE · ACTIVITY-DIAGRAM.ZOVO.ONE

Turn a few lines of text into a UML activity diagram document, and check the flow.

+3 this week 79 Trust /100

Last scanned (19 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability71
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1002 tokens (~334/item across 3 items; 2 tools + 1 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 Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 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 current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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 +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.

  • 19 Nov 26 +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.

  • 16 Nov 26 +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.

  • 14 Nov 26 +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.

  • 12 Nov 26 +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.

  • 10 Nov 26 +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.

  • 9 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 8 Nov 26 73

    First indexed and scored.

Diagnostics

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 · Probed https://activity-diagram.zovo.one/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=zovo.one CN=WE1,O=Google Trust Services,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 1a6be51dae225a780e14b5b59cd24fa3
SANs: zovo.one, *.zovo.one
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of activity-diagram.zovo.one. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
one. DS published 64939 8 Verified
zovo.one. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://activity-diagram.zovo.one/mcp Verified 200
http (plaintext) http://activity-diagram.zovo.one/mcp HTTPS enforced 301 https://activity-diagram.zovo.one/mcp
MCP tools · 2 exposed · ~777 tokens

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 →

Tool Tokens
check_activity_diagram ~277

Use this when the user wants activity diagram text checked without a drawing, for example "is my flow valid?" or "which steps are not reachable?". Takes the same diagram text as make_activity_diagram. Returns ready true or false; when a line breaks the grammar or a block is not closed, the line number, the token and the reason; otherwise the counts, the steps with their block path, steps that are not reachable (found by a breadth-first search from the start), and empty branches. Does not draw the diagram or make files.

NameTypeReqDescription
diagramstringyesThe activity in this line grammar, one statement per line, up to 40,000 characters, 2,000 lines and 400 characters per line (comments included): start | stop | end | :Action text; | if (condition) th…
NameTypeReqDescription
analysisobject––
countsobject––
error–yes–
grammararrayyes–
limitsobjectyes–
nodesarrayyes–
readybooleanyes–
shownobject––

No examples provided.

make_activity_diagram ~500

Use this when the user wants a UML activity diagram or a process flowchart drawn from steps, for example "draw the checkout flow as an activity diagram" or "make a PDF of this process". Takes the diagram text in a line grammar: start / stop / end; :Action text; ; if (condition) then (label) ... elseif (condition) then (label) ... else (label) ... endif; while (condition) is (label) ... endwhile (label); fork ... fork again ... end fork; note: text (right after the step it belongs to); # comments. Labels are optional; a condition or label must not contain ( or ). When the user describes the process in words, write it in this grammar first. Returns counts, the steps in flow order with their block path, the links between them, the flow check (steps that are not reachable, empty branches), 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 200 actions, 60 decisions, 6 fork branches, 6 nesting levels and 400 characters per line. Does not read repeat loops, switch, swimlanes or partitions. Download links of large diagrams expire after about 1 hour.

NameTypeReqDescription
diagramstringyesThe activity in this line grammar, one statement per line, up to 40,000 characters, 2,000 lines and 400 characters per line (comments included): start | stop | end | :Action text; | if (condition) th…
page_sizestring–PDF paper: letter (default) or a4. A wide diagram turns the page to landscape. Example: a4.
titlestring–Title printed on the diagram and used in file names, up to 80 characters, e.g. "Order checkout".
NameTypeReqDescription
analysisobjectyes–
countsobjectyes–
downloadsobjectyes–
edgesarrayyes–
layout_checkobjectyes–
nodesarrayyes–
pdfobjectyes–
shownobject––
titlestringyes–
warningsarrayyes–

No examples provided.

Install

How do I install the Zovo Activity Diagram MCP server?

Zovo Activity Diagram is a hosted endpoint at https://activity-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.

remote · activity-diagram.zovo.one

# add to Claude Code
claude mcp add --transport http theluckystrike-activity-diagram 'https://activity-diagram.zovo.one/mcp'
Common questions

What is the Zovo Activity Diagram MCP server?

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

Is the Zovo Activity Diagram MCP server safe to use?

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

Zovo Activity Diagram exposes 2 tools: make_activity_diagram, check_activity_diagram. Their descriptions and schemas cost roughly 777 tokens of context every time the server is loaded.

Does the Zovo Activity Diagram MCP server require authentication?

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

Is the Zovo Activity Diagram MCP server still maintained?

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

VerifyMCP ran 14 checks on Zovo Activity 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.