Architecture Diagrams
PYPI · ARCH-DIAGRAM-MCP · 2 COMPONENTS
AWS, Azure and GCP architecture diagrams with official icons, reviews, Terraform and GCP import
Available components
Last scanned (17 hours ago)
Scores higher than 74% of PyPI servers
Category Cloud Infrastructure
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 Security95
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects filelock 3.19.1, reached via diagrams > pre-commit > virtualenv > filelock. A fixed version is available. View diagnostics → Fail
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 2 of 45 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 apatilgtn/architecture-diagrams). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1098 tokens (~109/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 (70% 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 10 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 current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 29 Oct 26 0
- CVE-2026-112910 affects this package: medium ▼ security
- CVE-2026-112909 affects this package: medium ▼ security
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 62
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 4 Nov 2026 · Analysed pypi/arch-diagram-mcp@1.2.0
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 | apatilgtn/architecture-diagrams |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/apatilgtn/architecture-diagrams/.github/workflows/release.yml@refs/tags/v1.2.0 |
| Rekor log index | 3513951967 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:b714719fca673521baddb9985980389bfbba204351ab2069c39e274cfd0a612c |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 6 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| 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 45 packages
| Packages resolved | 45 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
diagram_from_inventory ~297
Diagram infrastructure that is already running, from the cloud's own inventory, with real names. Google Cloud: pass the output of `gcloud asset list --project <id> --content-type resource --format json` (or `gcloud asset export` newline-delimited JSON) in `inventory_json`, or a file `path` inside the configured input roots. Works however the resources were created (console, gcloud, IaC). Layout: Project > VPC > Subnet > GKE cluster > namespace. Edges come from configuration (Cloud SQL/secret/Pub/Sub references, URLs matched to Cloud Run services, load balancer backends, push subscriptions, Scheduler targets, VPC connectors). Filter with `projects`, `regions` and `labels` (e.g. {"app": "payments"}); `include_neighbors` keeps resources that matched resources connect to. Calls made only in application code are not visible: add those edges to the returned spec and re-render with generate_architecture_diagram.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | – |
| include_kubernetes | boolean | – | – |
| include_neighbors | boolean | – | – |
| inventory_json | – | – | – |
| labels | – | – | – |
| output_formats | – | – | – |
| path | – | – | – |
| projects | – | – | – |
| provider | string | – | – |
| regions | – | – | – |
| render_diagram | boolean | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
diagram_from_terraform ~142
Build a diagram from Terraform: `terraform show -json plan.out`, state JSON, or a .tfstate file. Pass the JSON text in `terraform_json`, or a file `path` inside the configured input roots. VPC/VNet/subnet/resource-group become nested boundaries; references become edges (dashed = inferred through listeners, NICs, role assignments, etc.). Returns the generated spec so it can be refined and re-rendered.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | – |
| output_formats | – | – | – |
| path | – | – | – |
| render_diagram | boolean | – | – |
| terraform_json | – | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
generate_architecture_diagram ~111
Render an architecture diagram with official provider icons. spec.nodes: services (`type` = icon id from search_icons). spec.clusters: boundaries (account, subscription, project, region, VPC/VNet, subnet, AZ, namespace), nested with `parent`. spec.edges: node-to-node connections with optional label, colour and style. spec.output_formats: any of png, svg (self-contained), pdf, jpg. Returns file paths and an inline PNG preview.
| Name | Type | Req | Description |
|---|---|---|---|
| spec | – | yes | – |
No output schema declared.
No examples provided.
get_template ~32
Return a reference architecture spec to customise and pass to generate_architecture_diagram.
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_icon_categories ~29
List every category of a provider and the service icons in each.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_templates ~33
List bundled reference architectures (AWS, Azure, GCP) that can be loaded with get_template.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
review_architecture ~57
Heuristic Well-Architected review of a spec (security, reliability, operations, performance). Returns a 0-100 score, grade, and findings with recommendations. Findings reflect only what the diagram shows.
| Name | Type | Req | Description |
|---|---|---|---|
| spec | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_icons ~87
Search ~1,900 official icons by service name, alias or category. Examples: 'ecs', 's3', 'aks', 'cloud run', 'postgres', 'redis', 'kafka', 'load balancer'. Returns canonical ids (usable as node `type`) and their aliases.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| provider | – | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
server_info ~28
Report version, Graphviz status, icon count, storage, auth mode, caller identity and limits.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
validate_diagram ~32
Check a spec without rendering: icon ids (with suggestions), references, nesting, limits.
| Name | Type | Req | Description |
|---|---|---|---|
| spec | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Architecture Diagrams MCP server?
Architecture Diagrams runs locally as a PyPI package, launched with uvx arch-diagram-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · arch-diagram-mcp
claude mcp add apatilgtn-architecture-diagrams -- uvx arch-diagram-mcp
What is the Architecture Diagrams MCP server?
Architecture Diagrams is an MCP server listed in the public MCP registry as io.github.apatilgtn/architecture-diagrams. AWS, Azure and GCP architecture diagrams with official icons, reviews, Terraform and GCP import. This page covers its PyPI package (arch-diagram-mcp).
Is the Architecture Diagrams MCP server safe to use?
Architecture Diagrams scores 77 out of 100 on VerifyMCP. We recorded 6 known advisories against it as of 4 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 Architecture Diagrams MCP server expose?
Architecture Diagrams exposes 10 tools: search_icons, list_icon_categories, list_templates, get_template, validate_diagram, and 5 more. Their descriptions and schemas cost roughly 848 tokens of context every time the server is loaded.
Is the Architecture Diagrams MCP server still maintained?
Architecture Diagrams is still listed as active in the MCP registry. We last reached this channel on 4 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 Architecture Diagrams MCP server under?
Architecture Diagrams declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.