MCP server for Mermaid diagram validation and rendering
Cloud & Infrav1.0.0streamable-httpmcp.mermaidchart.com repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 557ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo Mermaid Server@1.0.0 |
| tooling | 35 / 35 | tools/list OK: 25 tools e.g. "validate_and_render_mermaid_diagram"; 25/25 described, 25/25 fully-typed schemas, median description 158 chars |
| latency | 7 / 10 | initialize round-trip 557ms |
| provenance | 15 / 15 | description present; repository linked; version 1.0.0; namespace com.mermaidchart matches endpoint/repo |
Score 97/100 · latency 557ms · 25 tools · auth: open
Claude Code:
claude mcp add --transport http mermaid-mcp https://mcp.mermaidchart.com/mcp
Generic MCP client config:
{ "mcpServers": { "mermaid-mcp": { "type": "http", "url": "https://mcp.mermaidchart.com/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/com.mermaidchart/mermaid-mcp · referral link https://mcpqueen.com/go/com.mermaidchart/mermaid-mcp (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/com.mermaidchart/mermaid-mcp)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 04:15 | A | 97 | 557ms |