Svg (georgeharker) MCP Server

svg-mcp PyPI v0.7.1

Published by georgeharker — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

A FastMCP server exposing structured, hierarchical SVG authoring with a render-and-see feedback loop.

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. 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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 7

high Shell/command execution in server code (plugins/opencode/src/index.ts)MTC-SRC-002

In the server's implementation (`plugins/opencode/src/index.ts:25`): 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: spawnSync } from "node:child_process" import { existsSync, readFileSync } from "node:fs" import { homedir } from "node:

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 plugins/opencode/src/index.ts

high Shell/command execution in server code (plugins/opencode/src/sharedserver-resolve.ts)MTC-SRC-002

In the server's implementation (`plugins/opencode/src/sharedserver-resolve.ts:12`): 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: spawnSync } from "node:child_process" import { existsSync, mkdirSync, rmSync, statSync, writeFileSync } from "node:fs"

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 plugins/opencode/src/sharedserver-resolve.ts

high Shell/command execution in server code (plugins/pi/src/index.ts)MTC-SRC-002

In the server's implementation (`plugins/pi/src/index.ts:29`): 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: spawnSync } from "node:child_process" import { existsSync, mkdirSync, readFileSync, writeFileSync } from "node:fs" impo

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 plugins/pi/src/index.ts

high Shell/command execution in server code (plugins/pi/src/pi.ts)MTC-SRC-002

In the server's implementation (`plugins/pi/src/pi.ts:68`): 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: CommandSpec): void exec(command: string, args: string[], options?: ExecOptions): Promise<ExecResult> sendMessag

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 plugins/pi/src/pi.ts

high Shell/command execution in server code (plugins/pi/src/sharedserver-resolve.ts)MTC-SRC-002

In the server's implementation (`plugins/pi/src/sharedserver-resolve.ts:12`): 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: spawnSync } from "node:child_process" import { existsSync, mkdirSync, rmSync, statSync, writeFileSync } from "node:fs"

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 plugins/pi/src/sharedserver-resolve.ts

high Shell/command execution in server code (src/svg_mcp/render/export.py)MTC-SRC-002

In the server's implementation (`src/svg_mcp/render/export.py:74`): 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: vg)) proc = subprocess.run(args, capture_output=True, check=False, timeout=60) if proc.returncod

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 src/svg_mcp/render/export.py

high Shell/command execution in server code (src/svg_mcp/render/resvg.py)MTC-SRC-002

In the server's implementation (`src/svg_mcp/render/resvg.py:66`): 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: proc = subprocess.run( args, capture_output=True,

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 src/svg_mcp/render/resvg.py

Tools 31

Each tool and what it can reach — statically extracted from the published source.

  • set_preview_backdropnetwork egress
  • convert_unitsno sensitive capability
  • current_contextno sensitive capability
  • describe_documentno sensitive capability
  • describe_nodeno sensitive capability
  • export_formatsno sensitive capability
  • export_renderno sensitive capability
  • export_svgno sensitive capability
  • extract_imageno sensitive capability
  • findno sensitive capability
Show 21 more tools ↓
  • get_bboxno sensitive capability
  • get_computed_styleno sensitive capability
  • get_filterno sensitive capability
  • get_geometryno sensitive capability
  • get_paramsno sensitive capability
  • get_subtreeno sensitive capability
  • get_transformno sensitive capability
  • list_documentsno sensitive capability
  • list_fontsno sensitive capability
  • list_guidesno sensitive capability
  • list_layersno sensitive capability
  • list_pagesno sensitive capability
  • list_resourcesno sensitive capability
  • list_stylesno sensitive capability
  • measure_textno sensitive capability
  • outlineno sensitive capability
  • path_bboxno sensitive capability
  • render_backendsno sensitive capability
  • render_documentno sensitive capability
  • render_svgno sensitive capability
  • start_previewno sensitive capability

What this scan could not see

Versions 6

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.7.1 latest A 93/100 7 1.13.0 2026-08-25
v0.7.0 A 93/100 7 1.12.1 2026-08-20
v0.6.2 A 93/100 7 1.12.1 2026-08-18
v0.6.1 A 93/100 4 1.12.1 2026-08-16
v0.5.0 A 93/100 4 1.12.1 2026-08-15
Show 1 more version ↓
v0.4.4 A 93/100 4 1.12.1 2026-07-27

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 · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/svg-mcp-2/badge.svg)](https://mcptrustchecker.com/registry/svg-mcp-2)
HTML
<a href="https://mcptrustchecker.com/registry/svg-mcp-2"><img src="https://mcptrustchecker.com/registry/svg-mcp-2/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/svg-mcp-2/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 svg-mcp --online --registry pypi

Use the free API → How scoring works

Other implementations of Svg 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Developer Tools