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.

Diagrams MCP

PYPI · DIAGRAMS-MCP-SERVER · 2 COMPONENTS

Generate cloud architecture diagrams, flowcharts, and sequence diagrams.

−2 this week 89 Trust /100

Last scanned (17 minutes ago)

Scores higher than 92% of PyPI servers

Category Cloud Infrastructure

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security90
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known medium-severity CVE affects fastmcp 3.2.3, a direct dependency. A fixed version is available. View diagnostics → Fail
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 4 of 69 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to ByteOverDev/diagrams-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 139 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1301 tokens (~92/item across 14 items; 9 tools + 5 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (78% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 5 Nov 26 −3
    • Stability: pass → 0.80 functional
  • 1 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
  • 29 Oct 26 +14
    • CVE-2026-112910 affects this package: medium ▼ security
    • CVE-2026-112909 affects this package: medium ▼ security
    • Malware scan: unverified → pass ▲ security
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −1
    • GHSA-7xgj-8392-5q4r affects this package: medium ▼ security
    • Known CVEs: CVE check failed: a known medium-severity CVE affects fastmcp 3.2.3, a direct dependency. A fixed version is available. security
  • 23 Oct 26 0
    • Stability: 0.97 → pass security
  • 22 Oct 26 0
    • Stability: pass → 0.97 functional
  • 19 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
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 5 Nov 2026 · Analysed pypi/diagrams-mcp-server@0.1.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo ByteOverDev/diagrams-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/ByteOverDev/diagrams-mcp/.github/workflows/release.yml@refs/tags/v0.1.2
Rekor log index 1277495911
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:7f867828152b1d2f7a9f5d528d998a8628a533a70d956206c87fa95a671dd012

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 7 findings
ID CVE Severity Vector Fix available
GHSA-7xgj-8392-5q4r medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-69hj-f68j-2879 CVE-2026-112909 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N yes
GHSA-8mx5-7m5m-r77g CVE-2026-112910 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L yes
GHSA-qmgc-5h2g-mvrw CVE-2026-22701 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H yes
GHSA-w853-jp5j-5j7f CVE-2025-68146 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H yes
PYSEC-2026-1374 CVE-2026-22701 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H yes
PYSEC-2026-1375 CVE-2025-68146 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 69 packages
Packages resolved 69
Stale 3
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,014 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
find_equivalent ~210

Find cross-provider equivalents for a diagram node by infrastructure role. Given a node name (e.g. 'EC2', 'Lambda', 'ComputeEngine'), returns the infrastructure role category it belongs to and the equivalent nodes from other providers. Args: node: Node class name to look up (case-insensitive, e.g. 'EC2', 'lambda'). target_provider: Optional provider to filter equivalents to (e.g. 'gcp', 'azure', 'aws'). If omitted, all equivalents across all other providers are returned. Returns: A dict with keys: category (str): Infrastructure role category name. description (str): Human-readable description of the category. source (dict): The matched node with keys node, provider, service, import. equivalents (list[dict]): Equivalent nodes, each with keys node, provider, service, import.

NameTypeReqDescription
nodestringyes–
target_provider–––

Structured output declared, but exposes no named fields.

No examples provided.

list_categories ~82

List all infrastructure role categories with their mapped nodes. Returns a list of category dicts, each with: category (str): Category identifier (e.g. 'virtual_machine'). description (str): Human-readable description. providers (list[str]): Providers covered by this category. nodes (dict): Mapping of provider → list of node names in that category.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

list_nodes ~92

List available node classes for a provider.service combo. Args: provider: Provider name (e.g. 'aws', 'gcp', 'k8s'). service: Service category (e.g. 'compute', 'database', 'network'). Returns: List of nodes with keys: name, import, alias_of (optional).

NameTypeReqDescription
providerstringyes–
servicestringyes–
NameTypeReqDescription
resultarrayyes–

No examples provided.

list_providers ~31

List all available diagram providers (aws, gcp, azure, k8s, onprem, etc.).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

list_services ~65

List service categories for a provider (e.g. 'aws' -> ['compute', 'database', ...]). Args: provider: Provider name from list_providers (e.g. 'aws', 'gcp', 'k8s').

NameTypeReqDescription
providerstringyes–
NameTypeReqDescription
resultarrayyes–

No examples provided.

render_diagram ~140

Render a mingrammer/diagrams Python snippet to PNG and return the image. The code must be a complete Python script using `from diagrams import ...` imports and a `with Diagram(...)` context manager block. Args: code: Full Python code using the diagrams library. filename: Output filename without extension. download_link: If True, store the image on the server and return a temporary download URL path (/images/{token}) instead of the inline image. The link expires after 15 minutes.

NameTypeReqDescription
codestringyes–
download_linkboolean––
filenamestring––

No output schema declared.

No examples provided.

render_mermaid ~174

Render a Mermaid diagram definition and return the image with metadata. The definition should be valid Mermaid syntax (e.g. flowchart, sequence, class, ER, state, or Gantt diagram). Returns a list of content blocks: the rendered image (SVG inline or PNG download link) plus a JSON text block with metadata including a mermaid.live edit link for opening the diagram in a browser editor. Args: definition: Mermaid diagram definition text. filename: Output filename without extension. download_link: If True, store the image on the server and return a temporary download URL path (/images/{token}) instead of the inline image. The link expires after 15 minutes.

NameTypeReqDescription
definitionstringyes–
download_linkboolean––
filenamestring––
NameTypeReqDescription
resultarrayyes–

No examples provided.

render_plantuml ~141

Render a PlantUML diagram definition to PNG and return the image. The definition should be valid PlantUML syntax wrapped in @startuml/@enduml (sequence, class, component, activity, state, deployment, etc.). Args: definition: PlantUML diagram definition text. filename: Output filename without extension. download_link: If True, store the image on the server and return a temporary download URL path (/images/{token}) instead of the inline image. The link expires after 15 minutes.

NameTypeReqDescription
definitionstringyes–
download_linkboolean––
filenamestring––

No output schema declared.

No examples provided.

search_nodes ~79

Search for diagram nodes by keyword across all providers and services. Args: query: Search term (case-insensitive substring match). Returns: List of matching nodes with keys: node, provider, service, import, alias_of (optional). Sorted by relevance: exact match first, then prefix, then substring.

NameTypeReqDescription
querystringyes–
NameTypeReqDescription
resultarrayyes–

No examples provided.

Install

How do I install the Diagrams MCP server?

Diagrams MCP runs locally as a PyPI package, launched with uvx diagrams-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · diagrams-mcp-server

# add to Claude Code
claude mcp add mskry-diagrams-mcp-server -- uvx diagrams-mcp-server
Common questions

What is the Diagrams MCP server?

Diagrams MCP is listed in the public MCP registry as io.github.mskry/diagrams-mcp-server. Generate cloud architecture diagrams, flowcharts, and sequence diagrams. This page covers its PyPI package (diagrams-mcp-server).

Is the Diagrams MCP server safe to use?

Diagrams MCP scores 89 out of 100 on VerifyMCP. We recorded 7 known advisories against it as of 5 November 2026. Its build provenance is signed and verified. 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 Diagrams MCP server expose?

Diagrams MCP exposes 9 tools: render_diagram, list_providers, list_services, list_nodes, search_nodes, and 4 more. Their descriptions and schemas cost roughly 1,014 tokens of context every time the server is loaded.

Is the Diagrams MCP server still maintained?

Diagrams MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Diagrams MCP server under?

Diagrams MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.