Vaults Diagram Tools MCP Server

vaults-diagram-tools npm v0.1.4

Published by malnati — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.

Trust grade
A
100/100
Last scanned
Trust
A · 100/100
How safe the published surface and source look. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade

Started at 100 and nothing was deducted: the deterministic scan raised no scored threat in the published surface it inspected. Capability observations and advisory notes are recorded but never lower the score.

Findings 12

high Shell/command execution in server code (packages/mcp/tools.mjs)MTC-SRC-002

In the server's implementation (`packages/mcp/tools.mjs:6`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server packages/mcp/tools.mjs

high Shell/command execution in server code (packages/renderer/inject-mermaid-icons.py)MTC-SRC-002

In the server's implementation (`packages/renderer/inject-mermaid-icons.py:302`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: subprocess.run(

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server packages/renderer/inject-mermaid-icons.py

high Shell/command execution in server code (packages/renderer/inject-sequence-fontawesome.py)MTC-SRC-002

In the server's implementation (`packages/renderer/inject-sequence-fontawesome.py:13`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: subprocess.run(

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server packages/renderer/inject-sequence-fontawesome.py

high Shell/command execution in server code (packages/renderer/render-mermaid-ascii.mjs)MTC-SRC-002

In the server's implementation (`packages/renderer/render-mermaid-ascii.mjs:16`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server packages/renderer/render-mermaid-ascii.mjs

high Shell/command execution in server code (packages/renderer/tests/lib/network-guard.mjs)MTC-SRC-002

In the server's implementation (`packages/renderer/tests/lib/network-guard.mjs:42`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server packages/renderer/tests/lib/network-guard.mjs

high Shell/command execution in server code (packages/renderer/tests/markdown-policy.test.mjs)MTC-SRC-002

In the server's implementation (`packages/renderer/tests/markdown-policy.test.mjs:5`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server packages/renderer/tests/markdown-policy.test.mjs

high Shell/command execution in server code (packages/renderer/tests/sequence-layout.test.mjs)MTC-SRC-002

In the server's implementation (`packages/renderer/tests/sequence-layout.test.mjs:5`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server packages/renderer/tests/sequence-layout.test.mjs

high Shell/command execution in server code (packages/renderer/tests/wrapper-default-vendor.test.mjs)MTC-SRC-002

In the server's implementation (`packages/renderer/tests/wrapper-default-vendor.test.mjs:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server packages/renderer/tests/wrapper-default-vendor.test.mjs

high Shell/command execution in server code (packages/renderer/tests/wrapper-puppeteer-config.test.mjs)MTC-SRC-002

In the server's implementation (`packages/renderer/tests/wrapper-puppeteer-config.test.mjs:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server packages/renderer/tests/wrapper-puppeteer-config.test.mjs

high Shell/command execution in server code (packages/source-diagrams/source-diagrams.mjs)MTC-SRC-002

In the server's implementation (`packages/source-diagrams/source-diagrams.mjs:15`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server packages/source-diagrams/source-diagrams.mjs

medium Dynamic module load from a non-literal (packages/renderer/build-mermaid-icon-registry.mjs)MTC-SRC-005

In the server's implementation (`packages/renderer/build-mermaid-icon-registry.mjs:169`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: import(packageName)

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server packages/renderer/build-mermaid-icon-registry.mjs

medium Dynamic module load from a non-literal (packages/renderer/render-mermaid-assets.mjs)MTC-SRC-005

In the server's implementation (`packages/renderer/render-mermaid-assets.mjs:271`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: import(spec)

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server packages/renderer/render-mermaid-assets.mjs

What this scan could not see

Versions

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.4 latest A 100/100 12 1.5.0 2026-07-22

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 100/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/vaults-diagram-tools/badge.svg)](https://mcptrustchecker.com/registry/vaults-diagram-tools)
HTML
<a href="https://mcptrustchecker.com/registry/vaults-diagram-tools"><img src="https://mcptrustchecker.com/registry/vaults-diagram-tools/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/vaults-diagram-tools/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan vaults-diagram-tools --online

Use the free API → How scoring works

More in Developer Tools