Svg Asset Compliance Lint

io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.4Updated Oct 24, 2026

14 rules over the SVG files your design tool exported, before they become a legal object

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that lints exported SVG files against 14 compliance rules before they are used as legal objects.

What you can do
Checks SVG files exported from a design tool against a set of 14 compliance rules, flagging assets that would not pass as legal objects. Runs locally over stdio as an npm package invoked with npx. The manifest lists no individual tools, so the exact operations are not documented in the supplied material.
When to use it
Worth adding when you export SVG assets from a design tool and want an assistant to check them against compliance rules before they are shipped or used as legal objects.
Requirements
A local runtime with Node.js so the npm package can be started with npx over stdio. No authentication, environment variables or headers are declared. Desktop only; not available as a web executable.
Before you install
The supplied README describes VS Code themes rather than this linter, so the documentation does not match the server's stated purpose; verify behavior before relying on it. No tools, credentials or data-handling details are documented.

Installation

In SourceWeft

  1. Open Svg Asset Compliance Lint in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

readystack-themes

Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack

Source: README.md at commit ee1c884

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.4LatestSep 23, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.