Lit Binding Xss Audit

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

Finds the lit-html binding positions auto-escaping does not cover, before the component ships

The publisher's own server: audit.domains - Domain Valuation

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Local MCP server that audits lit-html templates for binding positions where auto-escaping does not apply, before a component ships.

What you can do
  • Audit lit-html templates for binding positions that auto-escaping does not cover.
  • Surface risky bindings so they can be reviewed before a component is released.
  • No tool list is published, so the exact operations are not documented; the description only states the audit purpose.
When to use it
Useful when you maintain Lit or lit-html components and want a pre-release check of template bindings for XSS-prone positions that escaping does not handle.
Requirements
Runs as a local process over stdio, launched with npx from the npm package; Node.js and network access for the package fetch are implied. No authentication, environment variables or headers are declared. Desktop only.
Before you install
The README does not describe the audit tooling; its visible content is about VS Code themes and a website, so the package's actual behavior is hard to verify from the listing. Review the package before running it locally, and treat any findings as advisory rather than a guarantee.

Installation

In SourceWeft

  1. Open Lit Binding Xss Audit 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 23, 2026
  2. v1.0.2Sep 19, 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 Audit integrations