io.github.jmshinhwa/security-headers-csp-lint MCP Server
io.github.jmshinhwa/security-headers-csp-lint
What this kind of tool is for
- Scan a repository or dependency tree for known vulnerabilities.
- Audit secrets, permissions, or headers during a pre-release review.
- Have your agent explain a suspicious script or config before you run it.
How to compare servers like this
- Failure mode:
- Vulnerability reports are probabilistic; read findings as leads to verify, not verdicts.
- Data leaving the box:
- Check whether files or code are uploaded anywhere before scanning anything private.
- Maintenance signal:
- Security rulesets age fast; stale tools miss new classes of issue.
- Report clarity:
- The best tools say what is wrong, how sure they are, and how to fix it — verify findings yourself.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the io.github.jmshinhwa/security-headers-csp-lint MCP server?
Reads security headers and CSP line by line in your config file and names the lines that silently do
How to install io.github.jmshinhwa/security-headers-csp-lint
Copy-paste configuration for popular MCP clients.
{
"mcpServers": {
"security-headers-csp-lint": {
"command": "npx",
"args": [
"-y",
"@readystack/security-headers-csp-lint",
"--mcp"
]
}
}
}Related MCP servers
13 rules that decide whether a vulnerability report ever reaches you
View repository →Find the lines your bank will refuse before you send the batch
View repository →Finds retired API versions and removed sfdx force:* commands in your DX repo before a deploy or a CI
View repository →Reads your SOUP register the way an auditor does: 16 rules over clauses 8.1.2, 5.3.3, 5.3.4, 4.3 and
View repository →Reads the licence field in the open manifest and names every deprecated SPDX id, invalid string, PEP
View repository →19 offline checks on the SPF, DMARC and DKIM records in your branch — including the DMARC rewrite of
View repository →