Zovo Sequence Diagram MCP server
io.github.theluckystrike/sequence-diagramtheluckystrikestreamable-httpv1.0.0Scanned
Turns a few lines of text into a UML sequence diagram you can print.
2 tools: 2 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Zovo Sequence Diagram MCP server can do
The Zovo Sequence Diagram MCP server is published by the GitHub account theluckystrike. It has 2 tools. It can create or change data (2 tools: make_sequence_diagram and check_sequence), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 8, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 2Claude Code: ask
check_sequenceUse this when the user wants sequence diagram text checked without a drawing, for example "check my sequence diagram for unclosed blocks" or "which participants have no messages".No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use this when the user wants sequence diagram text checked without a drawing, for example "check my sequence diagram for unclosed blocks" or "which participants have no messages". Takes the same diagram text as make_sequence_diagram. Returns ready true or false; when a line breaks the grammar, the line number, the token and the reason; otherwise the participants with outgoing and incoming message counts, message counts by kind, the blocks with their lines, nesting depth and messages, activate lines with no deactivate, and participants that differ only in upper and lower case. Does not draw the diagram or make files, and does not read features of other diagram languages outside this grammar.
Annotations the server declares
- title: Check sequence diagram text
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
make_sequence_diagramUse this when the user wants a UML sequence diagram drawn, for example "draw a sequence diagram of the login flow" or "make a PDF of these API calls".No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use this when the user wants a UML sequence diagram drawn, for example "draw a sequence diagram of the login flow" or "make a PDF of these API calls". Takes the diagram text in a line grammar: participant Name / actor Name / participant "Long Name" as Alias; A -> B: text (sync), A ->> B: text (async), A --> B: text (reply), A -> A: text (self); note over A: text / note over A,B: text; alt cond / else cond / end, loop cond / end, opt cond / end; activate A / deactivate A; # comment lines. When the user describes the flow in words, write it in this grammar first. Returns counts, the messages in order, the blocks with their messages, a check on the drawing (messages in order, frames holding their messages, overlapping labels), the PDF page count and smallest text size, an interactive diagram, and PDF, SVG and CSV downloads. Refuses a line outside the grammar with its line number and token. Up to 30 participants and 400 messages. Does not read features of other diagram languages outside this grammar. A diagram too wide for the paper with text of at least 7 pt gets no PDF (SVG and CSV only), and the result says so. Download links of large diagrams expire after about 1 hour.
Annotations the server declares
- title: Make sequence diagram
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:23 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://sequence-diagram.zovo.one/mcp: tools/list returned 2 tools to an anonymous client, including make_sequence_diagram (write), check_sequence (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http sequence-diagram https://sequence-diagram.zovo.one/mcpclaude mcp add --transport http sequence-diagram https://sequence-diagram.zovo.one/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__sequence-diagram__make_sequence_diagram",
"mcp__sequence-diagram__check_sequence"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as sequence-diagram. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.theluckystrike/sequence-diagram/verify?hash=7c123ac2b5b69172f761cf1364ee949249cb72f920be84b165d0933c0a478505" | jq -e '.changed == false'Pinned hash 7c123ac2b5b6, from Nov 8, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.theluckystrike/sequence-diagram/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.theluckystrike/sequence-diagram)Source: MCP Registry. Synced Nov 8, 2026, 03:18 UTC.
Zovo Sequence Diagram MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Zovo Sequence Diagram MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Zovo Sequence Diagram MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Zovo Sequence Diagram MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Zovo Sequence Diagram MCP server have?
- 2 tools: 2 write. make_sequence_diagram and check_sequence.
Does the Zovo Sequence Diagram MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Zovo Sequence Diagram MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Zovo Sequence Diagram MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.