Glyphs MCP Server

glyphs-mcp PyPI v0.2.1

Published by nmassi — 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.

MCP bridge for AI-assisted type design in GlyphsApp

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 1

high Shell/command execution in server code (plugin/GlyphsMCP.glyphsPlugin/Contents/Resources/handlers.py)MTC-SRC-002

In the server's implementation (`plugin/GlyphsMCP.glyphsPlugin/Contents/Resources/handlers.py:5977`): 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: error = None try: exec(code, {"Glyphs": Glyphs, "__builtins__": __builtins__}) except Exception as e: error =

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 plugin/GlyphsMCP.glyphsPlugin/Contents/Resources/handlers.py

Tools 41

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

  • analyze_kerningno sensitive capability
  • analyze_spacingno sensitive capability
  • audit_font_colorno sensitive capability
  • check_compatibilityno sensitive capability
  • check_diagonal_weightsno sensitive capability
  • check_junctionsno sensitive capability
  • check_overshootsno sensitive capability
  • check_punctuationno sensitive capability
  • check_related_formsno sensitive capability
  • compare_colorno sensitive capability
Show 31 more tools ↓
  • compare_proportionsno sensitive capability
  • compare_stemsno sensitive capability
  • create_glyphno sensitive capability
  • delete_glyphno sensitive capability
  • delete_kerning_pairno sensitive capability
  • duplicate_glyphno sensitive capability
  • execute_in_glyphsno sensitive capability
  • get_featuresno sensitive capability
  • get_font_infono sensitive capability
  • get_glyphno sensitive capability
  • get_glyph_svgno sensitive capability
  • get_kerningno sensitive capability
  • get_mastersno sensitive capability
  • get_selectionno sensitive capability
  • get_spacing_stringsno sensitive capability
  • get_stem_targetsno sensitive capability
  • list_glyphsno sensitive capability
  • measure_colorno sensitive capability
  • measure_stemsno sensitive capability
  • rename_glyphno sensitive capability
  • rmx_batchno sensitive capability
  • rmx_harmonizeno sensitive capability
  • rmx_monospaceno sensitive capability
  • rmx_scaleno sensitive capability
  • rmx_tuneno sensitive capability
  • set_feature_codeno sensitive capability
  • set_glyph_colorno sensitive capability
  • set_glyph_pathsno sensitive capability
  • set_glyph_unicodeno sensitive capability
  • set_glyph_widthno sensitive capability
  • set_kerning_pairno sensitive capability

What this scan could not see

Versions 1

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.2.1 latest A 93/100 1 1.13.0 2026-08-25

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

Use the free API → How scoring works

More in Developer Tools