Line9
REMOTE · MCP.LINE9.AI · SCANNED SEP 25
Render Mermaid with Line9 layout in your assistant.
Available components
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 Security74
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability77
- 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 636 tokens (~159/item across 4 items; 3 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 Management27
- Stability observed for 8 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 3 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
How do I install the Line9 MCP server?
Line9 is a hosted endpoint at https://mcp.line9.ai/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 · mcp.line9.ai
claude mcp add --transport http ai-line9-diagrams 'https://mcp.line9.ai/mcp'
{
"mcpServers": {
"ai-line9-diagrams": {
"url": "https://mcp.line9.ai/mcp"
}
}
} {
"servers": {
"ai-line9-diagrams": {
"type": "http",
"url": "https://mcp.line9.ai/mcp"
}
}
} [mcp_servers.ai-line9-diagrams] url = "https://mcp.line9.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-line9-diagrams": {
"type": "remote",
"url": "https://mcp.line9.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-line9-diagrams --url 'https://mcp.line9.ai/mcp' --transport streamable-http
mcp_servers:
ai-line9-diagrams:
url: "https://mcp.line9.ai/mcp" {
"McpServers": {
"ai-line9-diagrams": {
"Transport": "http",
"Url": "https://mcp.line9.ai/mcp"
}
}
} assistant mcp add ai-line9-diagrams -t streamable-http -u 'https://mcp.line9.ai/mcp'
{
"mcpServers": {
"ai-line9-diagrams": {
"type": "http",
"url": "https://mcp.line9.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 71
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 25 Sept 2026 · Probed https://mcp.line9.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=line9.ai | CN=WE1,O=Google Trust Services,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 8201651f4a20a7590ed93bec1d622af3 |
| SANs: line9.ai, mcp.line9.ai, *.mcp.line9.ai | ||||||
| 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 mcp.line9.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| line9.ai. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.line9.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.line9.ai/mcp | HTTPS enforced | 301 | https://mcp.line9.ai/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 →
get_diagram Get a diagram ~132
Fetch a published diagram's current Mermaid source by name or slug, and show it rendered. The returned source is stamped with the diagram's identity — keep the `line9:` frontmatter block when you edit it so that Line9 recognises the diagram when it is opened and published there instead of creating a new one. Requires Line9 sign-in. This connector cannot publish or save. To publish, the user opens the diagram in Line9 (the `open_url` link) and publishes there — not with the Line9 CLI.
| Name | Type | Req | Description |
|---|---|---|---|
| diagram | string | yes | Diagram name, slug, or trailing public_ref. |
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | – | – |
| controls | object | – | – |
| diagram | object | – | – |
| diagram_type | string|null | – | – |
| diagrams | array | – | – |
| edge_count | number | – | – |
| engine_version | string | – | – |
| error | object | – | – |
| fallback_reason | string | – | – |
| height | number | – | – |
| mermaid_version | string | – | – |
| node_count | number | – | – |
| open_url | string | – | – |
| orientation | string | – | – |
| path | string | – | – |
| plan | string | – | – |
| render_mode | string | – | – |
| schema_version | number | yes | – |
| signed_in | boolean | – | – |
| source | string | – | – |
| status | string | yes | – |
| stop_reason | string | – | – |
| svg | string | – | – |
| truncated | boolean | – | – |
| warnings | array | – | – |
| watermark | boolean | – | – |
| width | number | – | – |
No examples provided.
list_diagrams List my diagrams ~84
List the diagrams published in the user's Line9 workspace(s): name, visibility, version, last update and permalink. Use it to find a diagram before `get_diagram`. Requires Line9 sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum rows to return (1–100; default 50). |
| query | string | – | Case-insensitive substring of the diagram name. |
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | – | – |
| controls | object | – | – |
| diagram | object | – | – |
| diagram_type | string|null | – | – |
| diagrams | array | – | – |
| edge_count | number | – | – |
| engine_version | string | – | – |
| error | object | – | – |
| fallback_reason | string | – | – |
| height | number | – | – |
| mermaid_version | string | – | – |
| node_count | number | – | – |
| open_url | string | – | – |
| orientation | string | – | – |
| path | string | – | – |
| plan | string | – | – |
| render_mode | string | – | – |
| schema_version | number | yes | – |
| signed_in | boolean | – | – |
| source | string | – | – |
| status | string | yes | – |
| stop_reason | string | – | – |
| svg | string | – | – |
| truncated | boolean | – | – |
| warnings | array | – | – |
| watermark | boolean | – | – |
| width | number | – | – |
No examples provided.
render_diagram Render diagram ~408
Render Mermaid source with Line9's layout engine. Call this whenever you write or change Mermaid and the user should see the result. Flowcharts and sequence diagrams get Line9's layout; other Mermaid kinds are rendered with Mermaid's own layout and flagged as such. Returns a short verdict — kind, size, warnings, or a parse error with its line and column — plus an "Open in Line9" link. On a parse error, fix the named line and call again. Assistants that support MCP Apps show the diagram in a panel; there, do not paste the SVG or repeat the source in your reply. In an assistant with no panel (a terminal or editor), reply with the verdict line and the `open_url` link — that link is the only way the user sees the diagram. Write flowcharts as `flowchart LR` unless the user asks for top-to-bottom; chat panels are wide and short. No sign-in needed; renders carry a small Line9 mark unless the user is signed in to Line9 Pro. Set theme, orientation, spacing and legend in the source itself (`line9:` frontmatter; `flowchart LR`), never as arguments. This connector cannot publish or save. To publish, the user opens the diagram in Line9 (the `open_url` link) and publishes there — not with the Line9 CLI.
| Name | Type | Req | Description |
|---|---|---|---|
| plan | string | – | Opaque plan from a previous result (widget use). A hint only: skips the solve when it still fits the source. |
| source | string | yes | Mermaid source. Optional YAML frontmatter is honoured — set it in the source, never as arguments: `title`, and a nested `line9:` block with `theme` (one of `boardroom`, `linen`, `blueprint`), `scale:… |
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | – | – |
| controls | object | – | – |
| diagram | object | – | – |
| diagram_type | string|null | – | – |
| diagrams | array | – | – |
| edge_count | number | – | – |
| engine_version | string | – | – |
| error | object | – | – |
| fallback_reason | string | – | – |
| height | number | – | – |
| mermaid_version | string | – | – |
| node_count | number | – | – |
| open_url | string | – | – |
| orientation | string | – | – |
| path | string | – | – |
| plan | string | – | – |
| render_mode | string | – | – |
| schema_version | number | yes | – |
| signed_in | boolean | – | – |
| source | string | – | – |
| status | string | yes | – |
| stop_reason | string | – | – |
| svg | string | – | – |
| truncated | boolean | – | – |
| warnings | array | – | – |
| watermark | boolean | – | – |
| width | number | – | – |
No examples provided.
What is the Line9 MCP server?
Line9 is an MCP server listed in the public MCP registry as ai.line9/diagrams. Render Mermaid with Line9 layout in your assistant. This page covers its hosted endpoint (https://mcp.line9.ai/mcp).
Is the Line9 MCP server safe to use?
Line9 scores 75 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 Line9 MCP server expose?
Line9 exposes 3 tools: render_diagram, list_diagrams, get_diagram. Their descriptions and schemas cost roughly 624 tokens of context every time the server is loaded.
Does the Line9 MCP server require authentication?
No. We connected to Line9 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Line9 MCP server still maintained?
Line9 is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.