Security Headers Csp Lint

io.github.jmshinhwaPublished by GitHub account jmshinhwav0.1.3Updated Oct 24, 2026

Reads security headers and CSP line by line in your config file and names the lines that silently do

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Local MCP server that reads security headers and CSP in a config file line by line and names the lines that silently weaken protection.

What you can do
  • Reads security header and Content-Security-Policy configuration in a project's config file.
  • Points out the specific lines that silently weaken or break the intended policy.
  • Reports findings line by line rather than as a general scan summary.
  • No tool list is published, so the exact operations are not documented.
When to use it
Useful when reviewing or hardening HTTP security headers and CSP in a web project's configuration and you want an assistant to flag the exact lines that quietly undermine the policy.
Requirements
Runs as a local process on the user's machine via npx from the npm package @readystack/security-headers-csp-lint; desktop client only. No authentication, environment variables or headers are declared.
Before you install
The README content does not match the described purpose, so verify the package before installing. It reads project config files, which may contain sensitive values; review what is sent to the assistant.

Installation

In SourceWeft

  1. Open Security Headers Csp 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. v0.1.3LatestSep 19, 2026
  2. v0.1.1Sep 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.