Zovo Swimlane
REMOTE · SWIMLANE.ZOVO.ONE
Turns a business process into a cross-functional flowchart that shows which team does each step.
Available components
Last scanned (14 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Productivity and Notes
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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 1008 tokens (~336/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
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 →
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.
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://swimlane.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 swimlane.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://swimlane.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://swimlane.zovo.one/mcp | HTTPS enforced | 301 | https://swimlane.zovo.one/mcp |
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 →
check_swimlane Check swimlane process ~305
Use this when the user wants a process with lanes checked without a drawing, for example "check my process for steps that do not reach the end" or "which steps are unreachable". Takes the same lanes, steps and links as make_swimlane. Returns unknown lanes and step ids, duplicate ids, steps not reachable from a start step, steps with no path to an end step, decisions with fewer than 2 outgoing links or unlabeled branches, end steps with outgoing links, and loops (allowed, listed). Draws nothing and makes no files. Up to 12 lanes, 150 steps, 300 links. Does not rewrite or fix the process; do not use it for plain flowcharts without lanes.
| Name | Type | Req | Description |
|---|---|---|---|
| lanes | array | yes | Lane names in display order, 2 to 12, each up to 40 characters, e.g. ["Customer", "Sales", "Warehouse"]. A lane is usually a role, team or system. |
| links | array | – | Arrows between step ids, up to 300, e.g. [{"from":"s1","to":"s2"},{"from":"s2","to":"s3","label":"yes"}]. |
| steps | array | yes | Steps, 1 to 150, e.g. [{"id":"s1","lane":"Customer","text":"Place order","kind":"start"},{"id":"s2","lane":"Sales","text":"Credit OK?","kind":"decision"}]. |
| Name | Type | Req | Description |
|---|---|---|---|
| counts | object | yes | – |
| decisions | array | yes | – |
| end_steps | array | yes | – |
| issues | array | yes | – |
| limits | object | yes | – |
| loops | array | yes | – |
| no_path_to_end | array | yes | – |
| notes | array | yes | – |
| ready | boolean | yes | – |
| shown | object | – | – |
| start_steps | array | yes | – |
| unreachable | array | yes | – |
No examples provided.
make_swimlane Make swimlane diagram ~565
Use this when the user wants a swimlane diagram, cross-functional flowchart or process map with roles, teams or systems as lanes, for example "draw our order process as a swimlane" or "make a swimlane PDF of who does what". Takes lanes in order, steps (id, lane, text, kind: step, decision, start or end) and links (from, to, label; branches that leave a decision need labels), plus orientation (horizontal: lanes as rows, flow left to right; vertical: lanes as columns, flow top down), page size and title. Returns counts, each step's lane and flow position, unreachable steps, steps with no path to an end, loops, a geometry check (steps outside their lane, overlapping steps and labels, lines crossing a step), an interactive diagram, and PDF, SVG and CSV downloads. Refuses, with the reason: unknown lanes or step ids, duplicate lanes, ids or links, a link from a step to itself, a missing start or end step, an end step with outgoing links, decisions with fewer than 2 outgoing links or with unlabeled or repeated branch labels. When one step with its branch labels is wider than the page at 6 pt, it returns the SVG and CSV without a PDF and says why. Up to 12 lanes, 150 steps, 300 links. Does not draw plain flowcharts without lanes, BPMN message flows, org charts or sequence diagrams. Download links of large diagrams expire after about 1 hour.
| Name | Type | Req | Description |
|---|---|---|---|
| lanes | array | yes | Lane names in display order, 2 to 12, each up to 40 characters, e.g. ["Customer", "Sales", "Warehouse"]. A lane is usually a role, team or system. |
| links | array | – | Arrows between step ids, up to 300, e.g. [{"from":"s1","to":"s2"},{"from":"s2","to":"s3","label":"yes"}]. |
| orientation | string | – | horizontal (default): lanes are rows and the flow runs left to right. vertical: lanes are columns and the flow runs top down. |
| page_size | string | – | PDF page: letter (default), a4 or tabloid (11 x 17 in). Landscape unless portrait needs fewer pages. |
| steps | array | yes | Steps, 1 to 150, e.g. [{"id":"s1","lane":"Customer","text":"Place order","kind":"start"},{"id":"s2","lane":"Sales","text":"Credit OK?","kind":"decision"}]. |
| title | string | – | Title on the diagram and in file names, up to 80 characters, e.g. "Order to cash". |
| Name | Type | Req | Description |
|---|---|---|---|
| counts | object | yes | – |
| downloads | object | yes | – |
| flow_positions | number | yes | – |
| issues | array | yes | – |
| lanes | array | yes | – |
| layout_check | object | yes | – |
| loops | array | yes | – |
| no_path_to_end | array | yes | – |
| orientation | string | yes | – |
| object | yes | – | |
| shown | object | – | – |
| steps | array | yes | – |
| title | string | yes | – |
| unreachable | array | yes | – |
| warnings | array | yes | – |
No examples provided.
How do I install the Zovo Swimlane MCP server?
Zovo Swimlane is a hosted endpoint at https://swimlane.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 · swimlane.zovo.one
claude mcp add --transport http theluckystrike-swimlane 'https://swimlane.zovo.one/mcp'
What is the Zovo Swimlane MCP server?
Zovo Swimlane is an MCP server listed in the public MCP registry as io.github.theluckystrike/swimlane. Turns a business process into a cross-functional flowchart that shows which team does each step. This page covers its hosted endpoint (https://swimlane.zovo.one/mcp).
Is the Zovo Swimlane MCP server safe to use?
Zovo Swimlane 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 Swimlane MCP server expose?
Zovo Swimlane exposes 2 tools: make_swimlane, check_swimlane. Their descriptions and schemas cost roughly 870 tokens of context every time the server is loaded.
Does the Zovo Swimlane MCP server require authentication?
No. We connected to Zovo Swimlane without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zovo Swimlane MCP server still maintained?
Zovo Swimlane 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 Swimlane MCP server?
VerifyMCP ran 14 checks on Zovo Swimlane, 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.