Vsix Publish Lint

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

Find the package.json lines that stop vsce before you run the release build

The publisher's own server: Publish.fun

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Local stdio MCP server that inspects a VS Code extension's package.json for lines that would block a vsce publish.

What you can do
  • Points an assistant at a VS Code extension's package.json to find entries that would stop vsce before a release build.
  • Reports the offending lines so they can be fixed ahead of packaging.
  • The manifest lists no tools, so the exact operations are not documented; the README only describes a theme project by ReadyStack.
When to use it
Useful when preparing a VS Code extension release and you want packaging problems in package.json surfaced before running vsce. Otherwise it adds little.
Requirements
Runs as a local process via npx from the npm package @readystack/vsix-publish-lint; requires Node.js and a local VS Code extension project with a package.json. No authentication, environment variables or headers are declared. Desktop only.
Before you install
The README does not document the server's behavior and reads as project marketing, so review the package before running it. It reads project files locally; no write, network or credential behavior is documented.

Installation

In SourceWeft

  1. Open Vsix Publish 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

2
  1. v1.0.4LatestSep 19, 2026
  2. v1.0.2Sep 16, 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.

Other Publish integrations